Making Your Test Automation Transparent

Business analysts, developers, and testers are sometimes not on the same page when it comes to test automation. When there is no transparency in test cases, execution, coverage, and data, review of automation by all stakeholders is difficult. Making automation scripts easily readable and writable allows stakeholders to better participate. Subodh Parulekar describes how his team dealt with these issues. Learn how they leveraged behavior-driven development (BDD) concepts and put a wrapper around their existing automation framework to make it more user-friendly with the easy to understand Given-When-Then format. Subodh discusses how his team implemented the new approach in four months to automate 700+ test cases. Now, test reports contain the actual Gherkin test step that passed or failed allowing any stakeholder to evaluate the outcome. Learn how stakeholders can rerun a failed test case from the reporting dashboard to determine if the failure is related to a synchronization, environmental, functional, or test data problem.