Relay E2e Test

facebook/relay-e2e-test

Write and run markdown-driven e2e tests for Relay. Covers fixture format, server/client code patterns, interaction DSL, snapshots, and running tests.

2k tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

18951

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/facebook/relay --skill relay-e2e-test

What comes with it

7 201 bytes besides the instruction

references/running-tests-github.md

references/running-tests-internal.md

references/writing-fixtures.md

What it tells the agent to use

found in the instruction text

Bash runs shell commands — read the instruction before connecting

The instruction itself

2 sections, as written by the author

Relay E2E Tests

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.

References

Read the appropriate reference file based on your task:

Writing fixtures — fixture format, example, server/client code patterns, interaction DSL, snapshots. Read when creating or modifying test fixtures.
Running tests (internal) — setup, commands, and compiler resolution for fbsource / OD. Read when running tests internally.
Running tests (GitHub) — setup, commands, and compiler resolution for the OSS repo. Read when running tests on GitHub.

How to use it

Copy the folder

Take facebook/relay-e2e-test from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.