2.2-Test levels
2.2.1 - Component / Unit testingt
Focuses on components that are separately testable.
Typical test basis
- Detailed design
- Code
- Data model
- Component specification
Typical defects and failures:
- Incorrect functionality
- Data flow problems
- Incorrect code and logic
Typical test objects:
- Components, units or modules
- Code and data structures
- Classes
- Database modules
Summary:
- Performed by developers who have coded the component.
- For agile teams, Test Driven Development (TDD) is the most common practice.
- Developed and tested using development environment.
2.2.2 - Integration Testing
Focuses on the interaction between components or systems.
This stage should be focuses on the communication between the modules, not the functionality of the individual modules because that part should be covered in unit tests.
Typical test basis
- Architecture at component or system level
- Sequence diagrams
- Interface and communication protocol specifications
- Use cases
- Workflows
Typical defects
- Interfaces mismatch
- Failures in communication between components
- Incorrect timing, sequencing or interface calls
Typical test objects
- Sub-systems
- Database implementation
- Infrastructure
- Interfaces
- API´s
- Microservices
2.2.3 - System Testing
Typical test basis
- Use cases
- Epics and user stories
- Models of system behavior
- State diagrams
- System and user manuals
Typical defects
- Incorrect calculations
- Incorrect or unexpected system functional or non-functional behavior
- Failure of the system to work properly
- Failure of the system to work as described in system and user manual
Typical test objects
- Applications
- Hardware/Software systems
- O.S
- System Under Test (SUT)
2.2.4 - Acceptance Testing
Then purpose of acceptance testing is to validate the system is fit for purpose.
Typical test basis
- Business processes
- User or business requirements
- Risk analysis reports
- Installation procedures
- Legal contracts or standards
Typical defects
- System workflows don´t meet business or user requirements
- Business rules are not implemented correctly
- Non-functional failures such as security vulnerabilities, performance efficiency or improper operations.
Typical test objects
- System Under Test
- Forms
- Reports
- Recovery systems and hot sites
- Existing and converted production data
Alpha and Beta testing:
Alpha
Is performed at the developing organization´s site, not by the development team, but by potencial or existing customer, operators or independent test team.
Beta
Is performed by potential or existingn customer or operators at their own locations.
Note
Beta testing may come after Alpha testing or may occur without any preceding alpha testing.
Last update:
2022-08-29