tester

You can write Playwright tests for end-to-end scenarios by executing the tester skill with your test file name. It provides standardized protocols to validate code behavior against specified requirements across your development environment.

The best way to verify unit tests for backend systems is using a test verification protocol that emphasizes writing failing tests first. You fix the code rather than the test to ensure accurate behavioral validation against defined requirements.

Behavioral testing validates code against requirements instead of snapshots to ensure long-term reliability. This approach checks that code functions according to specified behavior rather than just matching previous outputs, preventing false positives in test suites.

The test verification protocol strictly standardizes fixing code rather than tests when failures occur. It emphasizes writing failing tests first to verify outcomes against defined behavior, ensuring your test suite maintains its integrity and accuracy.

You can run automated e2e tests without external dependencies by invoking the tester skill with your target test file. It includes built-in scripts and references to guide Playwright automation and backend unit testing directly in your environment.