Testing Process

The standard testing process is a set of steps followed by Vansah to ensure the quality and reliability of software applications.

 

1. Test Planning

Objective: Define the scope, objectives, and resources required for testing. Refer to the project’s user stories, epics, or other requirement documents to understand the features and functionalities that need to be tested.

  • Activities:
    • Identify test objectives and requirements.
    • Determine the testing scope and coverage.
    • Use Jira’s Agile boards to create user stories that capture the functional requirements of the software.
    • Define the acceptance criteria within the user stories to outline the specific conditions that must be met for the functionality to be considered working.

Objective: Create Test Cases in Jira and link them to the corresponding user stories. 

  • Activities:
    • Identify existing Test Cases available to link to your user stories
    • Determine the testing scope and coverage

ObjectiveCreate Test Cases in Jira and link them to the corresponding user Test Folder Cycles. 

  • Activities:
    •  Identify existing Test Cases available to link to your Test Folder
    • Determine the testing scope and coverage

Objective: If your test objectives are high-level and encompass multiple user stories, create epics in Jira to represent these broader objectives. Link related user stories to the corresponding epics.

  • Activities:
    • Navigate to the Test Plan where you want to link Test Cases
    • Add new Test Cases or link existing Test Cases to the Test Plan. 

2. Test Design

Test Cases Creation

Objective: Create Test Cases based on requirements and specifications.

Activities:

  • Creating Test Cases
    • Utilize Vansah Intelligence (GenAI) for AI Test Case generation, which streamlines testing processes, reduces manual efforts, and enhances the accuracy and efficiency of test cases.
    • Create New Test CaseNavigate to Vansah Test Repository or Jira Issue where you can create Test Cases. Use the provided interface to create a new test case. Include a clear and descriptive title that communicates the specific scenario being tested.
  • Defining Test Steps
    • Add Test Steps: Within the test case, define the individual test steps that need to be executed to validate the intended functionality.
    • Include Expected Results: For each test step, articulate the expected outcome or result that indicates the successful execution of that step.
  • Mapping to Requirements
    • Link to User Stories or Requirements: Link the test case to the corresponding user stories or requirements in Jira. This establishes the traceability between the test case and the specific functionality being tested.
  • Adding Attachments and Media
    • Upload Supporting Documents: If applicable, attach any relevant documents, screenshots, or media files that provide additional context or guidance for executing the test case.
  • Adding Attachments and Media
    • Upload Supporting Documents: If applicable, attach any relevant documents, screenshots, or media files that provide additional context or guidance for executing the test case.
  • Automate Test Cases
    • Identify tests for automation: If applicable, identify test cases which can be automated and use the appropriate Test Automation tool. 
    • Integrate Test automation: use the appropriate Vansah connect solution to integrate test case results into Vansah.

3. Test Execution

Objective: Run your Test Cases ensure the quality, reliability and functionality of the product/software being developed.

Activities:

  • Access the Jira Issue or Associated Test Cycle/Plan
    • Navigate to the Test Case within the Issue or Test Plan
    • Initiate Test Case execution by clicking on the Test Case and clicking on Run
  • Recording Test Results
    • Execute the step steps outlined in the Test Case by following the provided instructions. As you progress through each step, record the actual results observed during the test execution.
  • Mapping to Requirements
    • Link to User Stories or Requirements: Link the test case to the corresponding user stories or requirements in Jira. This establishes the traceability between the test case and the specific functionality being tested.
  • Verifying Expected Results
    • Compare the actual test results with the expected results defined in the Test Case. Confirm whether the software behavior aligns with the anticipated outcomes.
  • Creating Defects
    • Document Defects: If any discrepancies, failures, or issues are encountered during test case execution, document them within the test management tool, typically by raising a defect or issue linked to the test case.
  • Completing Test Case Execution

4. Test Reporting

Objective: Generate test reports to provide insights into the testing progress and quality of the product.

Activities:

  • Utilize Vansah’s reporting Gadgets for Jira Dashboard to create customized reports based on various parameters such as test execution status, burn up, test coverage and traceability.
  • Analyze test reports to identify trends, areas of improvement, and overall test coverage
  • Use metrics like test pass rate, defect density, and test execution to evaluate the effectiveness of testing efforts.

5. Communication and Collaboration

Objective: Share test reports with relevant stakeholders to keep them informed about the testing progress and product quality

Activities:

  • Insert Testing Reports from Jira into Confluence to share real-time reports with stakeholders.
  • Update the test reports to ensure that the reported issues have been successfully addressed.
  • Analyze the patterns and root causes of the reported issues to implement preventive measures and process improvements for future testing cycles

Related Articles