System testing
System testing checks the complete, integrated system against its requirements. We test end-to-end workflows and quality characteristics such as performance and security, in an environment as close to production as possible.
What system testing covers
- FunctionalEnd-to-end user journeys
- Non-functionalPerformance, security, usability
- IntegrationAPIs, databases, third parties
- End-to-endComplete workflows
What is system testing?
System testing focuses on the behaviour and capabilities of a whole system or product, often including functional testing of end-to-end tasks and non-functional testing of quality characteristics.
It checks that the complete, integrated system meets its specified requirements and works correctly in an environment that represents real use.
Source: ISTQB Foundation Level syllabus v4.0. The level before this one is integration testing; the one after is acceptance testing.
System testing levels
| Level | Description | Phase |
|---|---|---|
| Alpha testing | Internal testing by the development team or internal QA in a controlled environment, before external release. | Pre-release |
| Beta testing | Testing by a limited group of real users in their own environment, for feedback on usability, performance and real-world use. | Limited release |
| End-to-end testing | Complete workflows from start to finish, simulating real user scenarios across every integrated component. | Full workflow |
ISTQB places alpha and beta testing under acceptance testing. We list them here because they run on the complete system, straight after system testing.
System testing process
Environment setup
Configure a production-like environment with every integrated component, database, third-party service and infrastructure dependency.
Test scenario design
Write end-to-end scenarios for the critical user journeys and business workflows, covering functional and non-functional requirements.
Functional validation
Run functional tests that check features, integrations and business logic across the complete system.
Non-functional testing
Assess quality characteristics: performance, security, usability, reliability and scalability under realistic load.
Defect resolution and regression
Retest the fixes, run regression tests so a fix does not break something else, and confirm the system is ready for release.
System testing coverage
Functional coverage
Every feature works when integrated, across complete user journeys and business processes.
- End-to-end user journeys
- Business processes
- Cross-module integration
- Data passing between modules
Non-functional coverage
Quality characteristics beyond basic functionality.
- Performance under load
- Security vulnerabilities
- Usability and accessibility
- Reliability and stability
Integration coverage
All components, external services and third-party integrations work together.
- API integrations
- Database interactions
- Third-party services
- Hardware interfaces
The non-functional side is covered in depth on our non-functional testing page, and functional testing on functional testing.
How BetterQA does system testing
We test the product as your users will meet it, end to end, in an environment set up to match production, and report each defect with what it means for the release.
Engineers who test for a living
50+ QA engineers, working since 2018. People plan and run the system testing and report what the results mean for your release.
Bugs you can act on
Every defect we find is written up in BugBoard, our own test management tool, or in your tracker, with steps to reproduce, the expected and actual result, and the environment.
A certified process
ISO 9001 for quality management and ISO 27001:2022 for information security. See our certifications.
How an engagement works
- €20-45 per hour
- First month is a trial
- First two weeks complimentary if you are not happy
- 30 days' notice after that
System testing: common questions
What is system testing?
A test level that checks the complete, integrated system against its requirements, including end-to-end functional tests and non-functional tests such as performance and security.
What is the difference between system testing and functional testing?
Functional testing is a type of testing that can happen at any level. System testing is a level: it tests the whole system, functionally and non-functionally.
What is the difference between system testing and integration testing?
Integration testing checks the connections between components. System testing checks the complete product once everything is connected.
Who performs system testing?
Usually an independent QA team, separate from the developers who built the system, in a production-like environment.
Is end-to-end testing the same as system testing?
End-to-end testing is part of system testing: it follows complete workflows across every component. System testing also covers non-functional characteristics.
What does it cost?
Our rate is €20-45 per hour. For ongoing work the first month is a trial, the first two weeks are complimentary if you are not happy, and after that it is 30 days' notice.
Need system testing?
Tell us what your system does and what it connects to. We will set up a production-like environment and test it end to end before your users do.