Document Playwright guidelines for end-to-end HTTP API tests.
npx skills add https://github.com/Zoppy-crm/.github --skill e2e-testing-zoppy-crm
Please help me install this Agent Skill. Skill: e2e-testing Source: https://github.com/Zoppy-crm/.github/tree/main/skills/e2e/e2e-testing Command: npx skills add https://github.com/Zoppy-crm/.github --skill e2e-testing-zoppy-crm
This guide codifies rules and patterns to create consistent, maintainable end-to-end HTTP API tests for the zoppy-e2e-api project, reducing flaky tests and speeding up onboarding for new test authors.
Create an e2e Playwright spec for the partners customers endpoint that authenticates with the partners fixture, performs a create-read-update-delete flow, and asserts expected status codes and response shapes.
High-intent search queries and answers about installing and using this skill.
Reliable Playwright API E2E tests require defining a project structure, authentication flows, test categories like validation and CRUD, and strict status code expectations to validate HTTP-level behavior consistently. This approach reduces flaky tests and speeds up onboarding.
Testing public webhooks and Partners API endpoints involves using specific test patterns like not-found checks and smoke tests, applying ExternalToken authentication, and validating HTTP status code conventions to ensure backend endpoint reliability.
Setting up authentication for Playwright E2E API testing involves configuring a global login flow and utilizing Partners ExternalToken authentication, alongside shared fixtures and HTTP client utilities, to access protected endpoints during test execution.
E2E HTTP API tests should include validation tests, not-found checks, full CRUD flows, and smoke checks for hard-to-test endpoints, applying serial execution rules when test order matters to maintain consistency across the suite.
Yes, running a Playwright E2E API test suite requires specific environment variables to be configured, which define operational settings and authentication credentials needed to execute the tests and generate reports correctly.
Serial execution rules in Playwright API testing should be applied when test order matters, such as during full CRUD flows where subsequent read, update, or delete operations depend on the successful completion of prior create operations.
DGouronAutomate Playwright end-to-end testing workflows with structured test organization.
HomericIntelligenceExecute Mojo or Python test suites and generate validation reports.
masang-jgkim2Automate Playwright headless/headed E2E browser tests for DQPM.
sobirdValidate Claude Code API endpoints and HTTP behavior with curl.
