This slide pack describes an innovative approach to designing automated tests. This approach bridges the "language" gap that can sometimes exist between test automators/developers and business stakeholders.

1. Workflow Test Automation
Bridging the Language Gap
7 Pages

2. Bridging the Language Gap
• Technologists speak in «code»
• Business stakeholders speak in «user workflow»
• Should we care?
• Stakeholders dont «really» embed themselves in projects and dont
neccesarily fully understand «technical» demonstrations they are
shown, for example, on Agile projects
• Technologists perhaps asssume stakeholders understand what they
demonstrate and perhaps struggle to describe tests in a way that
stakeholders interpret correctly
•The Gap -> bad outcomes!
(c) 2019 D. Harrison [https://www.dharrisonch.com]
1

3. Bridging the Language Gap
•How to bridge the gap?
•Use workflow diagrams as the
statement of tests!
• Designable, executable workflow
diagrams
• Stakeholders are familiar with
«flowcharts» (i.e. on general ppt’s)
(c) 2019 D. Harrison [https://www.dharrisonch.com]
2

4. Bridging the Language Gap
• A new way! – Executable workflow
(c) 2019 D. Harrison [https://www.dharrisonch.com]
3

5. Bridging the Language Gap
• Introducing - Workflow Studio
(c) 2019 D. Harrison [https://www.dharrisonch.com]
4

6. Bridging the Language Gap
(c) 2019 D. Harrison [https://www.dharrisonch.com]
•Action elements -> Test Parts
• Perform test operation (access d/b,
call Web Service, invoke WebDriver
operation) –> Execute()
• Perform outcome verification –>
Verify()
•General workflow elements -> logic
5

7. Bridging the Language Gap
• Workflow Studio:
• Extensibility via the use of test “parts”
• Test Parts are available in a design-time Toolbox
(along with standard workflow parts)
• Test Parts are composable into a workflow on a
Design surface
• Designs can be persisted
• Designs can be executed directly
• BDD++
(c) 2019 D. Harrison [https://www.dharrisonch.com]
6

8. Bridging the Language Gap
• Benefits:
• Workflow Diagrams can be more readily discussed with
stakeholders
• Test development is now a design step
• Workflow Diagrams can be developed with stakeholder
paticipation
• Tests can be presented directly in the «language» of
project stakeholders
• The Gap -> Resolved
(c) 2019 D. Harrison [https://www.dharrisonch.com]
7