Test Levels Flashcards
How does each test level be described in terms of?
Objectives.
Test Types involved (functional, nonfunctional and structural). The work product being referenced for deriving the test cases (test basis). The test object (what’s being tested). Typical defects and failures found. Test harness requirements and tool support. Responsibilities and environment requirements.
What is component testing?
It is the first stage in testing and often described, consists of testing and debugging small programming work components that are separately testable.
What is the aim of component testing?
To determine whether a module, system or function, subroutine, of module works in isolation, before we try and integrate it into the system. Only once we are happy with the component and ensure it behaves as expected does t then make sense to combine it with the other components.
Objective of Component Testing.
Find and remove defects.
Component testing does not need to log the incident due to…
It being small bugs such as a missing semi colon so it would just add it in as to save time…
what is an approach to component testing?
TDD (test driven development) or Test-First approach, highly iterative and is based on cycles of developing test cases and then building small pieces of code and executing the component tests, correcting any issues and iterating until they pass. Aim to drive out the functionality the software actually needs, rather than what developers think it probably ought to have.
What is the aim of Component Integration Testing?
To ensure that all the major interfaces and interactions between all the individual components. OnlyHOW the components communicate with each other! (Not it’s functionality)
What are the Component Integration Strategies? 4
Non-incremental (big-bang). Architecturally(top-bottom, bottom-top). Functional Integration.
Explain big-bang Integration.
Integrate all components at once. Not recommended as it may be difficult to identify which link has failed and result to be more costly in the long run.
Explain Top-Down Integration
Add components one at a time, based on architecture. Begin testing with components highest in the hierarchy. Components are added in descending hierarchial order. Use stubs to stimulate lower-level components. Identifies defects in the architecture.
Explain bottom-up Integration.
Add components one at a time on architecture. Begin with testing with components lowest in the hierarchy. Components are added in ascending hierarchical order. Drivers are used to stimulate higher level components. Higher risk that architure may be incorrect.
Explain functional integration.
Select a specific area of functional capability, sequence of transaction processing or other other aspect of the system. Integrate the components needed for that part of the system. Test to determine if the components work correctly together. Good as tests real business scenarios such as most-used path or critical business function.
What is system testing?
Tests the end to end integrated system as defined by the scope of a development project or programme. Test the behaviour of a whole system or product.
What is system integration testing?
Testing between systems and hardware and software. Series of systems.
What is acceptance testing?
Establish confidence in a system.
