Integration software testing pdf
Mistakes can be made at each of these stages, in the information handling, or in the transfer of the information from one stage to another. Also, the integration of testing throughout the lifecycle provides a way to verify and trace consistencies among the stages. These sub-objectives of testing at each stage will then achieve the overall objective of ensuring high quality software.
There are many methods to do this [Dav93], most commonly inspections and prototyping. We do not advocate any particular method, but emphasize that some method should be employed, and the requirements should be evaluated before design starts. Test requirements should be written to state testing criteria for the software system and high level test plans should be developed to outline the testing strategy. The test plan should also include the scope and objectives for testing at each stage.
This high level test plan will be referenced in the later detailed test plans. The testing requirements should describe support software needed for testing at each stage. Project test plans and representative system test scenarios should be built to show that the system meets the requirements.
The test scenarios will also provide feedback to the software architectural designers and help them develop a design that is easily testable. The software design should represent the software system functions so that they can be transformed into executable programs [Som92].
Testing at this stage should help to validate the design and interface. The major test preparation goal at system and software design stage is to prepare for acceptance and usability testing. An acceptance test plan is created that includes acceptance test requirements, a test criterion, and a testing method.
The major test in uence goal at this stage is to in uence the design of the user interface. Usability tests or an interface prototype should be designed to clarify the customer's interface desires. Usability testing is carried out when the user interface is an integral part of the system.
Many problems in large software systems arise from subsystem interface mismatches. The major test action goal at the intermediate design stage is to avoid mismatches of interfaces in the subsystems. To prepare for testing at the later stages, test support tools such as test drivers, stubs, and testing measurement tools should be acquired or built.
The major test in uence goal at this stage is to in uence detailed design. It also suggests an ordering for implementation and unit testing. The major test action goal at detailed design stage is to make sure that all test materials are ready for testing when the modules are written.
Preparation should be for both unit testing and integration testing. The major test in uence goal is to in uence the coding and unit and integration testing. Faults should be located and reported properly and promptly. Testing results should be well documented. Unit test results and problems should be reported properly for further processing. Designers and developers whose duties are becoming lighter at this point should be made available to help the testing team. The major test preparation goal during coding and unit testing is to prepare for integration and system testing.
After system testing, the software system is delivered to the customer. The major test action goal at the integration and system testing stage is to perform integration testing, system testing, acceptance testing and usability testing. Citation Type. Has PDF. Publication Type. More Filters. View 1 excerpt, cites background. Robustness testing for software components. The world's expanded reliance on programming enabled automated frameworks has elevated real worries about programming and coding dependability furthermore, configuration.
New practical approaches and … Expand. View 1 excerpt, cites methods. State Based Robustness Testing for Components. Notes Theor. An approach of test sequence generation for component-based software. Proactive model based testing and evaluation for component-based systems. A model-based testing technique for component-based real-time embedded systems.
View 1 excerpt. Case studies on testing object-oriented programs. Citation Type. Has PDF. Publication Type. More Filters. View 1 excerpt, cites background. Robustness testing for software components. The world's expanded reliance on programming enabled automated frameworks has elevated real worries about programming and coding dependability furthermore, configuration. New practical approaches and … Expand. View 1 excerpt, cites methods. State Based Robustness Testing for Components.
Notes Theor. An approach of test sequence generation for component-based software. Proactive model based testing and evaluation for component-based systems.
A model-based testing technique for component-based real-time embedded systems. View 1 excerpt. Case studies on testing object-oriented programs.
0コメント