Skip to content

2. Testing Principles & Approach

← Previous: Purpose & Objectives | Back to QA Strategy | Next: QA Roles & Responsibilities →

Quality Assurance at Spline Studio is guided by a set of principles that ensure testing activities are efficient, risk-focused, and aligned with product delivery goals. These principles define how QA work is planned and executed across projects.

flowchart LR
    A["QA Principles"] --> B["Risk-Based Testing"] & C["Early QA Involvement"] & D["Structured & Exploratory Testing"] & E["Automation-Assisted Regression"] & F["Evidence-Based Release Decisions"]
    B --> B1["Risk prioritization"] & B2["Critical areas focus"]
    C --> C1["Early validation"] & C2["Reduced defects"]
    D --> D1["Defined coverage"] & D2["Edge case discovery"]
    E --> E1["Regression stability"] & E2["Faster verification"]
    F --> F1["Quality indicators"] & F2["Release confidence"]

     A:::Pine
     B:::Aqua
     C:::Rose
     D:::Peach
     E:::Ash
     B1:::Aqua
     B2:::Aqua
     C1:::Rose
     C2:::Rose
     D1:::Peach
     D2:::Peach
     E1:::Ash
     E2:::Ash
    classDef Aqua stroke-width:1px, stroke-dasharray:none, stroke:#46EDC8, fill:#DEFFF8, color:#378E7A
    classDef Rose stroke-width:1px, stroke-dasharray:none, stroke:#FF5978, fill:#FFDFE5, color:#8E2236
    classDef Peach stroke-width:1px, stroke-dasharray:none, stroke:#FBB35A, fill:#FFEFDB, color:#8F632D
    classDef Pine stroke-width:1px, stroke-dasharray:none, stroke:#254336, fill:#27654A, color:#FFFFFF
    classDef Ash stroke-width:1px, stroke-dasharray:none, stroke:#999999, fill:#EEEEEE, color:#000000

2.1 Risk-Based Testing

Testing activities are prioritized based on risk and potential business impact. QA efforts focus on critical product functionality, complex system areas, and components that historically demonstrate a higher probability of defects.

This approach ensures that testing resources are used efficiently and that the most important product behaviors are validated first.

2.2 Early QA Involvement

QA is involved as early as possible in the development lifecycle. Early participation allows QA engineers to review requirements, clarify expected behavior, identify potential risks, and prepare test scenarios before implementation begins.

Early involvement helps reduce misunderstandings, prevents defects, and improves overall development efficiency.

2.3 Combination of Structured and Exploratory Testing

Spline Studio combines structured testing with exploratory testing techniques.

Structured testing ensures coverage of defined requirements and acceptance criteria through test cases and checklists.

Exploratory testing allows QA engineers to investigate edge cases, unexpected system behavior, and usability issues that may not be captured in predefined tests.

Together, these approaches improve overall defect detection.

2.4 Automation-Assisted Regression

Automation is used to support regression testing and improve the stability of product releases. Critical user flows and frequently executed scenarios are gradually automated to ensure faster verification and consistent results across releases.

Manual testing continues to play an important role in validating new functionality, user experience, and complex system interactions.

2.5 Evidence-Based Release Decisions

Release readiness decisions are based on objective testing results and quality indicators. QA provides visibility into testing outcomes, defect status, and coverage levels to support informed release decisions.

This approach ensures that releases are evaluated based on measurable quality signals rather than assumptions.

← Previous: Purpose & Objectives | Back to QA Strategy | Next: QA Roles & Responsibilities →