Repository navigation
Steps Library
The handow-seed project includes some general steps. Developers can scaffold stories depending the build-in steps library for most test requirements. The code of the built-in step functions are availbe in the handow project. handow project on Github
The handow project is a test engine driven by Playwright APIs, the handow-seed is just a template combine the test engine and SHM server together.
Developers needn't refer the source code of the built-in steps when they write stories. The Editor of SHM UI provides a Steps Browser button and popover panel. Users can list all available steps, search and filter them by keyword and type, find out the required step and copy the label to the editing story. That is Handow's None Coding Test way. Demo Editor
The Steps Browser can list all steps including users' custom steps. Handow will integrate them together. If the custom steps has same label (with same parameters), the custome step will override the built-in step with same label.
Implement a step means copy the step label as the statement line in a scenario. The step labels don't include the "Given/When/Then" keywaord. But they are catalogued in 2 groups - Acts (action steps) and Facts (varification steps). All Acts steps could be used as Given or When step by adding the "Given/When" keyword ahead. All Facts steps could be used as Then step by adding the "Then" keyword ahead. We can also use the subsequent keyword "And" to continue "Given/When/Then" to make the story more readable.
Users need pass parameters to the step to instantiate it in current scenario. The parameter names of a step can explain its data type mostly.
The @skip: () can make a step conditional according to current parameters. But make sure the scenario to keep the scenario valid after steps skipped.
- Can any Acts step be used as a "Given" step？
Supported by Handow team support@handow.org