@qawolf/flows is the wrapper around QA Wolf test code. It tells the runner what to run, where to run it, and which runtime objects to inject.
Most users should start with a launch-enabled flow.
Pick The Entry Point
Import from the package that matches the target you are authoring for.Start With launch: true
launch: true asks QA Wolf to start the browser or mobile app before your callback runs.
input, setOutput(...), and test(...).
When launch is enabled, the callback also receives platform runtime objects:
| Platform | Additional callback parameters |
|---|---|
| Web | page, context, optional browser |
| Android | driver |
| iOS | driver |
Pass Launch Options In The Definition
If startup needs options and those options are known up front, pass an object tolaunch.
page or driver.
Launch Manually For Advanced Flow Control
Pass the target directly and calllaunch(...) in the callback only when the flow must decide startup at runtime.
Next Steps
- Read Flow Model for the two startup styles.
- Use Write a Web Flow, Write an Android Flow, or Write an iOS Flow for platform examples.
- Keep API Reference nearby for exact option shapes.