9.2.4 Testing and evaluating Flashcards
List and describe the 3 levels of testing
- Module - testing that each module and subroutine functions correctly.
- Program - testing that the overall program, including associated modules/subroutines, work together as expected.
- System - testing that the overall system, including all programs and the interfaces between programs.
What are the elements included in System Level Testing?
- Software – The program must work with different operating systems and software on the computer
- Data – The program must be tested with different volumes and types of data, with expected and unexpected inputs
- Hardware – The program must be tested at minimum hardware requirements AND above, it should also be tested with external hardware such as printers
- Personnel and Procedures – The program should cater to users of different technological skill levels and the user interface must be evaluated
In the context of testing, what is a driver?
A driver is a section of code that calls the module to be tested (usually not a part of the final code). The driver might generate its own random test data and evaluate the results, or use an existing set of test data (perhaps loaded from a file).
They are used in the Module level of testing.
How can live test data be used to ensure that the testing environment reflects the expected environment in which the new system will operate?
- Large File Sizes – Highlights inefficient code and issues associated with data access
- Mix of Transaction Types – Completing transactions in different orders should not cause issues, sometimes problems can arise when multiple programs try to access the same database
- Response Times – Ideal response time is 0.1 and if the wait time is longer, feedback should be provided
- Volume Data (Load Testing) – This can be done with CASE tools and a laboratory of computers
- Existing Systems – Test the effect of the new system on the existing systems in the environment into which it will be installed.
What are the 5 components of a testing report?
- Test requirements - what needs to be tested?
- Test plan - how are the tested implemented?
- Test data - what are the test inputs and expected outputs?
- Test results - do the actual results match the expected results?
- Recommendations - what needs to be done now?
What is a post-implementation review?
A process involving demonstrating the final product to the client to confirm and describe how it meets the requirements.
A smaller project might be an informal process involving a meeting and a desmonstration. For a larger project, a more formal process of acceptance testing may be undertaken.