Run history
Select one or more saved runs. Compare builds an analysis you can print or download.
The catalog runs in the browser you already have open, on a Mac, a Windows PC, or a phone. Chrome, Firefox, Edge, and Safari stay in the list even when those programs are not installed. Before a run, choose the browsers and the screen size. Native runners are a local feature: on the public site the catalog runs in your browser, and the framework processes start only on a computer with this repository checked out and npm run lab:runners running. There, all 20 frameworks run as their own process: Playwright, Cypress, Robot, Selenium, WebdriverIO, CodeceptJS, Selenide, TestNG, Watir, Cucumber, Behave, Reqnroll, Jest, Vitest, and Mocha on the browser rows, Appium and Maestro on the phone rows, and JMeter, Gatling, and k6 on the load rows. Four run at the same time and the rest wait their turn. The browser runners bring their own browsers. JMeter, Gatling, and k6 load the same pages with 8 virtual users for 20 seconds. A result from one is not copied into the others. The same catalog checks every language, the message form, the photo dialog, the Linear board, the Backlog sprint, and the four clip pages. Performance rows time the CV, the lab, the studio, and their main assets. npm run test:k6, npm run test:jmeter, and npm run test:gatling load those same pages on the local server.
Watch a full catalog run · Watch the tour · Review any URL · Privacy and disclaimers · Accessibility
Automation is running in the background. Switch to Watch to see the live page.
The same list is offered on a Mac, a Windows PC, or a phone. The catalog runs in the browser you have open, at the screen size you check. Framework processes are local: they start only when npm run lab:runners runs on a computer with this repository, and they download their own browsers.