repository·main·Indexed 19 days ago
https://github.com/revylai/revyl-cliA command-line interface for Revyl, an AI-powered mobile testing platform for iOS, Android, Expo, React Native, and Flutter. The CLI enables developers to define tests in natural language or YAML, manage end-to-end (E2E) tests, and run them on cloud devices. It features a Model Context Protocol (MCP) server for integration with Cursor AI, supports agent-driven and CLI-driven PR reviews in CI/CD pipelines, and provides tools for syncing local test files with the Revyl platform.
The Revyl plugin for Cursor integrates mobile device testing and development workflows directly into the Cursor AI agent. It provides:
revyl-cloud-agent, revyl-mcp-dev-loop, and revyl-ci-sync.runtime-manifest.json upon MCP startup.The revyl-cli skill acts as a router to more specialized skills based on your specific task. Choose the skill that matches your goal:
revyl-cli-dev-loop: For local development loops and exploratory path capture.revyl-cli-create: For authoring robust YAML tests.revyl-cli-auth-bypass: For setting up authenticated app state specifically for tests.revyl-cli-analyze: For triaging failed runs.Revyl tests are defined as a series of blocks in a YAML file. Each block represents a specific type of action or assertion.
instructions: Defines a single meaningful user intent (e.g., "Sign in").validation: A durable assertion about user-visible state (e.g., "The home screen is visible").manual: Framework actions like wait, go_home, navigate, set_location, kill_app, or open_app.extraction: Reads screen data into a specified variable_name.code_execution: Runs a saved script or lightweight inline code.module_import: Imports a reusable module by name.if / while: Conditional logic and loops containing nested blocks.test:
metadata:
name: smoke-login-ios
platform: ios
tags:
- smoke
build:
name: ios-test
variables:
email: "{{global.login-email}}"
blocks:
- type: instructions
step_description: "Sign in with {{email}}."
- type: validation
step_description: "The home screen is visible."When analyzing test failures with the revyl-mcp-analyze skill, use the following classification rules to categorize the root cause:
For Expo Router apps, implement the bypass using a dedicated module and a root-level hook. It is recommended to add a 'backstop route' at app/revyl-auth.tsx to handle unmatched routes and provide visible feedback if the bypass fails.
app/_layout.tsx: Install the useRevylAuthBypass hook here to handle initial and runtime Linking events.app/revyl-auth.tsx: A backstop route that calls the handler to prevent unmatched-route screens.src/auth/revylAuthBypass.tsx: The core logic containing token, role, and redirect validation.import { useEffect } from "react";
import * as Linking from "expo-linking";
import { router } from "expo-router";
const allowedRedirects = new Map([
["/account", "/(tabs)/account"],
["/cart", "/cart"],
["/checkout", "/checkout"],
]);
const allowedRoles = new Set(["buyer", "support"]);
function launchValue(key: string) {
return process.env[key];
}
export function handleRevylAuthBypass(rawURL: string) {
const url = new URL(rawURL);
if (url.protocol !== "myapp:" || url.hostname !== "revyl-auth") {
return false;
}
const enabled = launchValue("REVYL_AUTH_BYPASS_ENABLED") === "true";
const expectedToken = launchValue("REVYL_AUTH_BYPASS_TOKEN");
const token = url.searchParams.get("token");
const role = url.searchParams.get("role") || "buyer";
const redirect = url.searchParams.get("redirect") || "/account";
const route = allowedRedirects.get(redirect);
if (!enabled) throw new Error("Revyl auth bypass is disabled");
if (!expectedToken || token !== expectedToken) throw new Error("Bad Revyl auth bypass token");
if (!allowedRoles.has(role)) throw new Error("Role is not allowlisted");
if (!route) throw new Error("Redirect is not allowlisted");
createTestSession({ role });
router.replace(route);
return true;
}
export function useRevylAuthBypass() {
useEffect(() => {
Linking.getInitialURL().then(url => {
if (url) handleRevylAuthBypass(url);
});
const subscription = Linking.addEventListener("url", event => {
handleRevylAuthBypass(event.url);
});
return () => subscription.remove();
}, []);
}When implementing the Android auth bypass, adhere to these security and safety practices:
REVYL_AUTH_BYPASS_ENABLED=true.role and redirect allowlists small and specific to the application's needs.Follow these rules to ensure high-quality, maintainable test YAML:
When using the revyl-mcp-dev-loop skill, adhere to these execution guardrails to ensure reliable automation:
interact tool. For example: interact(task="Tap the Sign In button").screenshot() before performing any action that depends on the current UI state to ensure your mental model matches the device.screenshot() to verify the outcome. You are allowed a short burst of up to two actions before verification for obvious two-step flows (e.g., entering a password and hitting enter).start_dev_loop.setup_status only when the user explicitly asks for setup diagnostics.next_steps as advisory only.Revyl adapts its development loop based on your mobile framework:
revyl-cli-auth-bypass to handle authentication friction.revyl dev installs and runs the build. Use revyl dev rebuild --wait for explicit rebuilds.build.platforms.<key>.output artifact as the app. Iterate between the build command and revyl dev rebuild --wait.The plugin manages the Revyl CLI runtime to ensure environment consistency. Each plugin release pins an immutable Revyl CLI GitHub Release and specific SHA-256 checksums for all supported OS/architectures.
Bootstrap Logic:
Custom Binaries:
Developers can bypass the automatic bootstrap by selecting an existing executable using the REVYL_BINARY environment variable.
When implementing the Revyl iOS Auth Bypass, adhere to these security best practices to prevent accidental production exposure:
REVYL_AUTH_BYPASS_ENABLED=true.role and redirect allowlists small and specific to the testing needs.