Page 21 - SOFTWARE TESTING & QUALITY ASSURANCE

Software Testing and Quality Assurance

(c) Identify the task that is not performed by a software developer during software testing.
(i) Study and understand the requirements and prepare verification and validation test
(ii) Prepare test data (iii) Plan testing (iv) Automate test cases (v) Fix defects
(d) During which stage of V Model is the acceptance test plan developed?

(i) Requirements specifications (ii) Functional specifications
(iii) System design (iv) Integration test
(e) What testing is carried out after integrating the units to ensure that specifications are met?
(i) Agile testing (ii) Unit testing (iii) System testing (iv) Acceptance testing
1.7 Review Questions

1. “The general aim of testing is to affirm the quality of software systems by systematically
exercising the software in carefully controlled circumstances”. Justify.
2. "Deve Gelperin and William C. Hetzel classified software testing based on the goals and phases".
Explain the phases.
3. What kind of bugs can you think of while testing a web page? How would you classify them?
4. Factors such as communication failure, unrealistic development timeframe, poor design logic,
poor coding practices and lack of skilled testing are reasons for occurrence of bugs. Explain.

5. Bugs detected at different levels of software development life cycle have different effects on the
cost incurred in resolving them. Explain.
6. Is there any difference between the water fall model and the spiral model? Discuss.
7. In V model, test cases are developed at every stage of software development. Explain.
8. Explain how you will carry out software development process using RAD model.

9. In Agile model, the customers, developers, and testers constantly interact with each other during
the entire development process. Discuss.
10. Do you think that all bugs found during software testing will not be fixed? Discuss.
Answers: Self Assessment

1. (a) True (b) False (c) True (d) True (e) False (f) False
2. (a) Incremental, Iterative (b) Communication (c) Cost (d) Functional code
3. (a) 1957-1978 (b) Human (c) Fix defects (d) Requirements specifications (e) System testing
1.8 Further Readings

Ron Patton, Software Testing-Second Edition, SAMS Publishing, USA
Hutcheson, Marnie L, Software Testing Fundamentals, Wiley Publishing, USA

http://www.articlesnatch.com/Article/Software-Bug-And-Their-Common-
Types/594429
http://software-testing-zone.blogspot.com/2008/12/why-are-bugsdefects-in-
software.html
http://tech.lds.org/index.php/newsletter-archive/238-the-cost-of-bugs
http://msdn.microsoft.com/en-us/library/ff649520.aspx
http://www.asknumbers.com/QualityAssuranceandTesting.aspx

14 LOVELY PROFESSIONAL UNIVERSITY