Skip to content

8.4. Feature Testing

← Previous: Test Design | Back to Testing Workflow | Next: Bug Fix Verification →

Once a feature or functionality is implemented and deployed to the testing environment, QA begins functional validation of the feature.

The goal of this phase is to verify that the implemented functionality behaves according to the defined requirements, design specifications, and acceptance criteria.

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

8.4.1 Objectives

  • Validate implemented functionality against requirements
  • Execute prepared test cases
  • Perform exploratory testing
  • Identify and document defects
  • Verify acceptance criteria fulfillment

8.4.2 Testing Environment

Feature testing is typically performed in the DEV server. Depending on the project setup, early validation may also occur in the development environment, while later stages of validation may involve the staging environment.

8.4.3 QA Activities

flowchart TB
    A["Structured Test Execution"] --> B["Exploratory Testing"]
    B --> C["Acceptance Criteria Validation"]

    C --> D["Defect Documentation"]
    D --> E["Test Case Updates"]

    E --> A

    subgraph QA Activities Flow
        A
        B
        C
        D
        E
    end

    style A fill:#C8E6C9,color:#000000
    style B fill:#E3F2FD,color:#000000
    style C fill:#FFF9C4,color:#000000
    style D fill:#FFCDD2,color:#000000
    style E fill:#F3E5F5,color:#000000
During this phase QA performs the following activities:

Structured Test Execution

Executing previously prepared test cases to validate implemented functionality.

  • running test cases in defined sequence
  • verifying expected results match actual behavior
  • documenting test execution results
  • capturing evidence (screenshots, logs) where appropriate

Exploratory Testing

Performing exploratory testing to identify unexpected behavior, edge cases, or usability issues.

  • investigating system behavior beyond predefined test cases
  • testing edge cases and boundary conditions
  • evaluating user experience and usability
  • identifying potential improvements

Acceptance Criteria Validation - validating that the implemented feature meets defined requirements and acceptance criteria - verifying all acceptance criteria are satisfied - confirming feature completeness - identifying gaps or missing functionality

Defect Documentation - documenting identified defects and reporting them through the defect tracking system - providing clear reproduction steps - including supporting evidence (screenshots, logs, videos) - classifying defects by severity and priority

Test Case Updates - identifying potential improvements or updates required for existing test cases - documenting new scenarios discovered during testing - updating test cases based on implementation details - refining test coverage as needed

Detailed entry and exit criteria for feature testing may be documented separately in dedicated QA guidelines.

8.4.4 Entry Criteria

Before feature testing begins: - All tasks related to the feature are in QA Review status - Feature implemented and deployed to testing environment - Test cases prepared and ready for execution - Test data and test accounts available - Requirements and acceptance criteria clearly defined - Environment stable and accessible

8.4.5 Quality Gates

  • All planned test cases are executed and results are documented
  • Feature acceptance criteria are confirmed
  • Exploratory testing is performed
  • All critical and high-priority defects are documented
  • No blocking defects remain for transition to the next stage
  • Feedback is provided to the development team and stakeholders
  • Test results communicated to stakeholders
  • Feature status (pass/fail/blocked) clearly indicated

8.4.6 Supporting Guides & Templates

QA Test Execution Guide - Describes how test execution is performed on the project, including test runs, result tracking, and evidence collection.

Test Execution in Xray - Guidelines for executing and tracking test runs in Xray

← Previous: Test Design | Back to Testing Workflow | Next: Bug Fix Verification →