|
Following stages shall be completed in the test analysis:
Product units shall be analyzed in detail with the help of Client's development and support team.
Test execution can be described as the task of inputting data into an application and checking the result of any processing done by that application by comparing them to expected values, devised by the test designers.
Review and User Approval
Each Test Specification must be approved by the Client users involved in the analysis and design stages, before the testing can be performed.
Issues and the resolution must be documented and retained as evidence of the review.
Upon approval of the test specification documentation the test analyst is to arrange a follow up meeting with the test engineers to formally hand-over all documentation and allow for any questions or comments.
Testing
Following stages shall be completed in the testing:
Baseline tests are performed using baseline test cases (current GUI), to provide a benchmark for later stages of testing.
GUI tests are performed using GUI test cases, will prove that all changes made to code have not affected application functionality or processing, and that operating in an environment also has no affect.
All test results must be approved by the Client users involved in the analysis and design stages. Issues and the resolution must be documented and retained as evidence of the review.
Hand-over
This phase will involve passing over to the relevant Client personnel any information that may be useful to them. This will include the Test Specification, test plans, test data files, and details of any production problems that have been found during testing.
Set up test framework: During this phase the test framework is set up to conform to the design as made in "Analysis of test framework".
Making stubs and drivers: This phase is undertaken simultaneously with the phase "Defining test-ifs". This phase might utilise standard software testing tools.
Software test tools will be used to execute test scripts and test clusters . Other tools might be necessary in order to direct the test. Thought should be given to the routines for loading the initial database, selecting the test environments, and the mid-term saving of data.
Stubs and drivers may be required to simulate the behavior of other modules/systems called by or called from the application under test. This may be necessary either to avoid test failures due to these other modules/systems or because these other modules/systems are (not yet) available in the test environment.
Make/extend navigation general and implementation of test actions: This phase is interlinked with the phase "Set up test sheets and specify test actions" from the test analysis task area.
Testing test clusters: The test scripts and test clusters are, themselves, a form of software, and these need to be tested with the test data to ensure that they produce valid test results.
Delivery test products and documentation: In this phase, the developed test material is delivered/installed in the environment in which the application is to be tested.
Execution of test clusters: In this phase, tests will be executed with the available test products, in order to allow the client to accept test products. |
