원클릭으로
revyl-mcp-create
// Create and maintain Revyl tests through MCP tools using create/update operations and execution feedback loops.
// Create and maintain Revyl tests through MCP tools using create/update operations and execution feedback loops.
Create robust Revyl E2E tests using CLI commands from app source analysis or exploratory sessions.
MCP dev-first mobile loop for reliable screenshot-observe-action execution, grounded interactions, and conversion of successful exploratory paths into tests.
Analyze failed Revyl test, workflow, and device-session reports via CLI to classify real bugs, flaky tests, infra issues, setup failures, or test-design improvements.
Native Android leaf recipe for test-only auth bypass deep links using Revyl launch intent extras.
Expo and Expo Router leaf recipe for test-only auth bypass deep links using Revyl launch variables.
Flutter leaf recipe for test-only auth bypass deep links using Revyl launch variables.
| name | revyl-mcp-create |
| description | Create and maintain Revyl tests through MCP tools using create/update operations and execution feedback loops. |
Use this skill when tests should be authored and managed through MCP tools.
create_test(name="...", platform="ios", yaml_content="...")update_test(test_name_or_id="...", yaml_content="...", force=true)run_test(test_name="...")get_test_status(task_id="...")Use the backend YAML contract returned by get_schema().
- type: instructions
step_description: "Tap Log in."
- type: validation
step_description: "The dashboard is visible."
- type: code_execution
script: "seed-user"
variable_name: seeded_user_id
- type: module_import
module: "login-flow"
- type: if
condition: "Is a cookie banner visible?"
then:
- type: instructions
step_description: "Tap Accept."
else:
- type: instructions
step_description: "Continue."
- type: while
condition: "Is there a Load More button visible?"
body:
- type: instructions
step_description: "Tap Load More."
For new authored YAML, use script for code execution and module for module imports. Legacy UUID forms may still parse for compatibility, but do not generate them.
If shared steps appear in 3+ tests:
list_modules()insert_module_block(module_name_or_id="...")