Getting Started with QA

This guide walks you through uploading a test document, generating test cases, and reviewing them before your first run.

​

Before You Start

You will need:

• A Starter plan or higher — QA testing is not available on the Free plan
• A connection configured for your application — the URL and credentials the tests will use to access your site (set one up here)

​

Step 1: Navigate to Quality Checking

1. Log into your account at the Marketrix dashboard
2. Click “Quality Checking” in the left sidebar

You will see the QA dashboard where all your test documents and results live.

​

Step 2: Upload a Test Document

Click Upload Document and choose your file. The system accepts these formats: You can also paste text content directly instead of uploading a file.

​

Adding Context

When uploading, you can include additional instructions (up to 1,000 characters) to help the system understand your document better. For example:

• “Focus on the checkout flow and payment processing”
• “These are admin-only features that require logging in as an administrator”
• “Test on mobile viewport sizes”

​

Selecting a Connection

Choose the connection that points to your application. This tells the system which URL and credentials to use when running the generated tests.

​

Step 3: Wait for Processing

After upload, your document goes through several stages: Processing typically takes 1-3 minutes depending on document length. The page updates automatically — no need to refresh.

​

Step 4: Review Generated Test Cases

Once processing is complete, you will see a list of generated test cases. Each test case includes:

• Title — A short description of what the test checks
• Objective — What the test is trying to verify
• Steps — The specific actions the test will perform
• Expected Outcome — What should happen if everything works correctly
• Priority — Low, Medium, or High based on the document content

Review each test case to make sure it matches your intent. The system does a good job, but your domain knowledge matters here.

​

Step 5: Refine Test Cases

If any test cases need adjustments, you can refine them:

• Edit individual test steps or expected outcomes
• Add additional instructions and re-process to generate updated tests
• Remove test cases that are not relevant

The system will create a new version when you make changes, so you can always roll back if needed.

​

Tips for Writing Effective Test Documents

The better your input document, the better your test cases. Here is what works well: Do:

• Write clear, specific user stories (“As a user, I can add items to my cart and see the total update”)
• Include expected outcomes (“The order confirmation page shows the order number”)
• Describe the user flow step by step
• Mention specific UI elements when relevant (“Click the blue Submit button”)

Avoid:

• Vague requirements (“The system should work well”)
• Implementation details (“The API should return a 200 status code”)
• Mixing multiple unrelated features in a single document

​

Troubleshooting

Document stuck on “Processing”:

• Large documents take longer. Wait a few minutes and check again.
• If it has been more than 10 minutes, try uploading a shorter version of the document.

Document shows “Failed”:

• Check that the file format is supported (PDF, Word, Text, Markdown, or CSV).
• Make sure the file is not empty or corrupted.
• Try re-uploading the document.

Generated tests do not match expectations:

• Add more detail to your additional instructions.
• Break large documents into smaller, focused ones (one per feature area).
• Use the refine option to regenerate with updated guidance.

Connection issues:

• Verify your connection URL is accessible and credentials are valid.
• Test the connection from the Connections page before uploading.

​

Next Steps