Version Control your Test Case

Version control is essential for maintaining structured and traceable test case management. In SimplifyQA, version control allows teams to maintain previous versions, and collaborate effectively on test case updates.

With SimplifyQA’s version control, users can update test cases systematically while preserving historical data. Each test case version captures modifications such as requirement changes, test script updates, or execution criteria adjustments.

How to Version Control Test Cases in SimplifyQA?

1. Navigate to the Test Case Module: After logging into SimplifyQA, go to the "Test Case" section from the left-hand panel.

1. Select a Test Case: Select an existing test case, search for it using the filters or search bar and click on the test case name.

1. Edit the Test Case: Open the test case and make the required changes, such as modifying steps, updating conditions, or adding new data.

2. Save the Changes in new version:

• After making updates, click the save dropdown button and select 'Save as new version' to store the changes as a different version.

• SimplifyQA will automatically version control the test case, logging the changes made.

1. Review Version History:

• Click on the "Showing Version" tab within the test case details.

• View the list of all changes, including:

  • Version numbers.

  • Date and time of updates.

  • Name of the user who made the changes.

  

How Version Control in SimplifyQA Helps in Real-World Testing?

Scenario: Testing a Banking Application

A team is working on a core banking system, where a test case verifies the fund transfer functionality between two accounts. Initially, the test case includes the following steps:

1. Log in to the banking application.

2. Navigate to the Transfer Funds section.

3. Enter sender and recipient account details.

4. Enter the transfer amount and submit the request.

5. Verify the success message and transaction ID.

Change Request and Modification

A new feature is introduced: two-factor authentication (2FA) for fund transfers above $10,000. The test case needs an update:

• Step 5 is modified to include OTP verification.

• Step 6 is added to verify that transactions above $10,000 require OTP validation.

Without version control, testers might overwrite the existing test case, making it difficult to track changes. However, with SimplifyQA’s version control, the team can:

• Create a new version of the test case with updated Step 5 and 6, while keeping the original intact.

• Track modifications with version history (e.g., "Added OTP verification for high-value transfers").

Best Practices for Version Control in SimplifyQA

• Always add version descriptions to keep track of changes.

• Control user access to prevent unauthorised modifications.

Frequently Asked Questions (FAQs)

Does version control apply to automated test cases as well?

Yes, both manual and automated test cases are version-controlled in SimplifyQA, ensuring consistency across all test artefacts.

Who can modify and manage test case versions?

Only users with appropriate permissions can create, or update can modify, ensuring controlled modifications.

Is version control available for all test artefacts in SimplifyQA?

Yes, version control applies to test cases, automation scripts, and reusable functions, ensuring consistency across all testing assets.

Is there a way to export the version?

Yes, you can export a specific version.

How many versions of a test case can SimplifyQA store?

SimplifyQA maintains a complete version history, allowing you to access all past versions without limitations.

Which features are copied and which are not when I create a new version of a test case?

Copied:

• All steps including modifications and options enabled at each step (Ex: Screenshot, skip, etc).

• Test data along with formulas and data iterations.

Not Copied:

• Review/Approve status and its details.

• DUO steps of the test case.

• Executions of the original test case.

Below configurations remains same as original:

• Baseline images and thumbnails (remains same).

• Emailer configuration (remains same).