You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: .claude/skills/integration-test/SKILL.md
+9-2Lines changed: 9 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
name: integration-test
3
3
description: Run integration tests against example projects in the examples/ directory. Use when the user wants to validate PreviewsMCP's build system support, rendering, interaction, or hot-reload end-to-end.
Run integration tests for PreviewsMCP example projects.
@@ -19,7 +19,14 @@ Run integration tests for PreviewsMCP example projects.
19
19
20
20
3.**For each example**, read its `README.md` and follow the "Integration Test Prompt" section. The README contains the exact steps to execute, including which MCP tools to call and what to verify.
21
21
22
-
4.**Report results.** For each example, report pass/fail per test step. Summarize at the end.
22
+
4.**Test playground.** After example tests, run the playground integration test:
23
+
- Call `preview_playground` with no arguments (default code) — verify it returns a session ID and file path
24
+
- Take a snapshot — verify it renders the default "Hello, playground!" view
25
+
- Call `preview_playground` with custom `code` containing a simple SwiftUI view — verify it compiles and renders
26
+
- Take a snapshot of the custom code session — verify the custom view appears
27
+
- Stop both playground sessions
28
+
29
+
5.**Report results.** For each example, report pass/fail per test step. Summarize at the end.
0 commit comments