I've provided details on this set up, but here's a visual walk through:
My Web Automation Jenkins looks like this the image below. Each job listed (Announcements, Call Forwarding, etc.) is a specific feature file that Cucumber will run - so each entry runs a multitude of tests. Each Test is sent to a Selenium Grid hub and is farmed to run on one of several VM's. This simultaneous testing brings down the overall end to end duration significantly (from 45min to 6min) :
When you mouse over a job that has run, it will offer the reports view in the menu, like so:
Clicking on the Cucumber Reports link will first present you with a summary of results:
If you click the test link in the Feature Statistics table, it will break down more details on what failed and passed:
No comments:
Post a Comment