Hello community,
I have been observing a hang in the test execution of my scripts when running a test suite which consists 700 test cases . The first 100-150 test cases got executed, but all of a sudden the execution halted and no traces of logs and reports were found.
Robot framework version -4.1
Extension - Robot Code robot framework support version 106.1
Visual studio code version - 1.95.3
does upgrading versions of robot could be considered in your case ?
does it work before ? i believe that the issue is related to your environment , please provide your setup versions ( python , appium/selenium , dependencies versions like libraries etc …)
Can you give any info on your test environment? Or what are you testing? Does this happen every time? Does it happen in the same test case or keyword every time?
700 test cases in one test suite sounds big count for me. Are they really in one file?
Would it be possible to split the test execution so that you run e.g. 100 test cases at one time? And then the next 100 test cases and so on… Does the test execution halt then?
This is just guessing but maybe your test execution consumes too much memory and crashes because of that?
Basically, I’m testing happy paths, denials and every corner test cases of my application. I wanted to check all the scenarios simultaneously under a single run. I am experiencing intermittent execution hangs, occurring approximately once every three runs. Also, I’m logging my output and reports to a separate file. Please find the libraries and dependencies below:
Python version - 3.8.3.
Package Version
If the hangs are more or less random it makes it even more harder to solve.
Does it happen in the same test case or keyword every time? Does it happen in the same time of a day?
What about your system? Does it have e.g. some automatic maintenance which forces reboots etc. every now and then?
Or maybe there is in a test case a loop which exit criteria is in some situations never fulfilled and it loops until the system runs out of memory? Make sure that in possible loops there are always a timeout or other exit method to avoid indefinite loops.
That is the thing that is haunting. It happens randomly at different test cases and different keywords .I have been using the timeouts after every test case and there are no infinite loops
Since you are running on windows and did not answer my question;
If use and pipe output from any commands and do not read the input fully - this happens. It’s windows feature. Hangs are random because it depends on how much stuff the execution generates.