Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.playmatic.ai/llms.txt

Use this file to discover all available pages before exploring further.

Use the @playmatic command in Slack to interact with the Playmatic agent. Simply describe what you need in natural language, and the agent will create or update tests in your playmatic/ folder. Each workflow below includes example instructions and best practices to help you get reliable and fast coverage.

​
Add regression tests

If you need to add coverage for your app, we recommend adding tests incrementally by pages or by feature. Breaking down the task lets the agent create more comprehensive tests. 
@playmatic, add some regression tests for the purchasing flow

​
Test new features

When testing new features, give the agent clear direction on what “good” looks like. The more specific your description, the better the agent can test the intended behavior. You can provide context in several ways: Using a spec or user stories: 
@playmatic, we're developing a new feature on this branch. Here are the user stories from the spec:
[paste your user stories here]
Can you help me write some tests for this?
Using a test plan: 
@playmatic, we're developing a new feature. Here's our test plan:
[paste your test plan here]
Can you help me write tests based on this?
Using natural language description: 
@playmatic, we're developing a new feature on the pr-14124 branch. The user should be able to create, delete, and copy todos in the dashboard. Can you write some tests for this?
The more specific you are about expected behavior, the better the agent will test the intended paths. Vague instructions will only catch obvious functional bugs.

​
Maintain existing tests

Update your tests to match changes in your application, ranging from simple selector updates to complete UI redesigns. Just tell the Playmatic agent which tests need updating and point it to the new source of truth (like a specific branch or environment). Updating tests after selector changes: 
@playmatic, the signup test is failing because we updated the form selectors. Can you update it to match what's currently on production?
Updating tests for a UX/UI revamp: 
@playmatic, we updated the UX of the inventory management feature. Can you update the related tests to match the staging branch?
Rewriting tests after major changes: 
@playmatic, we fully rebuilt the dashboard. Can you delete the existing dashboard tests and rewrite them based on the new interface?
Update tests after the new working implementation is committed to a branch. This gives the agent a clear source of truth to test against.

​
Next steps

Test Development

Learn more about the test creation & maintenance workflow.

Running Locally

Learn about setting up and running Playmatic tests locally.