Observed arrival · 2026-10-01
QAJev: Browser tests written as visitor goals
QAJev runs plain-language website tests in Chrome on desktop and phone, then checks whether the page shows the expected result.
- For
- Web developers testing visitor-facing flows
- Worth noticing
- A run can end as PASS, FAIL, or INCOMPLETE; harness problems are not counted against the site being tested.
Field notes
Scenarios pair a plain-language goal ending in “Stop when…” with expected visible text or a URL condition. Jev chooses browser actions, while QAJev checks the resulting page rather than treating the model’s DONE signal as proof; reports separate site failures from harness problems and list script errors, failed requests, and broken images as findings. The documentation also describes desktop and phone runs, optional Android-emulator testing, and an unsupported iOS Simulator path.
Observed signals
Read the marks
Editorial observations of this landing page, not a rating.
One card from the complete issue