Composing a pilot from reusable steps is the easy part. The friction shows up later: a checkout step needs a tweak, and now you’re hunting through a file tree trying to remember which fragment holds the line you need to change. The bigger your automation library gets, the more time you lose just finding the step.
PilotStudio keeps every piece one click away.
The whole pilot, in one outline
When a pilot pulls in step files with include, those steps aren’t hidden — they’re listed right in the outline beside your script. The top-level pilot reads like the flow it represents:
{% verbatim %}
{% include 'saucedemo_pom_login' %}
{% include 'saucedemo_pom_inventory' %}
{% include 'saucedemo_pom_cart' %}
{% include 'saucedemo_pom_checkout_info' %}
{% include 'saucedemo_pom_checkout_finish' %}
{% endverbatim %}
See the step you need? Click it. It opens in its own tab, ready to edit — change the step, then jump straight back to the pilot that composes it. No leaving the workspace, no guessing which file owns which selector.
How it works
- Every include is in the outline — composed steps sit right next to the main script, not buried in a tree.
- One click opens the step — the included fragment opens in its own tab.
- Edit, then jump back — fix the step and return to the parent pilot without losing your place.
- Shared field map travels with it — the same named locators flow into every step you open.
Who it’s for
Anyone maintaining a growing pilot library — the teams who already compose login, navigation, and checkout once and reuse them everywhere, and want to move through those pieces as fast as they assembled them.
Try it on your own flows
Start your free 30-day trial → — no credit card required. Or browse the full PilotStudio walkthrough on our YouTube channel.