{"enrichment":{"faq":[{"a":"E2e Test guides you through writing comprehensive end-to-end tests using Playwright's testing framework. Start by setting up your test infrastructure with fixtures and helpers, then structure your tests using page object models to encapsulate UI interactions. Write test cases that validate real user workflows, use data factories to generate test data consistently, and run tests in various modes\u2014headed for interactive debugging, debug mode for step-by-step inspection, or CI mode for automated validation. E2e Test helps you organize test specs logically and apply assertion patterns that reliably verify UI behavior.","q":"How do I write and run end-to-end tests with Playwright?"},{"a":"E2e Test provides strategies for debugging, fixing, and auditing failing or incorrect end-to-end tests to improve test reliability. When tests fail, use Playwright's debug mode to step through interactions and inspect element states. E2e Test teaches you to identify flaky tests\u2014those that fail intermittently\u2014and apply robust assertion patterns and proper cleanup and teardown procedures to eliminate race conditions. Audit your test specs regularly to catch issues early, and use data-testid selector strategies for stable element targeting that won't break when UI styling changes.","q":"What is the best approach for fixing failing e2e tests and debugging them?"},{"a":"E2e Test includes guidance on automatically detecting UI changes and syncing affected end-to-end tests to keep them aligned with component modifications. By using page object models and data-testid selectors, your tests remain decoupled from brittle CSS selectors. When UI components are updated, you update the page object layer once, and all dependent tests automatically reflect those changes. This approach minimizes test maintenance overhead and ensures your test suite stays current as your Bifrost UI evolves.","q":"How does E2e Test help keep my Playwright tests in sync when UI components change?"},{"a":"E2e Test emphasizes using page object models and data factories as core patterns for maintainable and scalable test suites. Page objects encapsulate UI interactions and selectors for each page or component, making tests more readable and reducing duplication. Data factories generate consistent, realistic test data on demand, eliminating hardcoded values and making tests easier to modify. Together, these patterns enable you to write tests that are resilient to UI changes, easier to debug, and simpler to extend as your application grows.","q":"What role do page objects and data factories play in E2e Test?"},{"a":"E2e Test guides you through setting up and maintaining end-to-end test infrastructure, including Playwright fixtures, helpers, and best practices. Configure fixtures to initialize test state, manage authentication, and clean up resources between tests. Build helper utilities for common operations like navigation, form filling, and assertion validation. Organize your test spec files logically by feature or page, and establish a consistent structure for fixtures and helpers that your team can follow. E2e Test also covers Playwright CI environment setup so your tests run reliably in automated pipelines.","q":"How do I set up and maintain E2e Test infrastructure including fixtures and helpers?"},{"a":"E2e Test teaches end-to-end testing best practices that ensure your Playwright test suite is reliable, maintainable, and effective. Use data-testid selectors instead of fragile CSS or XPath selectors to target UI elements stably. Structure tests with page objects to keep selectors and interactions organized. Implement proper cleanup and teardown to prevent test pollution. Apply consistent assertion patterns that clearly express what behavior you're validating. Run tests in headed mode during development for interactive debugging, and in CI mode for automated validation. Organize your test specs by feature or page, and use data factories to generate realistic test data consistently.","q":"What are the key best practices for end-to-end testing with Playwright?"}],"shadow_tags":["test-automation","ui-testing","quality-assurance","test-maintenance","assertion-patterns","page-object-model","test-fixtures","flake-detection","test-coverage"],"summary_rewrite":"This skill equips you to write comprehensive end-to-end tests for user interface features using Playwright's testing framework. It guides you through structuring tests with page object models and data factories, enabling maintainable and scalable test suites that validate real user workflows."},"files":[{"bytes":35723,"path":".claude/skills/e2e-test/SKILL.md","sha256":"d8fecf041fcc54f5eac1856927c73b3bf8b3951bc5055ef2276c06bd5738da64","url":"https://skillfed.io/files/maximhq/bifrost/e2e-test/d0b39743/SKILL.md"}],"id":"maximhq/bifrost/e2e-test","links":{"html":"https://skillfed.io/maximhq/bifrost/e2e-test","md":"https://skillfed.io/maximhq/bifrost/e2e-test.md","repo":"https://github.com/maximhq/bifrost"},"meta":{"agents_supported":["claude-code"],"first_seen":"2026-07-28","forks":949,"language":"Go","last_updated":"2026-07-28","license":"Apache-2.0","name":"E2e Test","publisher":"maximhq","stars":6831},"relations":{"similar":[{"id":"patricio0312rev/skills/cypress-playwright-setup"},{"id":"alinaqi/maggy/playwright-testing"},{"id":"hieutrtr/ai1-skills/e2e-testing"},{"id":"hairyf/skills/e2e-testing"},{"id":"PageAI-Pro/ralph-loop/e2e-tester"},{"id":"supabase/supabase/studio-e2e-tests"},{"id":"xu-xiang/everything-claude-code-zh/e2e-testing"},{"id":"ed3dai/ed3d-plugins/playwright-patterns"},{"id":"echoVic/boss-skill/e2e-playwright"},{"id":"affaan-m/ECC/e2e-testing"}]},"slug":{"owner":"maximhq","repo":"bifrost","skill":"e2e-test"},"version":"d0b39743"}