JustZix for a QA team — sharing actions by link
A tester should not wait on a developer for a "fill the form with test data" button. In JustZix they build it themselves — and then hand it to the whole team with a single link. Here is how.
The problem: QA tools hang on developers
A typical QA toolbar — "fill data", "clear the cart", "set state X" — is usually a request to a developer and an item in the backlog. Yet it is a few lines of JavaScript that a tester can write and maintain themselves.
Step 1 — build a set of actions
In one JustZix folder (URL pattern for the test environment) create a rule with actions: FILL fills the form, CLR clears the fields, STATE sets a specific app state. Each action is a button and a piece of JS.
Step 2 — share it with the team by link
JustZix lets you export a folder as a shared link — a JZS-XXXX-XXXX-XXXX-XXXX token with a lifetime of 1 to 48 hours. You send the link, the recipient sees a preview of the bundle (with a warning that it contains JavaScript), imports it with one click. The whole team has the same QA toolbar.
Link versus sync — which when
- A shared link — a one-off transfer to other people. The token expires, everyone then has their own copy. For handing a bundle to the team.
- Key sync — these are your rules on your devices, live. Not for sharing with other people.
For a QA team: one person maintains the "reference" bundle, and on changes sends out a fresh link.
Step 3 — updates
The app changed, the selector in the FILL action stopped matching? The bundle's author fixes the action on their side and sends out a new link. The rest of the team re-imports. Versioning is manual but simple — and it needs not a single ticket to the developers.
Pitfalls
- The bundle contains JavaScript — the recipient will see that. Which is good: importing foreign JS should be deliberate. In a team that trusts itself it is a formality; still, everyone should know what they import.
- The token expires. A link with a 24 h TTL will not work after two days — that is intentional. For a standing bundle, send a fresh link on every change.
- Test data is not production data. The
FILLaction enters test data — never hardcode real credentials into it.
See also
- A QA toolbar from scratch — building an action set step by step
- window.JZ as a framework — composing actions into a workflow
- Injected JS security — importing foreign bundles with care
Install JustZix — and give your QA team tools without a queue to the developers.
Rate this post
No ratings yet — be the first.