RSS feedTest Plan
Integration Testing: Why? What? & How?
By admin
Introduction:
As we covered in various articles in the Testing series there are various levels of testing:
Unit Testing, Integration Testing, System Testing
Each level of testing builds on the previous level.
“Unit testing” focuses on testing a unit of the code.
“Integration testing” is the next level of testing. This ‘level of testing’ focuses on testing the integration of “units of code” or components.
How does Integration Testing fit into the Software Development Life Cycle?
Software Quality Management
By admin | 2 comments
2This article gives an overview of Software Quality Management and various processes that are a part of Software Quality Management. Software Quality is a highly overused term and it may mean different things to different people. You will learn What is Software Quality Management?, What does it take to Manage Software Quality?, Quality Planning, Quality Assurance, Quality Control, Importance of Documentation and What is Defect Tracking?
The definition of the ISO 8204 for quality:
“Totality of characteristics of an entity that bears on its ability to satisfy stated and implied needs.”
This means that the Software product delivered should be as per the requirements defined. We now examine a few more terms used in association with Software Quality.
Quality Planning:
In the Planning Process we determine the standards that are relevant for the Software Product, the Organization and the means to achieve them.
Life Cycle of Testing Process
By admin | 2 comments
2This article explains about Differant steps in Life Cycle of Testing Process. in Each phase of the development process will have a specific input and a specific output. Once the project is confirmed to start, the phases of the development of project can be divided into the following phases:
- Software requirements phase.
- Software Design
- Implementation
- Testing
- Maintenance
In the whole development process, testing consumes highest amount of time. But most of the developers oversee that and testing phase is generally neglected. As a consequence, erroneous software is released. The testing team should be involved right from the requirements stage itself.
The various phases involved in testing, with regard to the software development life cycle are:
1. Requirements stage
2. Test Plan
3. Test Design.
4. Design Reviews
5. Code Reviews
6. Test Cases preparation.
7. Test Execution
8. Test Reports.
9. Bugs Reporting
10. Reworking on patches.
11. Release to production.
adobe first time quality engineer
By admin | 3 comments
3
Mai aveti pana maine la ora 24.00 sa va inscrieti la cea de-a doua editie a training-ului First Time Quality Engineer oferit de Adobe in cadrul programului Adobe Learning Center.
Training-ul este destinat exclusiv studentilor sau proaspetilor absolventi cu zero experienta si care vor sa isi inceapa o cariera in testarea software. Acesta se va desfasura pe o perioada de 5 zile (11-15 mai) zilnic de la 9 la 17, deci practic veti gusta cu adevarat din aroma corporatista din domeniul it 
(acest lucru nefiind neaparat un lucru rau)
Cei de la Adobe spun ca in acest timp angajatii lor vor incerca sa le arate juniorilor “ce presupune munca unui tester in echipele Adobe”.
Detaliile complete si agenda pot fi gasite aici.
Ca o nota personala, mi-se pare o initiativa foarte frumoasa, chiar ma bucur sa vad SRL-uri de la noi care se ocupa cu formarea noilor talente.
O mica problema ar consta in faptul ca nu sunt sigur daca veti si invata ceva din toata treaba asta pentru ca am avut ocazia acum 1 an sa dau un interviu la Adobe pt un post de senior QA si mi-au lasat o impresie foarte proasta. Raman la parerea mea ca oamenii stau foarte prost la capitolul quality assurance/metodologie/organizare. Si nu am nimic cu testerii cu mai degraba cu managementul defectuos din zona asta (probabil nu au gasit inca un manager QA care sa aiba si amanta).
Ma asteptam sa port o discutie tehnica inteligenta, provocatoare, dar in schimb m-am ales cu un test de engleza (traducere din ro in en) si am determinat cate frizerii sunt in Bucuresti. Ah! si cate bile rosii sunt in borcanul 2.
Exemplu de test plan
By george
Test plan-ul este unul din cele mai importante documente care se utilizeaza in procesul de testare. Eu unu il privesc ca un fel de “project management document” al procesului de testare. Cum la inceputul drumului meu in domeniul testarii software, aveam mari probleme in crearea unui plan de test, m-am gandit sa impartasesc cu voi un exemplu de test plan.
Bineinteles, ce voi prezenta mai departe este un test plan generalizat, asta nu inseamna ca trebuie urmat cu strictete, si ca neapart trebuie sa includa toate sectiunile pe care le voi prezenta eu sau ca nu se pot adauga alte lucruri. In functie de necesitatile fiecarui proiect in parte, test planul poate sa arate diferit ca si forma si continut.
Linkedin
Facebook
Twitter
RSS
Comentarii recente