Test App Automation

What This Skill Does

The Test App Automation skill allows users to automate operations for a Test App using Composio's Test App toolkit via Rube MCP. It is designed for developers and QA engineers who need to automate testing and management of a test application. The skill requires an active Test App connection and Rube MCP setup.

When to Use

Automating test executionManaging test dataCreating test reportsSetting up test environmentsRunning integration testsAutomating deployment to test

Key Features

Automates Test App tasks via Rube MCPUses Composio's Test App toolkitDiscovers available tools dynamicallyChecks connection status before executionEnforces schema compliance for argumentsProvides example workflows

Manual Installation

Test App Automation via Rube MCP

Automate Test App operations through Composio's Test App toolkit via Rube MCP.

Toolkit docs: composio.dev/toolkits/test_app

Prerequisites

Rube MCP must be connected (RUBE_SEARCH_TOOLS available) Active Test App connection via RUBE_MANAGE_CONNECTIONS with toolkit test_app Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds Call RUBE_MANAGE_CONNECTIONS with toolkit test_app If connection is not ACTIVE, follow the returned auth link to complete setup Confirm connection status shows ACTIVE before running any workflows

Tool Discovery

Always discover available tools before executing workflows:

RUBE_SEARCH_TOOLS queries: [{use_case: "Test App operations", known_fields: ""}] session: {generate_id: true}

This returns available tool slugs, input schemas, recommended execution plans, and known pitfalls.

Core Workflow Pattern

Step 1: Discover Available Tools

RUBE_SEARCH_TOOLS queries: [{use_case: "your specific Test App task"}] session: {id: "existing_session_id"}

Step 2: Check Connection

RUBE_MANAGE_CONNECTIONS toolkits: ["test_app"] session_id: "your_session_id"

Step 3: Execute Tools

RUBE_MULTI_EXECUTE_TOOL tools: [{ tool_slug: "TOOL_SLUG_FROM_SEARCH", arguments: {/ schema-compliant args from search results /} }] memory: {} session_id: "your_session_id"

Known Pitfalls

Always search first: Tool schemas change. Never hardcode tool slugs or arguments without calling RUBE_SEARCH_TOOLS Check connection: Verify RUBE_MANAGE_CONNECTIONS shows ACTIVE status before executing tools Schema compliance: Use exact field names and types from the search results Memory parameter: Always include memory in RUBE_MULTI_EXECUTE_TOOL calls, even if empty ({}) Session reuse: Reuse session IDs within a workflow. Generate new ones for new workflows Pagination: Check responses for pagination tokens and continue fetching until complete

Quick Reference