Apple Interview Question
Software Engineer in TestsCountry: United States
Some possibilities:
1. Threading issues. ("Synchronize" correctly in java to fix the issue)
2. Memory issues: (memory leaks of java objects or connections can be the reason)
3. In test suites lik JUnit, object model remains in memory and order of test cases run is not guaranteed. So make sure no singleton instances are leaking from one test case to another.
Look at the failures in the logs, in general, it will be the health of the server to be checked, if the server performance is slow(timeout errors, ObjectNotFound Exceptions), if there is an OutOfMemoryException is thrown in one of the test case or even outside this testSuite, need to be cleaned out.
Adding to the above answer.
if the test data is intact
else check if test data is still relevant
if servers are responding in desired turnaround time
check logs for similar kind of errors
check if application was up ,the whole time
check if machines are behaving slower due to continuos runs and memory leaks
Compare fail pattern to input data for correlation or check error log for stability issues (object not found/timing issues).
- Anonymous March 21, 20151 out of 7? Day of the week related? - Check run date for test, compare to calendar.
Is there a fail pattern? Does it literally fail every 7th time or just averages to fail 1/7 of the time? Error log and execution logs are crucial.