Integrations / Testing
Browser
Jigward checks your app in a real browser, and keeps the recording with the Task.
What Jigward can do in Browser
-
Work in your app
Open a site, read it, click through it and fill it in, for a test, a reported bug, or any work a Task asks for.
-
Sign in with a profile
It picks the values it needs by their keys and types them itself, so a password is never part of what it reads.
-
Follow links on the public web
It starts on the profile's sites and may follow a link to any public https address.
-
Keep a recording
A recording that can be replayed, on the Task before Jigward reports.
-
Keep the console and the network
The console log, and for each request the page made, when, where to, the answer and the request id.
-
Take screenshots
Of the pages that matter, kept with the Task and shared with a report given in Slack.
-
Turn a check into a test
Asked to keep one, a Task writes a small Playwright test project, runs it, and offers it as a draft pull request.
How teams use it
-
Check a page before release
Give a Task in Slack or the web app. Jigward signs in on staging, works through the pages, and reports with the recording.
For example: Book a ride from Earth Port to Moon Base 2 on staging, before and after midnight UTC.
-
Look into a reported bug
Jigward reproduces it in the browser, and the recording, console and requests show what happened.
For example: The save button does nothing for a new field. Can you see why?
-
Keep the check as a test
A check worth keeping becomes a Playwright test in your repository, offered as a draft pull request.
What you need
- An app on a public https address. A site behind a private network is out of reach.
- A sign-in Jigward may use there, best an account of its own.
- A Jigward organization, and an admin in it to set up the profile.
Connecting it
- An admin creates a browser profile in Integrations, with a name, one or more https addresses and the Context whose Tasks may use it.
- Add the values Jigward may type there, each under a key such as LOGIN, with a line saying what it is for.
- Give a Task that needs a browser, from anywhere you give Tasks.
Security and access
-
Values never reach the model
Jigward names the field and types the value itself. A value is masked in every step, recording and log it keeps.
-
Typed only into the profile's sites
On every other site, nothing is typed.
-
Only an admin manages profiles
Each profile belongs to one Context, and only that Context's Tasks may open it.
-
Hidden until asked
Every value is hidden on screen. A member reads one value at a time, and only when they ask to see it.
-
Addresses kept short
Of a request's address, Jigward keeps the path and a request or trace id, never the rest of the query.
-
A screenshot shows what the page shows
It is a picture of the page, so a page that displays a credential shows it there too.
Jigward never does these in Browser
- Type a stored value into a site outside the profile.
- Reach a site behind a private network.
- Read a stored value into what it reasons over.
- Present a recording or a screenshot as a test.
Other integrations
Browser is a trademark of its owner, and naming it does not mean it endorses Jigward.
Meet your next engineering coworker
Bring a question
from your own project.
See how Jigward can help your team understand the system and move the next task forward.
Jigward is in closed testing. Accounts are created by hand; sending a request does not create one.