I’m doing an Android app test with Appium. The test is configured for 200 iterations and is expected to take about 2 days:
*** Test Cases ***
Very Long Test
FOR ${i} IN RANGE 200
TRY
Doing testing...
EXCEPT
Increment a variable signifying the number of fails...
ELSE
Increment a variable signifying the number of successes
FINALLY
Cleanup of appdata etc..
END
END
I’ve used the try/except/else/finally structure to avoid having the whole test abort due to some error. We’re interested in the stability of the components that are being tested. But being such a long test, where stopping to look what might’ve caused the crash and then restarting it, is not possible.
Wondering if there’s a way of getting around this? I’d quite like to get a log after each iteration, or even better, of the iteration that registered a failure. That way, I could, like a 100 iterations in, have a look and ensure I haven’t messed something up unrelated to the actually components we’re testing.