Version control is enabled by default and allows teams to collaborate and manage multiple versions of test cases simultaneously while maintaining data integrity and providing a history of changes. Versions can be viewed together and compared for audit purposes.
You might want to generate a new version of a test case when you need to update test case details based on changes in your product, but also want to keep the previous version, in order to test previous versions of your product. You may also want to enforce a process where team members must create a new version of a test case to be approved, rather than change an existing one.
Changes to testing details only affect test executions using the current version. Changes to test steps do not affect test executions automatically to preserve the results history. However, the following notification appears on the Test Player screen: This test script is outdated because the test case has been changed. If you choose to update the test script, the steps are synced and updated.
You cannot create a new version directly from an older version, but you can make changes to older versions. Also, by default, all lists, grids, searches, queries, etc. display the latest version of test cases. The ability to create new versions can be managed in Project Settings.