Functional Test Case Platform for Unified Test Case Management

As the company’s business expands and organizational structures shift, the maintenance of test cases becomes increasingly difficult, especially when a product moves from one business line to another, leaving QA engineers uncertain about how to design regression test cases for the new iteration.

Currently, QA engineers often have to retrieve multiple versions of test cases from previous owners, making it hard to locate the complete, up‑to‑date set for the running version.

The article summarizes three key problems: (1) lack of a unified repository for test cases, (2) difficulty keeping cases current with business iterations, and (3) limited reusability of basic component cases during case design.

To address these issues, the Engineering Efficiency Team of the testing department launched a functional test case platform that provides unified storage, version‑driven updates, and case reuse.

Case Types

Business case: a test case for a specific requirement in a business iteration.

Business module case: an independent module extracted from a business line, such as a detail‑page module.

Base component case: a common component used across the company, like an address‑modification widget.

Business cases can reuse business module cases and base component cases, with the constraint that reused modules appear as second‑level nodes. After a business requirement is released, module owners approve and merge updates, ensuring modules stay fresh; updates to base components trigger notifications to dependent case owners.

Case Presentation

The platform displays test cases as a mind‑map, offering common node functions such as marking case type (smoke, core, missed), execution status (pass, fail), assigning owners, and quick bug reporting.

Technical Design

Cases are edited and stored in JSON format; the backend uses MongoDB with a "materialized path" approach for efficient tree storage and indexing. Version history is maintained by recording the root node ID, enabling easy retrieval and rollback of any version.

The frontend leverages the Ant Design framework and the gg‑editor mind‑map plugin to render and edit the mind‑map, displaying appropriate tags based on field types.

Future Plans

Version 1.0 already supports case copying, authoring, synchronization, and approval merging. Upcoming enhancements include:

One‑click bug creation with auto‑generated reproduction steps, eliminating the need to open TAPD.

A test plan feature that lets developers search for cases assigned to them by name and requirement.

Automatic statistics for smoke and total cases, with a forthcoming front‑end display.