Repository files navigation

A collection of websites focused on browsers usage and features.

Open anissue or (faster) a pull request.

Old goodpublic/index.html editing.

• npm install
• (optional) create.env from.env.example, then edit it
• (local)npm run dev or(prod)npm run build

Websites colors are CSS custom properties in/src/css/config/sites.css.

Tests usePlaywright and can be run withnpm test. They can all run locally or in a GitHub action.

Before running tests locally:

• make sure the project is accessible from a URL (e.g. usingnpm run preview);
• add this URL in thePW_BASE_URL entry of your.env;
• npx playwright install pulls the headless browsers used by the test.

You can also play with Playwright GUI by runningnpm run test:ui.

URLs are tested on merge requests usingLychee in a GitHub Action. To test URLs locally install Lychee and runnpm run test:absolute-links.

When running the tests locally, the results are in/tests/results:

• {tld}-{timestamp}.json: JSON report of the test suites;
• html/index.html: HTML report of the latest test suites;
• axe-html/{tld}-{timestamp}-{wcag2-a|wcag2-aa|others}.html: HTML reports of the accessibility tests, split by category (WCAG 2 A, WCAG 2 AA, others);

When running in a GitHub action, the “summary” view of the GitHub Action has anartifact section at the very bottom. The artifact archive contains the same HTML report as inhtml/index.html when you run tests locally.

When you open it and pick one of the accessibility tests, look into the “attachment” to find the HTML report dedicated to accessibility issues (as well as a JSON file).

Last deployment: