Generate Functional Tests with Context from your Entire Codebase
PlayerZero generates functional tests with full codebase and user context to ensure your pull requests are validated with precision and depth.
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.
→ 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.
Use the categories below to guide your investigation with the right level of context.
Contextual Scenarios
Understanding Test Scope – What your functional tests are actually covering
Understanding Test Scope – What your functional tests are actually covering
Context Scenarios:
- You’re reviewing a PR and want to see which files are covered by functional tests.
- You’re checking whether the tests align with your code changes.
- You want to identify untested parts of your PR.
- You’re distinguishing between automatically generated and manually written tests.
Investigating Code Impact – Uncover how your changes ripple through the system
Investigating Code Impact – Uncover how your changes ripple through the system
Context Scenarios:
- You’re curious about bugs historically tied to the files you edited.
- You’re tracing past customer complaints to current changes.
- You want to understand how this code affects upstream/downstream systems.
- You’re analyzing the dependency graph impact.
Improving Test Coverage – Spot gaps and reinforce your safety net
Improving Test Coverage – Spot gaps and reinforce your safety net
Context Scenarios:
- You’re looking for common test cases missed in PRs like yours.
- You’re thinking about how to test edge cases effectively.
- You’re mapping gaps in test coverage for your module.
- You’re exploring reusable tests from similar PRs.
Exploring Test History – Trace evolution and test reliability over time
Exploring Test History – Trace evolution and test reliability over time
Context Scenarios:
- You’re curious about how tests for this component have changed over time.
- You want to see trends in test coverage or failures.
- You’re investigating past test failures in the area you’re working on.
- You’re checking for known flaky tests associated with your changes.
Prompting Tips
- Anchor concepts together – “How does [Service A] interact with [Library B]?”
- Adjust context scope – Zoom in on specific files or pull system-wide dependencies.
- Define the output you want – Ask for code snippets, summaries, relationships, or histories.
- 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.