BDD WITH SQUASH
Are you working in agile with the BDD approach?
Squash offers a solution to formalize, automate and execute your BDD scenarios, while promoting the implementation of associated best practices.
WHY SQUASH?
Squash offers an integrated solution to meet the needs of each feature team member involved in BDD testing.
Gherkin formalization assistance
Improve your productivity and make your BDD test scenarios formalization in Gherkin more reliable, thanks to a simple and intuitive interface, with autocompletion to avoid syntax errors.
Action library to facilitate automation
Design modular tests suitable for automation, using libraries of variabilized actions that can be reused in your different test scenarios.
Agnostic test design to implementation choices
Write scenarios compatible with several automation technologies:
from the scenarios, Squash automatically generates the script skeleton expected by the different automation frameworks (Cucumber or Robot Framework).
Industrialization of the execution and analysis of automated BDD tests
Plan the automated execution of your tests or trigger them via a CI/CD pipeline, then take advantage of an interface that facilitates the analysis of the results.
HOW IT WORKS
Click on the numbered boxes to go directly to the related details.
Analyze the US and identify the necessary BDD scenarios
Before the developments, the Product Owner, developers and testers meet to collaboratively analyze the user stories and identify the resulting BDD scenarios or acceptance criteria.
As a tester, create in Squash TM the scenarios identified during these workshops as BDD test cases, and complete their description with the test objectives.
TIP
Behavior Driven Development focuses on behavior and not on implementation details (GUI, navigation), infrastructure or user path descriptions.
BDD scenarios can be complemented with navigation and GUI tests as well as exploratory tests.
Formalize the BDD scenarios to cover the US in Squash TM
Following these workshops, formalize these scenarios in Squash by adopting a modular approach consisting in factoring the actions/steps that are found in several tests.
You can also variabilize your BDD test cases. Example: instead of having several actions "the machine is running", "the machine is stopped", prefer a single variabilized action "the machine is "state"".
These two approaches allow to:
-
ensure the consistency of test cases
-
facilitate asset maintenance by avoiding redundancies
-
accelerate future test automation