Shared library

The shared library is your workspace's single, org-wide view of everything your team has built to test with — every test case and every test plan, across all of your projects. It's where teams go to find existing coverage and reuse it instead of quietly rebuilding the same checks in a new project.

What it is#

The library has two views:

• Cases (/library/cases) — every test case in the workspace, from all projects, in one searchable list.
• Plans (/library/plans) — every test plan in the workspace, again across all projects.

Where a project's own Test cases and Test plans tabs are scoped to that one app, the library zooms out to the whole organization. That makes it the right place to answer questions like "do we already test the checkout flow anywhere?" or "which plans cover the login experience?"

Why use it#

• Find existing coverage fast — search across every project at once instead of opening each one.
• Reuse instead of rebuild — when a flow has already been tested elsewhere, copy the approach rather than authoring it again.
• Avoid duplication — spot overlapping cases so teams aren't maintaining the same check in two places.
• Onboard quickly — a new teammate can browse the library to learn what the team already tests and how.

Find and reuse coverage#

1. 1

   Open the library

   From the main navigation, open the shared Library, then choose Cases or Plans.
2. 2

   Search across projects

   Browse or search the full org-wide list. Each item shows which project it belongs to, so you can see where coverage already exists.
3. 3

   Open an item to learn from it

   Open a case or plan to see exactly how the flow was tested — the steps, expectations, and recent results.
4. 4

   Reuse the approach

   Recreate the same coverage in your project, or fold an existing plan into your release checks. The library shows you the pattern; you apply it where you need it.

Tips#

• Use clear, consistent names for cases and plans — they're far easier to find in an org-wide list when they read like plain English.
• Before authoring a new test case, search the library first; the flow you need may already be covered.
• Treat the library as your team's shared catalog of what "tested" means across the product.

Related#