Test Levels

Component Testing Integration Testing System Testing Acceptance Testing

(UAT, OAT, CAT, RAT,
alpha and beta testing)
focuses on components that focuses on interactions between
both focus on the behavior and capabilities of a whole system or product
are separately testable components or systems
- Reducing risk
- Reducing risk - Verifying if the functional and non-functional - Establishing confidence in the quality of the
- Reducing risk - Verifying if the functional and non-functional behaviors of the system are as designed and system as a whole
- Verifying if the functional and non-functional behaviors of the interfaces are as designed and specified
Objectives

behaviors of the component are as designed
and specified
- Building confidence in the component quality
- Finding defects in the component
- Preventing defects from escaping to higher test
levels
specified
- Building confidence in the quality of the interfaces
- Finding defects (which may be in the interfaces
themselves or within the component or system)
- Preventing defects from escaping to higher test
levels
- Validating that the system is complete and will
- Validating that the system is complete and will work as expected
work as expected
- Verifying that the functional and non-
- Building confidence in the quality of the system as functional behaviors of the system are as
a whole designed and specified
- Finding defects
- Preventing defects from escaping to higher test
levels or production

- Software and system design - System and software requirements - Business processes
- Sequence diagrams specification (functional and non-functional) - User or business requirements
- Risk analysis reports
Test basis

- Detailed design - Interface and communication protocol - Regulations, legal contracts and standards
- Code specifications - Use cases - Use cases and/or user stories
- Data model - Use cases - Epics and user stories - System requirements
Attributes of test levels

- Component specification - Architecture at component or system level - Models of system behavior - System or user documentation
- Workflows - State diagram - Installation procedures
- External interface definitions - System and user manuals - Risk analysis reports

- System under test

- Subsystems
- Applications - System configuration and configuration data
Test objects

- Components, units or modules - Databases

- Hardware/software systems - Business processes for a fully integrated
- Code and data structures - Infrastructure system
- Operating systems
- Classes - Interfaces - Recovery systems and hot sites
- System under test (SUT)
- Database modules - APIs - Operational and maintenance processes
- System configuration and configuration data
- Microservices - Forms
- Reports
- Existing and converted production data

- Incorrect data, missing data, or incorrect data

encoding - Incorrect data calculations
- Inconsistent message structures between systems - Incorrect or unexpected system functional or non- - System workflows do not meet business or
Typical defects and

functional behavior user requirements

- Incorrect functionality (not as described in - Incorrect sequencing or timing of interface calls
design specification) - Incorrect control and/or data flows within the - Business rules are not implemented correctly
- Interface mismatch system
failures

- Data flow problems - System does not satisfy contractual or

- Failures in communication between components /
- Incorrect code and logic systems
- Unhandled or improperly handled communication
failures between components / systems
- Incorrect assumption about the meaning, units, or
boundaries of the data being passed between
components / systems
- Failure to comply with mandatory security regulations
- Failure to properly and completely carry out end-
to-end functional tasks
- Failure of the system to work properly in the
system environment(s)
- Failure of the system to work as described in
system and user manuals
regulatory requirements
- Non-functional failures such as security
vulnerabilities, inadequate performance
efficiency under high loads, or improper
operation on a supported platform

There are also specific approaches and responsibilities for each of the above test levels.
https://github.com/fromlegaltotech