Tutorial F

From Business Workflows to Automated Tests

Anne Kramer

09:00-12:30 CEST Tuesday 7th June

With the deployment of agile development practices, QA & Testing teams are challenged by the acceleration of production releases and the imperative of test automation. These challenges make test relevance and the alignment of these tests with business needs even more crucial. After all, what would be the economic justification of investing in automation and maintenance of tests that do not properly reflect the business needs?

While agility favours continuous collaboration on a largely verbal basis, how can we ensure that the business message is conveyed without distortion to the automated tests? What artifacts capable of transcending differences in profiles (business, developers, testers, POs, managers) should be used to support agile team collaboration given that the Gherkin language is not well accepted by many and is also ill-suited to the expression of longer, more complex tests at the top of the test pyramid?

This tutorial allows participants to practice a visual TDD approach (Acceptance Test Driven Development). In this approach, the test requirements are expressed in graphical workflows.

This graphical representation is not exclusive and can coexist with textual User Stories and acceptance criteria. Nevertheless, its visual nature makes it quickly understandable by all the project stakeholders, whatever their profile and technical background. Another advantage lies in the contextualization of the US: the business challenge, the “big picture” is always kept in mind.

The participants of the tutorial will build such a test workflow for a simple functional scope proposed as a practical exercise.

  • From their test workflows, they will manipulate a tool (YEST) that assists QA teams in test design
  • They will implement the designed tests in a textual form for manual execution and publish these manual tests in a test management tool (Xray forJira).
  • They will define the regression tests to be automated and implement the selected tests in the form of pre-defined keyword sequences. * They will produce and use data tables to assign data variables to the automated tests.
  • They will publish the automated scripts in the RobotFramework and will be able to launch the test execution.
  • Finally, they will see how the execution results are reported in Xray and how a visual pre-analysis of these results is proposed directly on their graphical application workflow in Jira.