Have the issues related to https://www.telerik.com/forums/scheduled-test-list-not-running-the-latest been resolved? I am experiencing similar issues and not certain whether they are related or new problems.
As a proof of concept, I built a simple test to enter some text into a search field and then click a search button. Let's call the test "myapp_search". I then duplicated the test 3 times, so I now have "myapp_search", "myapp_search (1)", "myapp_search (2)", and "myapp_search (3)". Then I created a dynamic test list to include all tests with a name containing "myapp" and "search". The dynamic list successfully ran all 4 tests both locally and remotely. After the test list ran successfully, I deleted the 3 duplicate tests, renamed the original test to something that does not match the dynamic list's rules, created more extensive tests that use the "myapp_search" as a test as step and fit into the same dynamic test list, and ran the test list again. Running the list locally runs the tests I would expect, but running the list remotely runs "myapp_search (1)", "myapp_search (2)", and "myapp_search (3)" despite the tests being deleted from the project. Note that this project is not in version control.
Using Test Studio 2018.1.418.0
Thank you!
Matt
3 Answers, 1 is accepted
Thank you for the detailed explanation of the issue you have faced.
Please note that the forum thread you referred is posted quite long time ago and concerns older versions of Test Studio. Ever since there are plenty of improvements and new features.
Though I hope I have the solution for you - could you please drop the storage database? Please note that this will delete all project related information in the database including the so far generated results from remote runs. If you would like to keep these you could drop only tests and testlists collections as described at the bottom of the article.
Please let me know if the test list can be executed correctly on the remote machine as well? Thanks!
Regards,
Elena Tsvetkova
Progress Telerik
Rank 1
Hi Elena,
Thank you for your reply. Dropping the tests and testlists collections seems to have resolved the issue.
How do I prevent this from happening in the future and having to drop collections when renaming tests? Although the post I linked is old, the issue seemed similar enough that it may help in determining a cause.
Thanks again!
Thanks for the feedback! I am pleased to know the proposed solution fixed the issue.
What causes the database to get corrupted and stop updating the files correctly is probably an issue in the MongoDB itself often caused by the network communication and failures in it. It is not the most reliable database out there but it works fine for the purposes of Scheduling in Test Studio. To prevent future discrepancies you could drop the database or the single collections from time to time to ensure the most up-to-date copy of the project is being uploaded.
I would like to thank you in advance for your cooperation and understanding!
Regards,
Elena Tsvetkova
Progress Telerik