LogoLogo
Product
  • Knowledge Base
  • What's New
  • Guides
  • User Story Coverage
    • Getting Started
    • User Story Challenges & Solution
      • Typical Implementation
      • The Challenges
      • The Solution
    • User Story Coverage Report Overview
      • Release Go / No Go Report
        • How to Generate / Edit the Report
      • User Story Quality Overview
        • How to Generate the User Story View
      • User Story Coverage Analysis
        • How to Generate the Analysis View
      • Uncovered Methods View
        • How to Generate the View
      • Customization
      • Integration
    • Use Cases by Persona
      • Managers
        • Informed Go/No Go Decisions Making
        • Effective Resources Prioritization
        • Overall Progress Monitoring
      • Developers
        • Code Quality Ownership
        • Seamless Collaboration with QA
        • Code Review Facilitator
      • QA Engineers
        • Test Execution Progress Monitoring
        • Testing Effort Prioritization
        • Testing Strategy Planing
    • Technical Overview
      • User Story Coverage Mechanism
      • Technical Architecture
      • Deployment Guide
        • US1_getResults.sh
        • US2_createReport.sh
        • US_UpdateConfluence.sh
  • Test Optimization
    • Getting Started
    • Test Execution Challenges & Solution
      • The Challenges
      • Test Optimization Solution
      • Test Optimization Main Advantages
    • Test Optimization Overview
      • Automated Test Optimization
      • Manual Test Optimization
      • Test Optimization for Pull Request
      • Test Selection Policies
        • Full Run Policy
        • No Code Changes Policy
        • Common Code Policy
        • Fastest Path to 100% Coverage Policy
      • Integrations
    • Use Cases by Persona
      • Managers
        • Fast Delivery
        • Resource Optimization
        • Thorough Testing in Tight Schedule
      • Developers
        • Exploring Only Relevant Test Failures
        • Faster Feedback Loop
        • Shift Left Testing
      • QA Engineers & Manual Testers
        • Faster & Focused Manual Testing
        • Optimizing Test Suite
        • Having Stable Product for Testing
    • Technical Overview
      • Test Optimization Mechanism
        • Associating Code With Tests
          • Statistical modeling
          • One-to-One Mapping
          • Calibration
        • Detecting Modified Code
        • Generating Test Recommendations
      • Technical Architecture
      • Deployment Guide
  • Quality Improvement
    • Getting Started
    • Challenges & Approach Comparison
      • The Challenges
      • Quality Improvement Approaches
      • Choosing the Right Approach
    • Quality Improvement Solution Overview
      • Test Gaps Analysis Report
        • How to Generate / Edit the Report
      • Coverage Trend Report
        • How to Generate / Edit the Report
      • Proof of Testing Report
        • How to Generate / Edit the Report
      • Release Quality Improvement Guide
        • STEP 1: Deploy SeaLights
        • STEP 2: Take a Quality Snapshot
        • STEP 3: Prioritize Code Areas
          • Add Code Labels
          • Ignore Irrelevant Code
          • Perform a Deep CSV Analysis
        • STEP 4: Set Baseline & Threshold
        • STEP 5: Analyze Test Gaps
        • STEP 6: Write Tests
        • Step 7: Make a Go / No Go Decision Based on Quality Gate
        • STEP 8: Measure Defect Escape Rate
      • Over Time Quality Improvement Guide
        • STEP 1: Deploy SeaLights
        • STEP 2: Take a Quality Snapshot
        • STEP 3: Prioritize code areas
          • Add Code Labels
          • Ignore Irrelevant Code
          • Perform a Deep CSV Analysis
        • STEP 4: Set Baseline & Goal
        • STEP 5: Set timeline
        • STEP 6: Write tests
        • STEP 7: Monitor progress
        • STEP 8: Measure Defect Escape Rate
    • Use Cases by Persona
      • Managers
        • Effective Prioritization & Budget Allocation
        • Tracking Progress & Measuring Impact
        • Data-Driven Release Decisions
        • Transparency & Communication
      • Developers
        • Mastering Code Coverage
        • Seamless Collaboration with QA
        • Code Quality Ownership
      • QA Engineers
        • Prioritizing Test Efforts
        • Contributing to Release Informed Decisions
        • Seamless Collaboration with Developers
        • Evaluating Testing Strategy
    • Technical Overview
      • Solution Mechanism
      • Technical Architecture
      • Deployment Guide
  • Value Proposition
    • Overview
    • Quality Use Cases
      • Go/No Go Decisions
      • Quality Improvement & Test Gaps
      • Governance & Quality Gates
      • Compliance & Proof of Testing
    • Test Optimization Use Cases
      • Reduce Costs & Infrastructure
      • Shorten Release Cycles
      • Reduce Troubleshooting
Powered by GitBook
On this page

Was this helpful?

  1. Test Optimization
  2. Use Cases by Persona
  3. Developers

Shift Left Testing

Test optimization fosters faster delivery cycles by enabling "shift-left testing". This approach involves introducing testing activities earlier in the development process, specifically targeting changes made in the code. By using test optimization:

  • You focus on relevant tests: Only tests linked directly to your code changes are executed, reducing overall testing time.

  • Issues are caught earlier: By testing changes as they happen, problems are identified sooner in the development lifecycle, before they can propagate and become more complex to fix.

  • Time to market is accelerated: Faster test cycles and earlier bug detection lead to quicker overall development, allowing you to get your code to market faster.


Step-by-Step Tutorial

1. Integrate the Tool
  • Choose and integrate a test optimization tool into your development pipeline.

  • Activate Test Optimization for pull request. The settings is currently done manually by SeaLights.

2. Configure Advanced Test Stages as Part of Pull Request Testing
  • Make sure the desired test stages you woud like to execute ealy in the process are now part of the development pipeline, are triggered automatically upon code commit.

  • Create a build that executes all your tests as a starting point for the Test Impact Analysis (TIA) engine to map tests to relevant code sections.

3. Trigger Focused Testing on Pull Request
  • Push your code changes to the version control system. Upon code commit, the CI/CD pipeline automatically triggers the test optimization tool.

  • The tool analyzes your codebase and identifies the modified sections.

  • Based on the code changes, the tool automatically selects and executes only the relevant tests (partial suite), significantly reducing execution time compared to running the entire test suite.

4. Review Targeted Results

Once the tests complete, access the results through your test management tools. You'll see only the tests selected by the TIA, ensuring you focus on the most relevant information related to your specific code changes.

5. Analyze and Address Issues

Analyze the test results to identify any failures associated with your code changes.

6. Fix and Re-test

Address identified issues in your code and re-run the focused test suite, verifying the fix and ensuring the change didn't introduce new issues.

Test optimization empowers developers to be more proactive and efficient throughout the development process, ultimately contributing to faster and higher-quality releases.

PreviousFaster Feedback LoopNextQA Engineers & Manual Testers

Was this helpful?