$ loading_
Write and run Markdown-driven end-to-end tests for Relay apps.
The material indicates an open-source, prompt/documentation-style testing skill with no required secrets and no declared remote endpoints. Overall risk is low, but because it discusses writing and running E2E tests with local compilation/execution context, any real implementation should still be verified for local code execution and test dependency handling.
The material explicitly states that no keys or environment variables are required. No API tokens, account credentials, or other sensitive authentication data are requested, so credential leakage or misuse risk appears low.
No remote endpoints are declared. The GraphQL server mentioned appears to be part of the local test fixture context, and the material does not show user data being sent to external networks.
System checks classify it as prompt-only. Although the README describes a test harness that compiles and runs tests, the audited material itself does not grant this skill direct ability to execute local code or spawn processes.
The material focuses on self-contained `.md` test files, snapshots, and reference docs. It does not request broad filesystem access, user private data, or excessive authorization scope.
Positive signals include being open-source on GitHub and pointing to the facebook/relay repository, making it auditable. However, the license is unspecified, community adoption is shown as 0 stars, and maintenance status is unknown, so it is prudent to verify the exact directory, recent activity, and dependency chain.
Copy the install command and let the AI configure it · recommended for beginners
Please install the "relay-e2e-test" skill from askskill: 1. Download https://raw.githubusercontent.com/facebook/relay/main/packages/relay-e2e-test/.llms/skills/relay-e2e-test/SKILL.md 2. Save it as ~/.claude/skills/relay-e2e-test/SKILL.md 3. Reload skills and tell me it's ready
Create a markdown-driven E2E test skeleton for a Relay page login flow, including fixture structure, server mocks, client interaction steps, and snapshot assertions.
A starter test file template with Markdown format, test steps, and assertion examples.
Here is an incomplete Relay E2E test. Complete the interaction DSL to cover button clicks, form input, waiting for requests, and verifying page state changes.
Completed interaction steps that describe the full user flow and support test execution.
This Relay Markdown E2E test failed on snapshot comparison. Analyze possible causes and suggest debugging steps for fixtures, server responses, and client rendering differences.
A troubleshooting checklist explaining likely snapshot failure causes and recommended fixes.
Markdown-driven end-to-end tests for Relay. Each test is a self-contained .md file that defines a GraphQL server (via Grats), a Relay-powered React component, and optional interaction steps. The test harness extracts the code blocks, compiles them with Grats + relay-compiler, renders with React Testing Library, runs interactions, and snapshot-tests the output.
Tests run against Relay runtime packages from source, so changes are reflected immediately without a build step.
Read the appropriate reference file based on your task:
Get idiomatic Relay guidance for React code, debugging, and code reviews.
Run, debug, and update Pysa taint analysis end-to-end integration tests.
Apply the right commit prefix, reviewer, and test plan for code changes.
Debug Pysa false negatives by comparing outputs and locating lost taint flows.
Read, write, and debug Pysa JSON taint models and .models output.
Understand the Pyre/Pysa architecture and locate key implementations quickly.
Design robust Playwright E2E tests, CI pipelines, and flaky test mitigation.
Run, filter, and debug unit tests in the VS Code repository.
Automate end-to-end QA testing with a computer-use SDK.
Build features, fix bugs, and refactor code with test-driven development.
Automatically repair failing Playwright E2E tests and verify fixes end to end.
Manage EchoRelay relay projects, keys, logs, and billing from MCP clients.