ContextQA
  • What is ContextQA?
  • Getting Started with ContextQA
    • Setup
      • Sign-Up / Login
      • Installing ContextQA Extension
    • Test Automation
      • Automation with Recorder
      • Automation with AI Agent
    • Advance Testing
      • Cross Browser Testing
      • API Testing
      • Visual Testing
      • Performance Testing
      • Accessibility Testing
      • Mobile Testing
        • Automate Test
          • Integrating VCS
          • Integrating Device Farm
          • Linking A Repository
          • Scanning Repositories
          • Test Execution Process
          • Configuring Tests
        • Mobile Testing Report
    • Manage Test Cases
      • Test Suite
      • Test Plan
    • Quality Insights
    • Integration
      • Slack Integration
      • Jira Integration
  • Advance Features
    • Self-Healing Test Cases
    • Parallel Test Execution
    • Parameterization
    • Environment Management
    • Visual Regression Testing
    • Performance Testing
    • Accessibility Testing
    • Generate Code
    • Root Cause Analysis
  • ContextQA Extension
    • Installing ContextQA Extension
    • Logging in to ContextQA from the Extension
    • Creating a Test Case in the ContextQA Extension
    • Edit Test case in Extension
    • Editing Test Steps in the ContextQA Extension
    • Deleting a Test Case from the ContextQA Extension
    • How to Re-record Test Steps in ContextQA
  • ContextQA Portal
    • Sign-Up / Login
    • ContextQA Dashboard
    • Test Development Section
      • Create
        • Create Test Case
        • Create Manual Testcase
        • Create Test Case with the help of AI
        • Create Test Suite
        • Create Cross-Browser Test Plan
        • Creating an Element Manually
        • Creating a Step Group
        • Creating Test Data Profiles
        • Create Cross-Device Test Plan
        • Creating an Environment
      • Edit
        • Edit Test Case
        • Editing Test Steps
        • Edit Test Suite
        • Editing Test Data Profile
        • Editing Test Plan
        • Edit Step Group
        • Edit Element
        • Edit Environment
      • Delete
        • Deleting a Testcase
        • Delete Test Step
        • Delete Test Suite
        • Delete Step Group
        • Delete Elements
        • Delete Test Data Profile
        • Delete Test Plan
        • Delete Machine/Device within Test Plan
      • Call Function
        • Call/Use Step Group in Testcase
        • Call Test Data Profile in Testcase
        • Call Environment
      • Run
        • Run Testcase
        • Run Details section
        • Run History
        • Executed Test Steps with visual regression
      • Elements/Conditions/Parameters
        • Add If Condition
        • Add While Condition
        • Add Element in Test Steps
        • Add Parameter in Test Case
    • API Testing
    • Creating Workspace
    • Enable Jira & Link issues
    • Bug report
  • ContextQA Insights
  • FAQ/Others
    • Assertion
    • AI Result/ Quick Fix
    • How to add Network idle Template
    • How to upload file and how to use File upload Template
    • How to add Page Display Templates
    • How to add Test Step to Visit a Page
    • How to Switch Tabs using Template
    • How to add Wait Template
    • Test Case Screenshot
    • Timeout Template
    • Element Directory in Extension
    • Find Locater of an Element
    • TestSteps Reorder
    • Test Plan Scheduler
    • Restore Deleted Test Case
    • Search Test case
    • Clone Test Step
  • Integration
    • Slack Integration
    • Jira Integration
Powered by GitBook
On this page
  • Proof Management
  • Release Management
  1. Getting Started with ContextQA

Proof & Release Management in ContextQA

Last updated 9 months ago

ContextQA provides a robust system for managing and validating test cases through Proof & Release processes. This guide will walk you through how to execute test cases, capture evidence, and complete the release process.

Proof Management

1. Access the Test Plan

  • Log in to ContextQA and navigate to the Test Development section by clicking the pencil icon in the sidebar.

  • Select Test Plans from the dropdown menu.

  • Choose the Test Plan you want to work with. A Test Plan organizes your test suites and test cases for efficient management.

2. View and Select Test Suites

  • Within the selected Test Plan, locate the Test Suites that contain your test cases.

  • Identify the test suites based on the environment or specific scenarios you need to test.

3. Run Test Cases Manually

  • Click the Run Manually button next to your chosen test suite.

  • This action creates a copy of the test suite for this specific run, which helps in maintaining and tracking test case execution.

4. Perform Regression Testing

  • You will be redirected to a new screen displaying the test cases to be executed.

  • Click on the desired test case to begin the execution.

  • ContextQA will automatically capture evidence such as screenshots, logs, and actions performed during the test.

Release Management

1. Capture Evidence

  • During the test case execution, ContextQA captures evidence including screenshots and logs of every step.

  • Continue interacting with the application as usual. ContextQA will document all actions and steps taken during the test.

2. Review Captured Evidence

  • After test execution, go to the Proof section to view all captured evidence.

  • Each test case will show the steps and evidence collected, including screenshots and details of the interactions.

  • Click on each step to review the captured data.

3. Mark Test Case Results

  • Review the captured steps and evidence.

  • For each step, you can:

  1. Mark as 'Pass' or 'Fail' based on the results.

  2. Add notes or comments if necessary (e.g., “Expected behavior missing”).

  • Click Update to save your results.

4. Finalize the Release

  • Once all test cases are reviewed, you will have a summary of the pass/fail status for each test case.

  • The release summary will include all captured evidence and test case results.

  • Ensure all data is accurate and complete before finalizing the release.

5. Post-Release Summary

  • After completing the release, you can revisit the release summary to analyze test results and evidence.

  • Use this data for reporting, further analysis, or future reference to ensure thorough documentation of the release process.


Your Proof & Release process is now complete with all necessary test cases executed and documented. This ensures a comprehensive validation of your application and helps maintain high-quality standards.

55MB
Validating and Releasing Your Test Cases .mp4