Missing Data

This guide helps troubleshoot issues where test results aren't appearing in Spekra.

No Results Appearing

Enable Debug Mode

First, enable debug mode to see what's happening:

['@spekra/playwright', {
  apiKey: process.env.SPEKRA_API_KEY,
  debug: true,
}]

Check the output for:

• Number of results captured
• API request status
• Any error messages

Common Causes

1. Reporter is Disabled

Check that enabled isn't set to false:

// This disables reporting!
['@spekra/playwright', {
  apiKey: process.env.SPEKRA_API_KEY,
  enabled: false, // Remove this line
}]

Also check environment variables:

echo $SPEKRA_ENABLED  # Should not be "false"

2. Wrong Test Config

Ensure the reporter is in the correct config file:

• playwright.config.ts for Playwright
• jest.config.js for Jest

And that you're running tests with that config:

# Ensure using correct config
npx playwright test --config=playwright.config.ts

3. Tests Didn't Run

Verify tests actually ran:

npx playwright test --list

If no tests are found, check your test file patterns.

Partial Results

Some Tests Missing

1. Check for Errors in Debug Output

Some tests may fail to be captured due to:

• Malformed test data
• Very long error messages
• Special characters in test names

2. Check Test Status

Only these statuses are captured:

• passed
• failed
• skipped
• flaky

Tests with other statuses may be ignored.

3. Verify All Shards Reported

For sharded tests, ensure all shards complete:

# GitHub Actions example
strategy:
  fail-fast: false  # Important! Let all shards complete
  matrix:
    shard: [1, 2, 3, 4]

Missing Metadata

Git Information Missing

If branch/commit info isn't appearing:

1. Ensure you're running in a git repository
2. Check that .git directory exists
3. Verify git is installed and accessible

git rev-parse HEAD  # Should output commit SHA

CI Information Missing

CI metadata requires specific environment variables. Check they're set:

GitHub Actions:

echo $GITHUB_WORKFLOW
echo $GITHUB_RUN_ID

GitLab CI:

echo $CI_JOB_URL
echo $CI_PIPELINE_ID

Delayed Results

Results Appear Late

Spekra processes results in near real-time, but delays can occur:

1. Network issues - High latency can delay submission
2. Large batches - Many tests take longer to process
3. CI delays - Job may not have completed yet

Refresh the Dashboard

Try:

• Hard refresh (Ctrl/Cmd + Shift + R)
• Clear browser cache
• Check a different time range

Wrong Organization

Results in Wrong Dashboard

If results appear in a different organization:

1. Check which API key you're using
2. Verify the key belongs to the correct org
3. Create a new key in the correct organization

# Check your current key
echo $SPEKRA_API_KEY | cut -c1-10

Compare with keys in Settings → API Keys.

Duplicate Results

Same Results Appearing Twice

This can happen if:

1. Same runId used twice - Ensure runIds are unique per run
2. Reporter configured twice - Check config for duplicate entries
3. Test ran twice - Check CI workflow for duplicate jobs

Solution

Generate unique runIds:

['@spekra/playwright', {
  apiKey: process.env.SPEKRA_API_KEY,
  // runId is auto-generated, don't set it manually
}]

Data Retention

Old Results Disappeared

Spekra retains data based on your plan:

Results older than your retention period are automatically deleted.

Still Having Issues?

Collect this information before contacting support:

1. Debug output from a test run
2. Your test framework and version
3. CI provider (if applicable)
4. Approximate time of the missing results
5. Any error messages

# Capture debug output
SPEKRA_DEBUG=true npx playwright test 2>&1 | tee debug-output.log

# Get versions
npx playwright --version
npm list @spekra/playwright