System Testing (Pre-Production Validation)

← Previous: Smoke Testing | Back to Testing Workflow | Next: Regression Testing →

The goal of this phase is to validate the new functionality within the complete system environment before the release.

Testing at this stage ensures that newly implemented features work correctly when integrated with the full application and related services.

Objectives

Validate new functionality in complete system environment
Verify feature integration with existing system
Test end-to-end user workflows
Identify integration or system-level issues
Confirm system stability with new changes

Testing Environment

Testing is performed in the Pre-Production environment, which closely mirrors the production environment.

QA Activities

flowchart TD

A[Test Case Execution]
B[Integration Validation]
C[System Workflow Testing]
D[Exploratory Testing]

A --> E[System Validation]
B --> E
C --> E
D --> E

    style A fill:#E3F2FD,color:#000000
    style B fill:#E8F5E9,color:#000000
    style C fill:#FFF3E0,color:#000000
    style D fill:#E1F5FE,color:#000000
    style E fill:#FFCDD2,color:#000000

During this phase QA performs the following activities:

Test Case Execution - executing prepared test cases related to the implemented functionality - validating new features within the complete system context - testing critical user workflows end-to-end - verifying data flow across system components

Integration Validation - validating the interaction between newly developed features and existing system components - testing integration points and data exchange - verifying API interactions and service communication - validating database operations and data consistency

System Workflow Testing - testing complete user journeys across the system - validating business processes end-to-end - verifying cross-feature functionality - testing system behavior under realistic scenarios

Exploratory Testing - performing exploratory testing to identify unexpected system behavior - investigating edge cases and boundary conditions - evaluating system performance and responsiveness - identifying usability or UX concerns

Testing is performed using both structured test execution and exploratory testing techniques.

Entry Criteria

Before system testing begins:

Smoke tests passed successfully
Build deployed to Pre-Production environment
Test cases prepared for new functionality
Test data and accounts available
Environment stable and configured correctly

In addition to these core requirements, additional entry criteria may be defined depending on project-specific needs and constraints.

Quality Gates

All planned test cases are executed and results are documented
Integration points are verified and work correctly
End-to-end scenarios are executed, system is stable
No critical/blocker defects remain
All test results and status are communicated to stakeholders

Testing Scope

System testing focuses on:

New Functionality – recently implemented features
Feature Integration – how new features integrate with existing system
End-to-End Workflows – complete user journeys
System Behavior – overall application stability
Data Integrity – data consistency across operations

Outcome

The outcome of this phase typically includes:

validated system behavior of newly implemented functionality
confirmation that new features work correctly within the full system environment
identification of any remaining issues before release preparation
documented test results and coverage
quality assessment for release decision

Supporting Guides & Templates

System Testing Entry Criteria Guide – Defines conditions required to start system testing, including verification of full release scope deployment and successful smoke testing.

Test Plan Management Guide – Describes how to create, execute, and track test plans, including test runs and result management.

**Test Plan in Xray – Guidelines for creating and managing test plans in Xray.

← Previous: Smoke Testing | Back to Testing Workflow | Next: Regression Testing →