Glossary
Testing that verifies an application's features work according to requirements. Answers the question: "Does this feature do what it's supposed to do?" Distinct from non-functional testing (performance, security, accessibility).
Functional testing is the broadest category of testing most teams do. It includes unit tests, integration tests, E2E tests, smoke tests, and regression tests. Understanding the taxonomy helps teams allocate testing effort effectively.
A mix of manual and automated. Automated functional testing typically uses frameworks like Playwright, Cypress, or Selenium for UI testing, and Jest/Mocha for unit/integration testing. The gap: most teams automate unit tests well but struggle with UI-level functional testing.
Zerocheck automates UI-level functional testing - the layer most teams struggle with. Browser-step specs describe functional requirements. Tests verify that features work as described, not only that elements exist.