​
Overview

PlayerZero examines similar code changes and historical fixes across the codebase to identify patterns and potential solutions, while also considering the specific user interactions that triggered the issue. Follow this guide to learn how to leverage PlayerZero generated functional tests.

​
Prerequisites

​
Source Control Management (Codebase)

Connect your codebase to PlayerZero enables PlayerZero to map runtime errors, traces, and sessions back to the exact lines of code in your repository.

This is the foundational integration — all other data sources (traces, tickets, sessions) rely on it to establish full context across your stack.

→ To set this up, navigate to the SCM Setup Guide.

​
Process

This guide walks you through how to locate and interpret functional tests automatically generated by PlayerZero when reviewing pull requests.

​
1. Search for your PR

Navigate to the Pull Requests page and find your PR by using the search bar.

  • Search by title, branch name, or keywords within the PR content.

​
2. Open the PR Details View

Click your PR to open the details view and access functional test data.

  • Use the ‘Summary’ tab to see a centralized test list.
  • Use the ‘Files Changed’ tab to view test groupings by file, along with their completion status and related code.

​
3. Interact with the Functional Test Checklist

Review PlayerZero’s auto-generated comment, which includes a test summary and links.

  • The comment updates automatically when new commits are pushed.
  • Click ‘View more in PlayerZero’ to explore the full test checklist and trace details.

​
Ask the AI about Test Insights

Want to understand test coverage quickly? You can interact directly with PlayerZero’s AI Chat to investigate test scope, impact, and history across your pull request.

👉 Start an AI Chat session

Use the categories below to guide your investigation with the right level of context.

Contextual Scenarios

Prompting Tips

  1. Anchor concepts together – “How does [Service A] interact with [Library B]?”
  2. Adjust context scope – Zoom in on specific files or pull system-wide dependencies.
  3. Define the output you want – Ask for code snippets, summaries, relationships, or histories.
  4. Follow the thread – Use follow-ups like “Where else is this service used?”

​
Summary and Next Steps

By following this process, you’ve learned how to efficiently locate and interpret the functional tests PlayerZero generates for each pull request. These steps ensure that you’re not only reviewing code changes but also understanding the broader context and test coverage they require.

Was this page helpful?