Thank you for sharing details about the issue. I have a solution for you and I will also shed some light on the way changes are updated on the storage server and how the scheduling uses those tests.
The updated test, was part of a test list that you or your colleague scheduled for remote execution sometime in the future. To make it easier to follow, I will list the steps that updated the test in the storage below.
- When you schedule a test list for remote execution, Test Studio check if all necessary files for this test list are already uploaded on the storage server.
- If they are not uploaded, Test Studio will upload or update them.
- That test list, though, is not executed yet and someone makes a change to one of the tests and pushes those changes to the storage. You can make changes multiple times and you will be prompted to update those changes or not, until the scheduled test list is executed.
- When the time comes, the test list is executed on the execution server and the scheduled job is done.
- Even if you make and save any changes to a test, it will not be synchronized with the storage, because that test is not part of a test list that is scheduled for remote execution.
As you mentioned, you need to update the test in the storage, with the latest saved version of the test. To do that, you need to schedule that test, as part of a test list, for remote test execution somewhere in the near future. That should force Test Studio to update the storage with the latest updates for all tests, that are part of the test list.
I hope that the above suggestion and details will help you fix the data in the storage server. Please do not hesitate to contact us again, if you need further assistance and share more details about the misbehavior.
Thank you for your cooperation in advance.