Myrax docs

The browser gate

Eight checks run in a real Chromium on your own computer, at desktop and phone widths. A build is only done when every check passes, and this page lists exactly what is measured and what is not.

Most builders hand you code and call it finished. Myrax runs the built page in a real Chromium browser on your own computer, on a desktop and a phone viewport, and reports each check with the value it measured. A build is only called done when every check passes.

The checks, exactly

This is the complete list. It is short on purpose: every line below is something the run really measures, and nothing is claimed that the code does not do.

  • Entry page exists — an HTML file was produced in the workspace.
  • Page opens on desktop — the page answers with an HTTP status below 400, and its title is recorded.
  • No page errors on desktop — the console and the page raise nothing while loading.
  • Page has visible content — more than 20 characters of visible text. A blank page fails.
  • No sideways scroll on desktop — the document is not wider than the viewport.
  • Interactive elements reachable — links, buttons and form controls exist and at least one is visible. The count is reported, for example “23 of 23 visible”.
  • Page opens on phone — the same page loads at 390×844 with no page errors.
  • No sideways scroll on phone — nothing overflows the phone width.

What is not checked

Read this before relying on a green result. These are real gaps, not disclaimers:

  • No video recording. The run does not capture a recording, and it does not take a screenshot at every step. What you get is the measured value behind each check.
  • No form or checkout submission. Fields are not filled and no payment flow is exercised, unless a Vault login matches the site (see below).
  • No navigation walk. Only the entry page is opened. Other routes are not visited or clicked through.
  • No visual judgement. The checks measure structure and errors, not whether the design looks right or the copy makes sense.

The one interactive path

If you stored a login for the site in the Vault, the run signs in with it and reports that as its own check. Credentials stay on your machine. Without a matching Vault entry the sign-in check is skipped, so a build with no auth is not failed for a login it never had.

When it fails

A failed check goes back to the Builder with the exact name and measured detail attached, and the run repeats once. If it still fails, the build is marked failed and the reasons stay visible on the project. There is no silent green.

What “tested” means.

It means these eight checks passed in a real browser at two sizes. It is not a formal certification, it does not replace your own review, and it cannot tell you the page is good — only that it loads, shows content, and does not overflow.