Quality of this site
This site is also an exercise in quality. Every change goes through automated checks before it goes live, and everything can be verified in the public repository.
- 27 end-to-end test specs (Cypress)
- 5 verification pipelines in CI
View the repository →View the pipelines →
What is checked
On every change, CI runs these checks:
- Flows and content: navigation, languages (PT, EN and FR), contact form, blog, SEO, structured data and RSS feeds, with Cypress tests.
- Accessibility: axe-core (WCAG 2.2, levels A and AA) and Pa11y on the main pages, in the three languages, on desktop and mobile screens.
- Security: HTTP headers, cookies and attack surface; secret detection (Gitleaks); static analysis (CodeQL); dependency audit and review; licenses.
- Privacy (LGPD): tests on the data collected and the privacy notice.
- Performance: Lighthouse CI on mobile and desktop, with minimum scores and limits for LCP and CLS.
- Interface: unique and well-structured headings, complete metadata and minimum-size touch targets.
How the work is done
Each area of the site has a short spec in the specs folder, with acceptance criteria tied to the test that proves them. A change starts with the spec, is implemented until the criteria pass, and ends with the spec updated.
Tests outrank code: when a test fails, the site is fixed, not the test. New tests are welcome; existing ones are not loosened to make a change pass.
Limits
Automated tests do not replace manual evaluation with screen readers or measurements with real visitors. The CI lab scores are targets to prevent regressions, not promises of performance on every device.