e2e-video
Skill45 starsChanged 8 months agoMITView on GitHub
Run E2E UI tests with screen recording and upload videos to blossom
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- jetpack-compose-material3-expert-skillSkill
- landSkill
- orchestrateSkill
- swiftui-expert-skillSkill
- pr-shepherdSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Run local iOS/Android UI E2E tests with automatic MP4 screen recordings, then upload to blossom for PR descriptions.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
E2E Video Recorder
Run local iOS/Android UI E2E tests with automatic MP4 screen recordings, then upload to blossom for PR descriptions.
Takes an optional platform argument: ios, android, or both (default: both).
Takes an optional test method argument to run a single test.
Step 1: Run tests with recording
iOS
PIKA_UI_E2E_RECORD_VIDEO=1 KEEP=1 just ios-ui-e2e-localSingle test method:
PIKA_UI_E2E_RECORD_VIDEO=1 KEEP=1 \
PIKA_IOS_E2E_TEST_METHOD=<testMethodName> \
just ios-ui-e2e-localAndroid (requires nix)
nix develop -c env PIKA_UI_E2E_RECORD_VIDEO=1 KEEP=1 just android-ui-e2e-localSingle test method:
nix develop -c env \
PIKA_UI_E2E_RECORD_VIDEO=1 KEEP=1 \
PIKA_ANDROID_E2E_TEST_CLASS='com.pika.app.PikaE2eUiTest#<methodName>' \
just android-ui-e2e-localStep 2: Verify recordings
Recordings are written to screen_recordings/ with timestamped filenames:
ios-ui-e2e-local-<unix_ms>.mp4android-ui-e2e-local-<unix_ms>.mp4
Verify:
ffprobe screen_recordings/<file>.mp4Step 3: Upload to blossom
cargo run -p pikahut -- blossom-upload screen_recordings/*.mp4URLs are printed to stdout, one per line. Use these in PR descriptions.
To upload a single file:
cargo run -p pikahut -- blossom-upload screen_recordings/<file>.mp4Available test methods
iOS (PIKA_IOS_E2E_TEST_METHOD)
testE2E_deployedRustBot_pingPongtestE2E_hypernoteDetailsAndCodeBlocktestE2E_multiImageGrid
Android (PIKA_ANDROID_E2E_TEST_CLASS)
com.pika.app.PikaE2eUiTest#e2e_deployedRustBot_pingPongcom.pika.app.PikaE2eUiTest#e2e_hypernoteDetailsAndCodeBlock
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

