Plan your testing
Connect scope, risks, strategy and effort. All eight planning steps are available on Free.
Risk-based test planning
Turn product risk into testing direction.
Connect product scope, risks and test strategy in one plan. Work through the method yourself, bring the context into your AI coding assistant, or coordinate planning and execution with your team.
Choose where to begin.
Build with AI
Give your coding assistant product context and review the testing gaps together. Explore the Builder and Pro MCP workflow.
Coordinate your team
Take the plan into execution, share the work and connect your tools with Pro.
What needs testing?
Structure the scope where decisions differ.
Build a three-level Product Breakdown Structure for each test level. Organise systems, features and concrete components, then link the quality attributes that matter at component level.
- Add, reorder and nest PBS items up to level 3.
- Maintain a different structure where each test level needs a different view.
- Link quality attributes to the exact components assessed later.
The result is one consistent scope that can be reused in risk analysis, strategy, estimation and execution.
What matters most?
Turn product knowledge into visible priorities.
Use the Product Breakdown Structure as the working scope for Product Risk Analysis. Record business impact and likelihood for each linked component and quality; RiskRover calculates the score and risk class without replacing professional judgement.
- Assess every relevant test-level and quality combination.
- Review calculated Class A, B and C priorities in context.
- With RiskRover Pro, export the complete assessment as CSV or JSON for use outside the workspace.
Your workshop decisions stay attached to the same components that drive the test strategy.
How deeply should each area be tested?
Translate risk into usable testing direction.
Define test intensity and strategy text for each component-quality combination. Use configurable techniques to guide manual, exploratory and automation planning for light, focused and deep testing.
- See the risk score and class beside each strategy decision.
- Set intensity from 0 to 3 for the selected test level and quality.
- Keep or edit the strategy text and technique set your testers will use.
Testers choose and refine the approach. RiskRover provides context and editable guidance; it does not create or execute automated tests or generate finished test cases.
RiskRover Builder
Give your AI assistant a testing direction.
Draft product scope, compare existing tests with your Product Risk Analysis, and review proposed planning changes before saving. Builder adds MCP access for one user with the same planning and project limits as Free.
See how a solo developer can turn a payment risk into a concrete testing decision. Pro also includes MCP when you need collaboration, execution, exports or integrations.
RiskRover MCP for VS Code
Connect your project. Keep the decisions yours.
Builder and Pro include MCP access. The extension connects a supported AI client to your RiskRover project. Open the setup and capability details below.
How do I connect my coding assistant?
Create your project and configure its test levels in RiskRover first. Install the RiskRover Model Context Protocol (MCP) extension for VS Code; it bundles the server, so no separate Node.js installation is needed. Run Sign In, choose GitHub Copilot or Codex, then use the browser to choose the default project for your workspace and approve read-only or read-and-reviewed-write access. Return to VS Code and start a new agent session. Other MCP clients can use a restricted MCP-purpose token.
Which planning changes can I review and save?
Read-only access supports PRA assessment and PBS drafting. Read-and-write access supports reviewed PBS imports and reviewed Component quality, PRA, strategy, estimation, role and allocation updates. Review each proposal before approving it, then verify the saved result in RiskRover. PBS replace mode needs additional confirmation. Configure project settings and review the final test plan in the app; the MCP has no finalisation or export tool.
Who reads my code and runs my tests?
Repository content is not sent to RiskRover. The MCP server does not read workspace files or run commands; the selected AI client performs workspace inspection under its own permissions and data controls. RiskRover MCP does not create or execute automated tests. RiskRover does not guarantee complete coverage or replace professional judgement.
What can I reuse, share or export?
Free and Builder let one user work through all eight planning steps and review the in-app Master Test Plan. Pro adds collaboration, execution, reusable product baselines, Word test-plan and PRA exports, integrations and general API access. RiskRover supports 11 interface languages.
Effort estimation · Budget and resources
Connect testing effort to budget.
Set baseline hours per test level, then estimate each component from its strategy intensity, size and complexity. RiskRover totals the result across qualities and test levels.
- Adjust baseline hours independently for every test level.
- Review the calculated hours beside intensity, size and complexity.
- Allocate activity hours to roles and rates, then compare planned cost and capacity with your budget.
In this fictional payment upgrade, new payment functionality at System level is estimated at 18 hours: 8 baseline hours × 1.5 testing depth × 1.5 size × 1 complexity. Existing components retain their risk ratings and receive smaller regression allowances. This is one component-quality estimate, not the whole project.
Master Test Plan
Generate the Master Test Plan from the work you already did.
Review a document-style Master Test Plan built from project scope, stakeholders, test levels, quality attributes, environments, risks, strategy, effort, budget, roles and planning assumptions.
- Review document completeness and warnings before export.
- Set the plan version and plan date in the preview.
- Export a ready plan to Word from a RiskRover Pro workspace.
The plan becomes an output of the structured project work instead of a document that must be recreated manually.
Continue with Pro · Execution setup and planning
Turn the strategy into a plan the team can steer.
Plan who will test what, when it can happen and how much effort it needs. Free covers manual planning; Pro adds execution coordinated by test activities, delivery work or a mix of both.
- Allocate Activities to Resources or Resource Groups and record daily effort.
- Track evidence, Test Attention and follow-up alongside planned and actual effort.
- Keep Plan-based Activities separate from Delivery-based Work Items without losing one project timeline.
Choose Plan-based, Delivery-based or Mixed execution for each test level. Planning Periods group work in time; shared Milestones mark review points.
Integrations
Work with the tools your team already uses.
Reuse your risk-assessed product structure in supported test repositories, or bring selected delivery scope into planning. Pro includes personal connections with optional project overrides.
Azure DevOps
Bring selected Iterations and delivery scope into planning; maintain the PRA-derived hierarchy in Azure Test Plans. Assignment and status stay in Azure.
Jira & Xray
Bring selected Sprints and issues into planning; maintain PRA-derived folders in an Xray Test Repository. Assignment and status stay in Jira.
TestRail
Maintain PRA-derived sections below an existing TestRail root. Test cases, runs, milestones and statuses remain in TestRail.
API
Create expiring personal API tokens for scripts and API clients, with read-only or read-and-write scope. The full token is shown once when it is created.
RiskRover also includes PRA repository connections for Zephyr Scale and Qase. Check the integration guide for each provider’s supported workflow and limits.
Choose the way you work.
Free for manual planning. Builder for AI-assisted planning with one user. Pro for collaboration, execution, exports and integrations.
Product questions
Have a question about your setup?
Tell us what you want to do with RiskRover and we will explain whether it is supported and how it fits into your workflow.
Start free when you are ready to try the complete planning flow. Use this form for a specific capability, integration, export, API or security question.
Start with your project
Turn your own product risk into testing direction.
Start free with one user. Move to RiskRover Pro when the wider team needs the same direction.