How do I create my first test using the MCP server?

Open your IDE with MCP configured, then use the AI chat to describe what you want to test. For example: "Create a test that verifies users can log in with valid credentials." The MCP server generates and runs the test automatically.

What should I include in my test description?

Describe the user flow in natural language: starting point, actions to take, and expected outcomes. Be specific about important details like which buttons to click, what data to enter, and what should happen. The AI translates your description into executable tests.

How long does it take to run my first test?

Most tests execute in 30-60 seconds. After you submit a test description via MCP, the AI generates the test, runs it in a browser, and returns results—all within about a minute for typical web flows.

What if my first test fails?

Review the test results in the MCP response or dashboard to see screenshots, error messages, and execution logs. Common first-test issues include incorrect URLs, authentication requirements, or overly vague test descriptions. Refine your description and try again.

Can I run the same test multiple times from the MCP server?

Yes, tests created via MCP are saved to your Desplega workspace. You can re-run them anytime through the MCP server, the web dashboard, or CI/CD pipelines. The test remains available across all interfaces.

How-To/MCP/Writing Effective Test Prompts

Writing Effective Test Prompts

Learn how to write concise, effective prompts for the desplega.ai MCP Server to generate high-quality automated tests.

Best Practices for MCP Prompts

Be Specific & Concise

• Include exact URLs and page names, to facilitate navigation.
• Specify the exact feature to test
• Define clear success criteria
• Mention test dependencies, if any
• Keep prompts under 50 words when possible

Use AAA Framework

• Arrange: Set up test conditions
• Act: Perform the action
• Assert: Verify the outcome
• Structure prompts with this pattern

Example Prompts

Good Prompt

use qa-use mcp

Test tagging functionality on our settings page

Verify a user can execute a CRUD action on a tag; make sure to remove all tags after the test.

Why it works: clear action, defined outcome

Poor Prompt

Checkout my last feature, it should work perfectly.

Why it fails: Too vague, no specific outcome

Pro Tips

Prompt Optimization

• Start with "use qa-use mcp" every time
• Include specific URLs and page names
• Define clear success criteria
• Use the AAA framework structure
• Test one feature at a time

Workflow Best Practices

• Always search existing tests first
• Create tests incrementally
• Monitor test results closely
• Update tests when features change
• Use descriptive test names

Next Steps

Now that you know how to write effective prompts, you're ready to start creating and running tests!