◈ Acquista Crediti

I crediti non scadono mai. Usali quando vuoi.

🔒 Pagamento sicuro via LemonSqueezy

Frontend Testing Engineer

Write unit, integration, and end-to-end tests for web UIs using Vitest, Testing Library, Playwright, and Cypress with a component-first testing philosophy.

The Frontend Testing Engineer is an AI assistant that specializes in the art and science of testing web user interfaces. Good UI tests are notoriously hard to write well — they need to be fast, maintainable, resistant to refactoring, and actually catch the bugs that matter. This assistant knows how to achieve all of that across the full testing pyramid.

At the unit and integration level, the assistant works with Vitest and Jest for test runners, React Testing Library, Vue Testing Library, and Svelte Testing Library for component testing with a user-centric approach. It follows the Testing Library philosophy rigorously: query by role, label, and accessible name — not by CSS selectors or test IDs — so tests reflect what real users experience and survive implementation refactors.

At the end-to-end level, it writes Playwright and Cypress tests that cover critical user journeys, form submissions, authentication flows, and multi-step interactions. It knows how to write stable E2E tests that don't flake: proper waiting strategies, network interception, test isolation, and fixture management.

The assistant also covers visual regression testing with Playwright screenshots and Chromatic/Storybook integration, component testing in isolation with Storybook's play function and interaction tests, and accessibility testing automation with axe-core and jest-axe.

Ideal use cases include writing tests for an existing component that has no test coverage, reviewing and improving a flaky or brittle test suite, designing a testing strategy for a new feature or refactor, setting up a CI pipeline with appropriate test stages, or learning how to test a specific UI pattern (modals, data tables, infinite scroll, drag-and-drop) correctly.

Expected results are test files that are readable as specifications, run reliably in CI, and fail for the right reasons — catching real regressions without false positives that erode team trust in the test suite.

🔒 Unlock the AI System Prompt

Sign in with Google to access expert-crafted prompts. New users get 10 free credits.

Sign in to unlock