Test Management Consolidation: One License

The test management sprawl problem

Your organization has three test management tools. Different teams use different tools.

Frontend team uses Zephyr for test case management. API team uses Xray (integrated into Jira). Backend team uses qTest.

You have three licenses. Three schemas. Three places where test data lives. Three sources of truth.

When you need a cross-team test report? You export from all three, manually consolidate in Excel.

When a defect spans teams? Test data is scattered across three tools.
The cost of sprawl

Three licenses cost money. Three schemas cost maintenance overhead.

Annual cost of test management sprawl: Zephyr license: 15K/year

Xray license: 12K/year

qTest license: 18K/year

Manual consolidation work: 40K/year (dev time)

Total: 85K/year

Moving to one unified schema:

WalnutAI license: 30K/year

Consolidation work (one-time): 20K

Total: 50K/year going forward

Savings: 35K/year plus better data quality
How consolidation works

Step 1: Audit your current test data

Document where your test cases live:

• Zephyr: how many test cases, projects, cycles

• Xray: how many test cases, in which Jira projects

• qTest: how many test cases, projects, requirements

Total test case count. Total data volume.

Step 2: Map the schemas

Each tool has a schema. Test cases have different structures.

Schema mapping: Zephyr schema:

  - Test Case (name, status, priority)

  - Steps (action, expected result)

  - Execution (pass/fail, tester, date)

Xray schema:

  - Test (name, status, type)

  - Steps (action, expected result, data)

  - Execution (pass/fail, tester, defect link)

qTest schema:

  - Test Case (name, status, priority, module)

  - Steps (expected result, actual result)

  - Execution (pass/fail, tester, date, version)

Build a mapping from each schema to a unified schema.

Step 3: Design unified schema Define what a test case looks like in your unified system: Unified test case schema: Test Case

• ID (unique identifier)

• Name (test case name)

• Project (which product/team)

• Status (active, deprecated, archived)

• Priority (P0-P4)

• Type (functional, integration, regression, etc)

• Steps (array of step objects)

• Execution History (array of results)

• Linked Requirements (requirement IDs)

• Linked Defects (defect IDs)

• Owner (team/person responsible)

• Created Date

• Last Modified Date This schema works across all three tools. It is your source of truth. Step 4: Migrate data from each tool Export data from Zephyr, Xray, qTest. WalnutAI provides migration connectors for each tool. Map each export to the unified schema. Transform and deduplicate. Migration steps: 1. Export from Zephyr (CSV or API)

1. Map to unified schema (field mapping)

2. Check for duplicates (same test across Zephyr and qTest)

3. Merge duplicates

4. Repeat for Xray and qTest

5. Final validation

6. Import into WalnutAI unified store
   Step 5: Retire old tools

   Once migration is complete and verified:

   • Cancel Zephyr license

   • Cancel Xray license (or downgrade to read-only)

   • Cancel qTest license

   All test data is now in WalnutAI. Single license. Single schema.

   What consolidation enables

   With unified test data:

   • Cross-team test reports (pull test results from all teams in one query)

   • Unified defect tracking (link a defect to tests across all teams)

   • Test execution analytics (coverage trends, pass rates, by project/team)

   • Requirement traceability (see which tests cover which requirements, across teams)

Automated test generation (from unified requirements schema)
The execution timeline

Typical consolidation timeline: Week 1: Audit existing test data and schemas

Week 2-3: Design unified schema and mapping

Week 4-6: Migrate data from each tool

Week 7: Validation and testing

Week 8: Retire old tools

Total: 2 months from start to full consolidation
Handling tool-specific features

Each tool has unique features. Some do not map to your unified schema.

Decide: keep that feature, or is it not critical?

Common tool-specific features: Zephyr: cycles and releases (map to version field)

Xray: Jira integration (handled by WalnutAI Jira link)

qTest: requirements management (map to requirements link)

Most features have equivalents in unified schema.

Some specialty features are deprecated. That is OK.

Data quality during migration

During consolidation, some data might be messy:

• Inconsistent naming (TestCase vs Test Case vs test_case)

• Duplicate test cases (same test exists in two tools)

• Orphaned steps (steps without test case)

• Missing status (null status field)

WalnutAI migration tools flag these. You clean them up before final import.
Verification and validation

Before retiring old tools, verify:

• Total test case count matches (Zephyr + Xray + qTest = WalnutAI)

• All executions migrated (historical test results are intact)

• All links preserved (requirement links, defect links)

• All custom fields mapped (if any)

Run spot checks on random samples from each tool. Verify accuracy.

The team transition

Teams need to shift from three tools to one.

WalnutAI provides:

• Training on unified interface

• Migration guides for each team

• Read-access to old tools (during transition) for historical reference

• Support for common workflows (test execution, result tracking)
  

  Long-term benefits After consolidation, you get: • Lower licensing costs (one license vs three) • Unified test data (single source of truth) • Cross-team visibility (reports across all teams) • Better automation (automated test generation from unified schema) • Simpler maintenance (one tool vs three) Next steps If you are managing multiple test management tools:

  1. Schedule a consolidation audit with WalnutAI

  2. Document current test data across all tools

  3. Design your unified schema

  4. Migrate in phases (one tool at a time)

  5. Retire old licenses You will save money, improve data quality, and simplify your stack.

Consolidate your test management. One license instead of three. Try It on your project https://www.walnutai.ai/