Identify duplicate test cases - FAQs

Following are some frequently asked questions about identifying and managing duplicate test cases with our AI-powered de-duplication feature. As your test repository grows, redundant test cases can accumulate, leading to wasted effort and confusing reports. This feature helps you maintain a clean and efficient test suite by using AI to scan your projects for both exact and semantic duplicates. Use this guide to find answers about how the AI works, the review and merge process, and the impact on your existing test runs.

What is the main purpose of the AI-powered test case de-duplication feature?

The primary purpose of this feature is to help users identify and manage duplicate test cases. AI detects existing duplicate test cases that multiple users might have created by mistake across different folders within a project.

How does the AI identify duplicate test cases?

The AI analyzes test cases and compares them to find similarities. It then provides an “AI similarity score” to indicate how similar two test cases are and explains the reasoning behind that score.

What are the different types of duplicates the AI can identify?

The system identifies different types of duplicates, including:

• Exact duplicates: These are test cases where titles, description, steps and results are identical between the two.
• Semantic duplicates: These are test cases where certain aspects are the same, and more importantly, the intent of both test cases is the same, even if some details differ.

How does the review process for duplicate test cases work?

When duplicate test cases are found, you see a button like Review the duplicate. Click this takes you to a page with a side-by-side view of the potentially duplicate test cases. This view shows each test case, its location (folder), the AI similarity score, and the reasoning for the score.

What actions can I take when duplicate test cases are identified?

When reviewing duplicate test cases, you have a couple of options:

• Merge: You can choose to merge the identified duplicate test cases where a source test case gets merged into the target test case. The source test case details are added as a comment in target test case details. The source test case is archived as well post the merge.
• Archive: You can choose to archive one of the test cases from the identified duplicate pair.
• Discard suggestion: If you intentionally created the test cases and do not consider them duplicates or do not want to take any action, you can discard the AI’s suggestion.

If I discard a duplicate suggestion, will the AI flag it again in the next scan?

No, if you discard a specific suggestion for a pair of test cases (e.g., TC121 and TCABC), the AI will not flag that exact same pair again. The suggestion itself is removed, but your test cases remain as they are.

What happens if I discard a suggestion for TC141 and TC14156, and then another user creates a new test case, TC1423, which is very similar to TC141? Will the AI flag this new pair?

Yes, it will. Even if you previously discarded a suggestion for TC141 and TC14156, the AI will flag a new potential duplicate if another user creates TC1423, and it is found to be similar to TC141. The system evaluates new pairs independently.

Does this feature also prevent AI from generating duplicate test cases in the first place?

Not as of now. We plan to support this capability in future.

How often does the AI scan for duplicate test cases? Is the list updated in real-time?

The list of duplicate test cases is not updated in real-time. The system performs scans at scheduled intervals. When you view the list, it will indicate the time of the last scan.

If I copy a test case from one folder to another using a copy function, will the AI identify these as duplicates?

Yes, if you use a copy function and create an identical or very similar test case in another folder, the AI is designed to detect and flag these as potential duplicates.

What does the AI similarity score represent?

The AI similarity score is a measure calculated by the AI to quantify how similar two test cases are. The higher the score, the more similar the test cases are considered to be. The system also provides a reason for the assigned score.

What happens to test runs when a duplicate test case is archived or deleted?

When you archive or delete a duplicate test case, the result varies based on the status of the test runs:

• Closed Test Runs: Archived or deleted test cases keep their results and associations within the test runs they belong to. They remain unchanged.
• Active Test Runs: If you merge duplicate test cases, the source test case is archived, and its instances in active test runs are deleted.

Who can archive or delete test cases based on Role-Based Access Control (RBAC)?

In Test Management, permissions to archive or delete test cases are governed by RBAC. In general, a:

• Viewer: Cannot create, edit, archive, or delete test cases.
• Tester: Can create and edit test cases but cannot archive or delete them.
• Product User and Product Admin: Have full permissions, including creating, editing, archiving, and deleting test cases.