Hi,
I've been able to successfully run a test suite with < 40 tests without issue until a couple days ago when it simply stop running a test list (suite). When this occurs, no results are returned to the TS client. This usually occurs within the first 15 or 20 minutes. When the full suite runs, it takes 2+ hours to complete.
The number of tests in my suite hasn't changed significantly over the last several months, and I've not done anything to change my configuration, so am at a loss to determine the cause of this issue.
I've looked through the Forums to see if there's anything that might be applicable to my situation, but didn't see anything.
I'm at a loss to determine the cause of the problem, and would appreciate any assistance you can provide.
Thanks,
Dan
8 Answers, 1 is accepted
Thank you for reaching us out.
It seems that the scheduling setup crashed at some point and the scheduled jobs stuck. To overwhelm this situation please follow the below steps:
1. Open the Manage Results window and delete any listed runs there which do not have end time.
2. Exit Test Studio and the Test Runner from system tray (if required). In case there are multiple execution machines in the setup please stop the Test Runner on these as well.
3. Then please restart the Telerik services on the machine which hosts the Scheduler.
4. Type in the Start Menu Configure Scheduler and start the setup wizard. Click on Apply on each of the tabs and if it is all successful start Test Studio and the Test Runners on the execution machines if any.
5. Try to schedule a test list to run.
In addition to that you could be implement Windows Scheduler Tasks that actually perform the above steps few times a day or before each test list run. This will ensure a fresh and clear environment to run test on. Just for your reference here you could find a sample article how such a task could be integrated with ArtOfTest.Runner.
I hope these will be helpful for you.
In case the test list still could not be executed remotely please collect the log files during a failing run of the machine which acts as a Scheduler and the execution one and provide these for further investigation!
Thanks in advance!
Regards,
Elena Tsvetkova
Progress Telerik
Rank 1
Hi Elena,
Thanks for your very detailed response.
Unfortunately, none of the controls shown in the examples found on the Manage Results link above are enabled on my machine. I've tried a number of things to see what can be done to enable these controls, but have been unsuccessful.
At one point, in Summer 2016, I did create a Test List and scheduled it to run during my off hours, but eventually turned that off. There still remain some Results showing in the results tab. I thought by clicking one of these data sets would enable the disabled controls, but that didn't work. I eventually deleted the Test List, so in some ways, the results cannot be tied to a specific test list and are "orphaned" to an extent. I could click the Delete All button on the Results tab, but am worried that might result in other unintended behaviors.
Additionally, you suggest that if I can't get my tests to run remotely, I should submit a log file. I am running all my tests locally, there is no remote execution involved with any of my tests. I'm assuming that my scenario (creating/running tests on a local machine) is supported, but wonder if my TestStudio installation is not configured properly. Given that the issue is something that I'm only recently starting to experience makes me question that assertion.
If there's anything I can do for my installation that would enable the controls mentioned in your solution, I'm willing to do it, but just don't know what to do from here.
Thanks for your help,
Dan
Thank you for all details you shared about your setup.
I assumed it is a remote setup and thus the instructions. Though the only thing you could not access would be the Manage Results view. The rest of the steps should be applicable as well for the used setup.
Since you are running the tests on a single machine then it will be enough to generate the application log during an unsuccessful test list run. Please clear the log prior that to ensure only relative to the current issue are stored within the file. Once collected you could attached it zipped to this thread.
Thank you for your cooperation in advance!
Regards,
Elena Tsvetkova
Progress Telerik
Rank 1
Hi Elena,
Thanks for the response. I've attached the log file as requested.
Thanks,
Dan
Rank 1
Hi,
I'm just following up to see if anything useful was found in the log file I submitted. I'm still experiencing this, and would like to find a fix.
Thanks,
Dan
Thank you for providing the log file.
I reviewed its content and it seems that a test could not be found. Its name and location in project are OMS\3. TESTS\DEV-TEST\2. Passing, Move to PROD\FC - 2c2p Eventum 2373 Truncated Report Text, Short Names - OPPLA.tstest.
Could you please double check if this test is available in the Test Studio UI as well as in the project folder on disk. If it turns out the file is only available on disk please open it with a text editor like notepad and double check if you could read its content. If not the file seems to be corrupted and you would need to record the test again.
Anyways, please let me know if the file is available. Thank you in advance!
Regards,
Elena Tsvetkova
Progress Telerik
Rank 1
Hi Elena,
Thanks for the help.
It's interesting. I repurposed and renamed that file a little while ago. I wouldn't have expected that to have caused any problems.
It still exists on in the program folder on disk, and is obviously still part of the project and test list. Also the name change is accurately reflected in Test Studio and the file on disk.
I can open the file on disk using Notepad, so it didn't *seem* corrupted. I copy/paste/renamed the file and tried to add it as a new test to the project, but I got a message indicating the file was already part of the project. I thought that was a little weird.
I removed the test from my test list and am currently rerunning my test suite. It's gotten well past the point where it was previously failing, so I suspect this will run to completion.
Because I have no idea how/why it's corrupted and, therefore, have no way of correcting it, and given that I can open the "corrupted" file with notepad, I'll probably just recreate the test from scratch.
Thanks again for your help, this has gotten me over my hurdle.
Dan
Thank you very much for all your cooperation.
The reason to not being able to re-add the test is probably its UniqueId property. The tests in Test Studio could not have the same ids and sometimes if you manage the files outside of the product in the Windows explorer you could face such troubles.
Though I am glad to know we have figured that out and I hope the run will be successful this time.
Please let me know if you would need any further assistance!
Regards,
Elena Tsvetkova
Progress Telerik