The Testing Process supported by Vansah aims to ensure that the software or system you are testing meets the specified requirements, functions as intended, and is free from defects.
The process emphasizes both manual and automated testing, enabling a comprehensive evaluation from multiple angles to identify and address potential issues. Vansah seeks to reduce the risk of post-release issues, enhance overall software quality, and ensure a positive user experience all managed directly within your Jira project workspace.
A Typical Testing Lifecycle
Requirements Analysis
Objective:
Understand Project Requirements:
Gain a clear understanding of the project’s functional and non-functional requirements.
Identify key stakeholders and gather their input to ensure comprehensive requirement coverage.
Establish Testable Requirements:
Evaluate the project requirements to ensure they are clear, unambiguous, and verifiable.
Identify any inconsistencies or gaps in the requirements documentation
Activities:
Review and analyze the requirements, such as user stories, use cases, and functional specifications, to identify potential testing scenarios.
Validate the requirements to ensure they are complete, consistent, and testable.
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. Learn more
Activities:
Identify Test Objectives and requirements
Optional: If enabled use Vansah Intelligence to automate Test Case creation using GenAI.
Determine the Testing Scope and Test Coverage.
Ensure the acceptance criteria has been established within the user stories to outline the specific conditions that must be met for the functionality to be considered working.
Link Test Cases to user Jira Issues
Objective:
Create Test Cases in Jira and link them to the corresponding user stories. Learn more
Activities:
Identify existing Test Cases available and link the Test Cases to your user stories
Link Test Cases to Test Folder/Cycles
Objective:
You may decide to create a separate Test Cycle to execute Test Cases to validate the requirement. In this case you can manage testing using a Test Folder cycle. Learn more
Activities:
Identify existing Test Cases available to link to your Test Folder.
Link Test Cases to Test Plans
Objective:
If your Test objectives are high-level and encompass multiple user stories, create a Test Plan to represent these broader objectives. Link related user stories to a Test Plan and manage Testing from the plan created in Vansah.
Activities:
Navigate to the Test Plan where you want to link your requirements.
Add new Test Cases or link existing Test Cases to the Test Plan.
Test Design
Test Cases Creation
Objective: Create Test Cases based on requirements and specifications. Learn more
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 Case: Navigate 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. See example below.
Defining your Test Script
Depending on the need a Test Script can be either:
Plain Text
Multi Steps or
BDD – Gherkin format.
Plain Text Format
Description: Plain Text Format is a straightforward approach for users who prefer simplicity and ease of use.
Advantages:
Easy to write and understand.
Suitable for users who prefer a simple and direct approach to script writing.
Multi Steps Format
Using Multi Steps for Test Script writing enables users to record the testing process in a stepwise manner, enhancing precision.
Advantages:
Allows for a detailed and step-by-step recording of the testing process.
Enhances precision and accuracy in script writing.
BDD – Gherkin Format
BDD – Gherkin format involves writing scenarios using Gherkin-derived syntax, which is designed to be easy to learn by non-programmers while allowing a concise description of test scenarios and examples to illustrate business rules.
Advantages:
Enables the use of clear and concise descriptions of test scenarios and examples.
Facilitates the illustration of business rules in real-world domains.
Supports the Given/When/Then vocabulary, which is clear to all team members and helps avoid ambiguities, making conversations more efficient.
Allows for the creation of action words (reusable steps) from Gherkin keywords automatically.
Enables the use of scenario outlines to express examples more concisely through the use of parameters and data tables.
These differences in formats provide users with options to suit their preferences and testing requirements, ranging from simplicity and ease of use to detailed stepwise recording and clear, concise scenario descriptions.
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 Comments to Test Cases
Enrich Test Cases with comments: Include extra comments to support users with the information necessary to run or manage a Test Case
Automate Test Cases
Identify Test Cases 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.
Test Environment
Objective: Create a Test Environment label which matches your projects Test Environment. The Test environment will serve as a tag to report on Test Results and coverage of Tests conducted in the environment.
Test Data Preparation:
Populate the Test Environment with relevant and representative data to simulate your Test Cases.
Test Execution
Objective:
Run your Test Cases to ensure quality, reliability and functionality of the product/software being developed.
Access the Jira Issue or Associated Test Cycle/Plan
Navigate to the Test Case
Initiate Test Case execution by clicking on the Test Case and clicking on Run
Recording Test Results
Execute the Test Case outlined in the Test Script.
Compare the actual Test Results with the expected results defined in the Test Script. 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, link or create a new issue and have it Linked to the Test Run.
Test Reporting
Generate Test Reports to provide insights into the testing progress and quality of the product. You can also access the default Test Report available within the Jira Issue, Test Folder and Test Plan for quick reference.
Activities:
Configure Vansah’s reporting Gadgets for your Jira Dashboards to create customized reports based on various parameters such as Test Execution status, Testing Burn up, Test Coverage and Requirements Traceability.
Analyze Test Reports to identify trends, areas of improvement, and overall Test Coverage
Use metrics like Test Pass Rate, and Test Coverage to evaluate the effectiveness of testing efforts.
Jira Dashboard Gadgets
Burnup Execution Report
Test Execution Report
Test Summary Report
Issue Traceability Matrix
Issue Traceability Summary
Confluence Pages Reporting
Now that you have configured your Jira Dashboards you can embed your Testing gadgets into Confluence pages to report to a wider audience by sharing the confluence page without requiring users to access your Jira project.
All Vansah Testing gadgets can be embedded into a confluence page for real-time reporting with the ability to drill into the gadget report to access the underlying data.