Software Testing

Ch-17: Software Testing Strategies (reefer book by roger s. pressmen for these topic)

up to 17.1.3 (pg: 449-454), 17.3 (pg:456-465), 17.6, 17.7 (pg:467-472)

Note: You can whatsapp me the doubts related to this topic.

Overview of chapter (for detail understanding.. refer book)

What is Latent defect?

Latent defect: This defect is an existing defect in the system that does not cause any failure as the exact set of conditions has never been met

After studying this topic, set of questions should be answered and forwarded to me in doc file through whatsapp.

Objective Questions

1. In software quality assurance work there is no difference between software verification and software validation.

2. The best reason for using Independent software test teams is thatA) software developers do not need to do any testingB) strangers will test the software mercilesslyC) testers do not get involved with the project until testing beginsD) the conflicts of interest between developers and testers is reduced

3. What is the normal order of activities in which traditional software testing is organized?A) integration testingB) system testingC) unit testingD) validation testingE) c, a, d, and b

4. Which of the following strategic issues needs to be addressed in a successful software testing process?A) conduct formal technical reviews prior to testingB) specify requirements in a quantifiable mannerC) use independent test teamsD) wait till code is written prior to writing the test planE) both a and b

5. Top-down integration testing has as it's major advantage(s) thatA) low level modules never need testingB) major decision points are tested earlyC) no drivers need to be writtenD) no stubs need to be writtenE) both b and c

6. Bottom-up integration testing has as it's major advantage(s) thatA) major decision points are tested earlyB) no drivers need to be writtenC) no stubs need to be writtenD) regression testing is not required

7. Regression testing should be a normal part of integration testing because as a new module is added to the system newA) control logic is invokedB) data flow paths are establishedC) drivers require testingD) all of the aboveE) both a and b

8. Smoke testing might best be described asA) bulletproofing shrink-wrapped softwareB) rolling integration testingC) testing that hides implementation errorsD) unit testing for small programs

9. B) rolling integration testing10. (T/F) The focus of validation testing is to uncover places that s user will be able to

observe failure of the software to conform to its requirements.11. (T/F) Software validation is achieved through a series of tests performed by the

user once the software is deployed in his or her work environment.12. Acceptance tests are normally conducted by the

A) developerB) end usersC) test teamD) systems engineers

13. Security testing attempts to verify that protection mechanisms built into a system protect it from improper penetration.

14. Stress testing examines the pressures placed on the user during system use in extreme environments.

15. Performance testing is only important for real-time or embedded systems.16. (T/F) Debugging is not testing, but always occurs as a consequence of testing.

Questions (this should be hand-written and send me the pic and take picture and paste in the doc)

1. Show the software testing steps with the help of diagram2. Explain the need of performing Performance testing.3. How unit testing is performed.4. When unit tested modules are integrated, do we need to perform testing again.

Justify your answer. (if yes- name the testing technique with justification)5. Explain unit testing? How stubs and drivers are used in unit testing.6. What is the overall strategy for software testing?

Differentiate between1. Verification vs. Validation2. Stubs vs. Drivers3. Bottom up Integration Testing vs. Top up Integration testing 4. Smoke testing vs. system testing5. Alpha testing vs. beta testing6. Stress testing vs. security testing