The document describes the software testing process which has two goals: 1) to demonstrate that the software meets requirements through validation testing and 2) to discover defects through defect testing. It discusses the typical stages of development, release, and user testing and how testing involves a mixture of manual and automated methods. Testing aims to show that a program works as intended and finds defects before use.
The document describes the software testing process which has two goals: 1) to demonstrate that the software meets requirements through validation testing and 2) to discover defects through defect testing. It discusses the typical stages of development, release, and user testing and how testing involves a mixture of manual and automated methods. Testing aims to show that a program works as intended and finds defects before use.
The document describes the software testing process which has two goals: 1) to demonstrate that the software meets requirements through validation testing and 2) to discover defects through defect testing. It discusses the typical stages of development, release, and user testing and how testing involves a mixture of manual and automated methods. Testing aims to show that a program works as intended and finds defects before use.
The document describes the software testing process which has two goals: 1) to demonstrate that the software meets requirements through validation testing and 2) to discover defects through defect testing. It discusses the typical stages of development, release, and user testing and how testing involves a mixture of manual and automated methods. Testing aims to show that a program works as intended and finds defects before use.
Download as PPTX, PDF, TXT or read online from Scribd
Download as pptx, pdf, or txt
You are on page 1/ 13
Software Quality Engineering
Software Testing Process
BS-Software Engineering 6 B & C
Software Testing Process
• Testing is intended to show that a program does what it is intended to
do and to discover program defects before it is put into use. • When you test software, you execute a program using artificial data. You check the results of the test run for errors, anomalies, or information about the program’s non-functional attributes. Software Testing Process • The testing process has two distinct goals:
1. To demonstrate to the developer and the customer that the software
meets its requirements. – For custom software, this means that there should be at least one test for every requirement in the requirements document. – For generic software products, it means that there should be tests for all of the system features, plus combinations of these features, that will be incorporated in the product release. Software Testing Process
2. To discover situations in which the behavior of the software is
incorrect, undesirable, or does not conform to its specification. – These are a consequence of software defects. – Defect testing is concerned with rooting out undesirable system behavior such as system crashes, unwanted interactions with other systems, incorrect computations, and data corruption. Software Testing Process
• The first goal leads to validation testing, where you expect the system to perform correctly using a given set of test cases that reflect the system’s expected use. • The second goal leads to defect testing, where the test cases are designed to expose defects. • During validation testing, you will find defects in the system; during defect testing, some of the tests will show that the program meets its requirements. Software Testing Process • Test cases are specifications of the inputs to the test and the expected output from the system (the test results), plus a statement of what is being tested. • Test data are the inputs that have been devised to test a system. • Test data can sometimes be generated automatically, but automatic test case generation is impossible, as people who understand what the system is supposed to do must be involved to specify the expected test results. Software Testing Process
• However, test execution can be automated.
• The expected results are automatically compared with the predicted results so there is no need for a person to look for errors and anomalies in the test run. Model For Software Testing Process Software Testing Process
• Typically, a commercial software system has to go through three stages
of testing: 1. Development testing 2. Release testing 3. User testing Software Testing Process 1. Development Testing: • The system is tested during development to discover bugs and defects. • System designers and programmers are likely to be involved in the testing process
2. Release Testing: • A separate testing team tests a complete version of the system before it is released to users. • The aim of release testing is to check that the system meets the requirements of system stakeholders. Software Testing Process 3. User Testing:
• Users or potential users of a system test the system in their own
environment. • For software products, the ‘user’ may be an internal marketing group who decide if the software can be marketed, released, and sold. • Acceptance testing is one type of user testing where the customer formally tests a system to decide if it should be accepted from the system supplier or if further development is required. Software Testing Process
• In practice, the testing process usually involves a mixture of manual and
automated testing. • In manual testing, a tester runs the program with some test data and compares the results to their expectations. • They note and report discrepancies to the program developers. • In automated testing, the tests are encoded in a program that is run each time the system under development is to be tested. Software Testing Process • This is usually faster than manual testing, especially when it involves regression testing—re-running previous tests to check that changes to the program have not introduced new bugs. • The use of automated testing has increased considerably over the past few years. • However, testing can never be completely automated as automated tests can only check that a program does what it is supposed to do.
