Requirements-driven test automation

Communicate, Collaborate, Automate

Watch this example of testing a CRM’s web UI using JIRA user stories and a Selenium-Java framework, to discover how: 

1. “Shift Left” QA imports written user stories to logically precise models, eradicating design ambiguities and the costly bugs they create.

2. Identifying missing logic in the visual flowcharts builds complete specifications, enabling more reliable development and the generation of comprehensive test suites.

3. Model-based test generation creates test cases before a line of code is written, exporting rigorous test suites to test management tools for truly test-driven development.

4. Developers can leverage a catalogue of automated "Find and Makes" to create the data needed to code modelled components, enabling rapid and early feature development.

5. Developing from logically clear and complete models reduces miscommunications, minimizes code rework, and builds better systems earlier.

6. Testers and automation engineers use the requirements models to generate accurate automated tests, avoiding slow and manual scripting for rigorous in-sprint testing.

7. An application scanner rapidly builds automated tests from systems in UAT environments, generating executable test code for scanned elements.

8. Test data functions allocate unique data combinations to tests on-the-fly, enabling continuous testing without test data bottlenecks. 

9. Re-usable subflows link components visually, rapidly generating end-to-end tests and integrated tests for complex systems.

10. Updating the models re-generates automated test suites in-sprint, detecting damaging bugs before they reach production.