Skip to content

6. Test Levels

← Previous: Test Environments & Test Data | Back to QA Strategy | Next: Project QA Preparation Phase →

Testing activities within Spline Studio projects are performed across multiple levels to ensure that software quality is validated progressively throughout the development lifecycle.

Each testing level focuses on validating the system from a different perspective, starting from individual components and progressing toward full system behavior and user workflows.

6.1 Test Levels Pyramid

flowchart TB
    A["Unit Testing"] --> B["Integration Testing"]
    B --> C["System Testing"]
    C --> D["Acceptance Testing"]

    style A fill:#FFCDD2,color:#000000
    style B fill:#FFE0B2,color:#000000
    style C fill:#FFF9C4,color:#000000
    style D fill:#C8E6C9,color:#000000

6.2 Unit Testing

Unit testing focuses on verifying the behavior of individual components or pieces of code in isolation.

These tests are typically written and maintained by developers as part of the development process. Unit tests help identify issues early in the development lifecycle and ensure that code behaves as expected before integration with other system components.

Primary Responsibility: Developers

6.3 Integration Testing

Integration testing verifies the interaction between different system components, services, or external integrations.

This level of testing ensures that data flows correctly between modules and that integrated components work together as intended.

Integration testing may be performed by developers, QA engineers, or both depending on project architecture and complexity.

Primary Responsibility: Developers and QA Engineers

6.4 System Testing

System testing validates the behavior of the complete application as a whole.

This level of testing focuses on verifying functional requirements, user workflows, system stability, and overall system behavior. System testing is typically the primary responsibility of QA engineers.

Primary Responsibility: QA Engineers

6.5 Acceptance Testing

Acceptance testing focuses on validating that the system meets business requirements and is ready for delivery or release.

This level of testing may involve QA engineers, product managers, project stakeholders, or clients to confirm that the implemented functionality meets the intended business objectives.

Primary Responsibility: QA Engineers, Product Managers, Stakeholders

← Previous: Test Environments & Test Data | Back to QA Strategy | Next: Project QA Preparation Phase →