In real life, you might have a big Appium test suites which you can split into small parts and execute those in parallel on different machines / VMs / operating systems to get faster result, but it is still painful to have the test results at the end of test execution. One example of the most common reasons is a test might fail in the middle of the test-execution because of many reasons, especially if you have a complex system like IoT. The failed test might not give you the result file (e.g. xml file) because it stops in the middle and you need to see each of the the logs to figure out which test(s) is/are passed and which test(s) is/are failed. On the other hand, your team leader and developer team just care to see the test result which should be summarized and displayed on one single screen (they might not want to do extra miles to get those results, e.g. Logs, Jenkins builds, Jira, etc). In such a case, Setting up monitoring tool is in rescue, thus you do not need to worry about failing test because you will have real time test result.
About Budi Utomo
Budi Utomo is a Software Engineer, open source enthusiast and a member of Appium organisation on GitHub
Want to learn more about the Test Automation Days programme?
Meet world’s leading Test Automation experts
Day 1 is sold out, but we still have tickets left for day 2! Register here and ensure your place at this unique conference. The registration fee for Day 2 (June 20) is € 395,- excl. VAT.
We hope to welcome you to Utrecht in June!