Fastest

Analysis & Execution #

Once your GitHub integration is complete and workflows are triggered, FASTEST provides powerful analysis and execution capabilities. This section covers how to review analysis results, manage test case selections, and execute optimized testing workflows.

Analysis Results Overview #

After triggering a workflow (through pull requests or code changes), FASTEST generates comprehensive analysis results using multiple intelligent strategies.

Analysis Strategies #

FASTEST employs three main test case selection strategies:

1. Direct Mapping #

  • Purpose: Identifies tests directly related to changed code
  • Method: Maps code changes to corresponding test cases
  • Best For: Immediate impact assessment and regression testing
  • Example: If you modify a function calculateSum(), tests like testCalculateSum() will be prioritized

2. Hotspot Analysis #

  • Purpose: Focuses on frequently modified areas of code
  • Method: Analyzes historical change patterns and identifies high-risk areas
  • Best For: Preventing issues in code sections with high modification frequency
  • Example: Files or functions that have been changed frequently in recent commits

3. Historical Failure Prediction #

  • Purpose: Predicts potential failures based on historical data
  • Method: Uses machine learning to analyze past test failures and code changes
  • Best For: Proactive testing of areas likely to introduce bugs
  • Example: Tests that have failed historically when similar code changes were made

Reviewing Analysis Results #

Analysis Dashboard #

When analysis completes, you'll see:

1. Summary Statistics

  • Total number of tests analyzed
  • Recommended test cases count
  • Analysis confidence scores
  • Estimated time savings

2. Test Case Recommendations

  • Categorized by analysis strategy
  • Priority rankings (High, Medium, Low)
  • Reason for selection
  • Estimated execution time

Understanding Results #

Priority Levels #

  • High Priority: Critical tests that must be executed
  • Medium Priority: Important tests for comprehensive coverage
  • Low Priority: Optional tests for complete validation

Selection Rationale #

Each recommended test case includes:

  • Analysis Strategy: Which method identified this test
  • Confidence Score: How certain FASTEST is about the recommendation
  • Change Impact: Specific code changes that triggered this selection
  • Historical Context: Past performance and failure data

Test Case Queue Management #

FASTEST provides an interactive interface for managing your test execution queue.

Review Recommended Tests #

1. Examine Recommendations

  • Review the list of recommended test cases
  • Understand the rationale behind each selection
  • Check priority levels and confidence scores

2. Analysis Validation

  • Verify that recommended tests align with your changes
  • Consider project-specific testing requirements
  • Review any edge cases that might need additional coverage

Customize Test Selection #

Add Tests to Queue #

  • Accept Recommendations: Click to add recommended tests to execution queue
  • Bulk Selection: Select multiple tests at once using checkboxes
  • Priority Filtering: Add only high-priority tests for quick validation

Manual Test Addition #

  1. Browse All Tests: View complete test suite for your repository
  2. Search Functionality: Find specific tests by name or category
  3. Custom Addition: Add tests not identified by automatic analysis
  4. Test Dependencies: Ensure prerequisite tests are included

Remove Tests from Queue #

  • Deselect Tests: Remove tests that aren't relevant to current changes
  • Time Optimization: Remove time-intensive tests for faster feedback
  • Resource Management: Adjust based on available CI/CD resources

Queue Management Features #

Test Organization #

  • Grouping: Organize tests by category, priority, or analysis strategy
  • Sorting: Arrange by execution time, priority, or alphabetical order
  • Filtering: Show/hide tests based on various criteria

Execution Planning #

  • Time Estimation: View total estimated execution time
  • Resource Planning: Understand compute requirements
  • Parallel Execution: Optimize test runs for faster completion

Test Execution Process #

Initiating Execution #

1. Final Review

  • Confirm your test selection
  • Verify execution queue contents
  • Check estimated completion time

2. Execute Button

  • Click the "Execute" button to start the testing process
  • FASTEST will trigger the GitHub Actions workflow
  • Execution begins automatically in your CI/CD environment

Execution Workflow #

GitHub Actions Integration #

When you click "Execute":

  1. Workflow Trigger: FASTEST sends execution instructions to GitHub
  2. Actions Activation: GitHub Actions workflow starts automatically
  3. Environment Setup: Test environment is prepared (build, dependencies)
  4. Test Execution: Selected tests run in the CI/CD environment
  5. Result Collection: Test outcomes are gathered and processed

Real-Time Monitoring #

During execution, you can monitor:

  • Progress Tracking: See which tests are currently running
  • Live Updates: Real-time status updates in FASTEST dashboard
  • Log Streaming: View execution logs as tests run
  • Error Detection: Immediate notification of test failures

Execution Results #

Result Analysis #

Once execution completes, FASTEST provides comprehensive results:

Test Outcomes #

  • Pass/Fail Status: Clear indication of test results
  • Execution Time: Individual and total test execution times
  • Error Details: Detailed information about any test failures
  • Performance Metrics: Execution efficiency and resource usage

Result Categories #

1. Passed Tests ✅

  • Successfully executed tests
  • Confirmation of code stability
  • Performance benchmarks

2. Failed Tests ❌

  • Tests that didn't pass
  • Detailed error messages and stack traces
  • Suggested remediation steps

3. Skipped Tests ⏭️

  • Tests that were bypassed
  • Reasons for skipping (dependencies, environment issues)
  • Recommendations for resolution

Post-Execution Actions #

Result Review #

  1. Analyze Failures: Investigate any failed tests
  2. Performance Assessment: Review execution efficiency
  3. Coverage Evaluation: Ensure adequate test coverage
  4. Quality Validation: Confirm code changes meet quality standards

Next Steps #

Successful Execution #

  • Merge Approval: Use results to approve pull requests
  • Documentation: Record testing decisions and outcomes
  • Process Improvement: Note optimizations for future use

Failed Tests #

  • Bug Investigation: Investigate and fix identified issues
  • Re-execution: Run tests again after fixes
  • Additional Testing: Consider expanding test coverage

Historical Analysis #

FASTEST maintains execution history for:

  • Trend Analysis: Track testing efficiency over time
  • Performance Metrics: Monitor execution time improvements
  • Success Rates: Analyze test reliability and effectiveness
  • Process Optimization: Identify areas for workflow improvement

Best Practices #

Execution Strategy #

  1. Start Small: Begin with high-priority tests for quick feedback
  2. Iterate Frequently: Run tests often during development
  3. Monitor Performance: Track execution times and optimize accordingly
  4. Learn from Results: Use historical data to improve future selections

Quality Assurance #

  • Regular Review: Periodically assess the effectiveness of test selections
  • Feedback Integration: Incorporate team feedback into testing strategy
  • Continuous Improvement: Refine processes based on results and experience
  • Documentation: Maintain records of testing decisions and outcomes

Your FASTEST workflow is now complete! The platform will continue to learn from your usage patterns and improve its recommendations over time, making your testing process increasingly efficient and effective.