UReport / Docs / Troubleshooting Back to Docs

Troubleshooting

Find solutions to common issues and learn how to resolve problems.

Common Issues

Tests are not appearing in UReport

If your tests are not showing up, check the following:

1

Verify API Response

Check that your build creation returns a valid _id:

Expected Response
{
  "_id": "65abc123def456789",
  "product": "MyApp",
  "type": "API"
}
2

Check build_id in Test Submissions

Ensure each test includes the correct build_id from step 1.

3

Verify Product Lane Selection

In UReport, make sure you've selected the correct Product and Type in the filter.

4

Check Date Range

Ensure your date range filter includes the time when tests were submitted.

Dashboard widgets show "No Data"

Widgets showing no data usually indicate a filter mismatch:

Check Filters

  • Verify Product Lane selection matches your data
  • Check date range includes your test executions
  • Ensure status filters aren't excluding all results

Widget Configuration

  • Verify widget's product lane settings
  • Check if multi-query is configured correctly
  • Ensure relation filters match your data
Test relations are not appearing in filters

Relation data (components, teams, tags, customs) lives in a separate TestRelation record — not on the test result itself. There are two ways to supply it:

1

Option A — POST /api/test_relation (recommended)

Submit a TestRelation record keyed by UID, product, and type:

POST /api/test_relation
{
  "uid": "my-test-uid",
  "product": "MyApp",
  "type": "API",
  "components": [{"name": "Login"}],
  "teams": [{"name": "Frontend"}],
  "tags": [{"name": "smoke"}],
  "customs": {"Browser": ["Chrome"], "OS": ["Windows"]}
}
2

Option B — test.info (inline, overrides TestRelation)

Include tags, teams, components, or custom keys inside the test's info field. These override TestRelation values when present:

POST /api/test — using info
{
  "build_id": "65abc123def456789",
  "name": "MyTest",
  "status": "PASS",
  "info": {
    "tags": ["smoke"],
    "teams": ["Frontend"],
    "components": ["Login"],
    "Browser": "Chrome"
  }
}

Do not pass components, teams, or tags as top-level fields in the test POST body — the Test model has no such fields and they will be silently ignored.

After submitting relation data, also add the relation dimension to Product Lane Settings → Relations Filter so it appears in the UI filter panel.

Custom relation dimensions not showing in the filter panel

Custom dimensions (e.g. Browser, OS, Priority) come from TestRelation.customs or from arbitrary keys in test.info. After the data is in UReport, the dimension must be explicitly enabled in Product Lane Settings:

1

Verify data is present

Check a TestRelation record for this product/type contains the custom key in customs, or verify a test result has the key in info.

2

Add to Product Lane Settings

Go to Settings → Product Lane Settings → Relations Filter and add the key name (e.g. Browser) as a default filter.

Performance Issues

Dashboard is loading slowly

Reduce Date Range

Large date ranges load more data. Try reducing to last 7 or 14 days.

Reduce Widget Count

Too many widgets on one dashboard can slow loading. Consider splitting into multiple dashboards.

Use Specific Filters

Apply product lane filters to reduce the data set being queried.

Launches page is slow with many tests

Use Pagination

Reduce page size to 25 or 50 items instead of showing all.

Apply Filters First

Filter by status, team, or component before loading all data.

Try Tree View

Tree view can be more efficient for large test suites with hierarchical organization.

Integration Problems

API returns 401 Unauthorized

UReport supports two authentication methods. Use whichever fits your context:

API Token (recommended for CI/scripts)

Generate a personal API token in your profile: click your avatar → Edit Profile → API Token → Generate Token. Use it in every request:

bash
Authorization: Bearer <your-api-token>

Session Cookie (browser / interactive)

Call POST /api/login with username and password. The response returns a sessionId. Send it as a cookie in subsequent requests:

bash
Cookie: connect.sid=<sessionId>

For automated pipelines pushing test results, API token + Authorization: Bearer is the cleanest approach. Reporter plugins handle this automatically when you provide the token in the config.

API returns 400 Bad Request

Bad request errors indicate invalid data format:

Check the response body for specific error messages about which fields are invalid.

Required Fields for Builds

  • product (string, required)
  • type (string, required)

Required Fields for Tests

  • build_id (string, required)
  • name (string, required)
  • status (string, required)

Display Issues

Charts are not rendering correctly

Refresh the Page

Sometimes a simple refresh resolves rendering issues.

Clear Browser Cache

Clear your browser cache and reload the page.

Check Widget Size

Some charts need minimum dimensions. Try resizing the widget larger.

Theme colors look wrong

UReport supports light and dark themes. If colors appear incorrect:

1

Check Theme Setting

Go to your profile settings and verify the selected theme.

2

Clear Cache

Clear browser cache to ensure latest styles are loaded.

3

Check Browser Extensions

Some browser extensions (like dark mode extensions) can interfere with themes.

Getting Help

How do I report a bug or request a feature?

Report a Bug

When reporting bugs, include:

  • Steps to reproduce
  • Expected vs actual behavior
  • Browser and OS information
  • Screenshots if applicable

Request a Feature

For feature requests, describe:

  • The problem you're trying to solve
  • Your proposed solution
  • How it would benefit your workflow