tester

Create and verify end-to-end and unit tests with Playwright.

Updated May 12, 2026

Search Tags:#testing #test automation #unit testing #playwright #e2e testing

Ready to run

npx skills add https://github.com/HillBombCreations/vivreal-skills --skill tester-hillbombcreations

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tester
Source: https://github.com/HillBombCreations/vivreal-skills/tree/main/vivreal-workflow/skills/tester
Command: npx skills add https://github.com/HillBombCreations/vivreal-skills --skill tester-hillbombcreations

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit ensures the integrity and accuracy of your test suite by providing guidelines and tools for effective testing protocols, including automated Playwright tests and unit tests for backend systems.

Core Features & Use Cases

Playwright e2e + Unit Tests: Writes automated tests using Playwright to cover end-to-end scenarios and unit tests for backend systems.
Behavioral Testing: Validates the behavior of code against specified requirements rather than snapshotting current behavior.
Test Verification Protocol: Standardizes the process of test verification, emphasizing writing failing tests first and fixing the code rather than the test.

Quick Start

To execute tests, use the 'tester' skill followed by the test file name, e.g., 'tester my-test-file.test.js'.

Frequently Asked Questions about tester

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I write Playwright tests for end-to-end scenarios?▼

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.

What is the best way to verify unit tests for backend systems?▼

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.

Why does behavioral testing validate code against requirements instead of snapshots?▼

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.

Does the test verification protocol allow fixing tests when they fail?▼

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.

Can I run automated e2e tests without setting up complex dependencies?▼

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.