MCP workflow examples

Use plan, suite or case names to describe the work. Your assistant uses the configured project and finds the matching records.

Run an entire test plan

Run every test case in the Checkout smoke test plan against https://staging.example.com and report the results in TestCollab, including screenshots for failures. When finished, summarize the results and anything you couldn’t complete.

Replace the plan name and application URL with your own.

Prepare a smoke test plan

Inspect the Checkout suite and list the high-priority cases. Show the proposed case selection before creating a smoke test plan. Assign only unassigned work to the appropriate project member.

The assistant can use get_project_context, list_test_cases, and create_test_plan. The context includes the IDs and option values needed to avoid guessing suite, field and member references.

Improve an existing test case

Find the test case for completing checkout. Propose clearer steps and expected results while preserving its intent. Show me the change before updating it.

Use get_test_case to inspect the definition, then update_test_case for the approved edit. BDD-managed definitions should be changed in their feature files instead.

Organize a suite

List the children of the Checkout suite. Propose an ordering that groups payment validation cases together. Keep the existing case definitions.

Suite tools include list_suites, get_suite, move_suite, and reorder_suites.

Inspect a plan

Read the Checkout smoke test plan and show its configurations, latest run and progress. Explain which cases still need execution.

Use get_test_plan and the plan-listing tools to gather the state before deciding what to change.

Make instructions concrete

Use recognizable names or keywords, describe the intended outcome, and include any assignment constraints. If several plans match, the assistant can ask which one you mean. Your assistant’s tool availability and confirmation behavior depend on the MCP client you use.