Page 297 - DCAP305_PRINCIPLES_OF_SOFTWARE_ENGINEERING

Unit 14: Flow Based Testing Process

14.6 Summary Notes

• Software Testing is the process of executing a program or system with the intent of finding
errors.

• The local data structure is examined to ensure that data stored temporarily maintains its
integrity during all steps in an algorithm’s execution.
• Good design dictates that error conditions be anticipated and error handling set up to
reroute or cleanly terminate processing when an error does occur.
• Stubs serve to replace modules that are subordinate (called by) the component to be tested.
• Integration testing is a systematic technique for constructing the program true while at
the same time conducting tests to uncover errors associated with facing.
• A test plan can be defined as a document describing the scope, approach, resources, and
schedule of intended testing activities.
• Test cases are designed by the stepwise elaboration and refinement of the identified test
conditions using test techniques identified in the test strategy.

14.7 Keywords

Execution Testing: Execution testing can be conducted in any phase of the system development
life cycle.
Quick Emulator (QEMU): The QEMU stands for “Quick Emulator” and is a processor emulator
that relies on dynamic binary translation to achieve a reasonable speed while being easy to port
to new host CPU architectures.

Recovery Testing: It is a system test that forces the software to fail in a variety of ways and
verifies that recovery is properly performed.
Security Testing: It attempts to verify that protection mechanisms built into a system will, in
fact, protect it from improper penetration.
Stress Testing: It executes a system in a manner that demands resources in abnormal quantity,
frequency, or volume.

1. Prepare a flow chart for the states of flow based testing.
2. Write a test case for testing software.

14.8 Review Questions

1. Explain the flow based testing process.

2. How many levels of testing?
3. What is the different between the top-down and bottom-up integration testing approaches?
4. What is the system testing? How to different the integration testing?
5. Explain the recovery testing, security testing, stress testing, performance testing.
6. How do we plan a testing process?
7. Discuss the test case specifications.

8. What is the execution and analysis? How to use the execution testing with example?
9. Discuss the logging and tracking.
10. Define error tracking.

LOVELY PROFESSIONAL UNIVERSITY 291