Description
When running a Dynamic Test List in Progress® Telerik® Test Studio® via Scheduling, you may encounter a situation where tests that no longer exist in the local project are executed. These ghost tests may appear because the MongoDB storage database retains files even after they have been deleted from the local project. This issue can cause test failures and discrepancies between the local project and the tests executed remotely.
This knowledge base article also answers the following questions:
- How to remove ghost tests from a Dynamic Test List in Test Studio?
- Why are deleted tests still running in Test Studio Scheduling?
- How to clean up the MongoDB storage database for Test Studio?
Solution
To resolve this issue, follow one of the approaches below:
Approach 1: Using MongoDB Compass to Delete Specific Tests
- Download MongoDB Compass from their official download page.
- Connect MongoDB Compass to your Test Studio storage database using the instructions here.
- Navigate to the
testscollection in the MongoDB database. - Search for and locate the document corresponding to the ghost test using the guidelines here.
- Delete the identified document to remove the ghost test.
Approach 2: Use Static Test Lists or Refine Filters
- Replace the Dynamic Test List with a Static Test List if applicable. Static lists do not rely on filters and will contain only the tests explicitly added.
- Modify the filters for the Dynamic Test List to ensure they are more precise and exclude unintended tests.
Approach 3: Drop the Entire Storage Database
- Follow the steps outlined to drop the entire MongoDB storage database.
- After dropping the database, use the
Uploadbutton in Test Studio to upload the current state of your project to the Storage database.
Note!
Dropping the entire database also deletes all existing test results. If you need to keep the results from previous runs, consider dropping specific collections only using the instructions here.