Feature Overview

Test Case Scenarios are an important tool in Sanplex for designing and managing test cases. They aim to improve test effectiveness and coverage by simulating real user operating contexts. A scenario typically includes elements such as role, environment (space/context), time, and motivation, making test cases closer to real-world usage. This helps uncover potential risks and bugs to ensure system quality and stability.

Sanplex supports creating and managing scenarios with unlimited hierarchy levels, enabling teams to organize test cases flexibly based on project needs.

Typical Use Scenarios

• Test Case Design: During product development, the Test team can design test cases based on scenarios to ensure coverage reflects real user operations. For example, performance issues can be managed as a scenario, grouping performance-related pages and functions under a Performance Scenario for centralized management.
• Managing Complex Products: For large and complex products, the Test team can use unlimited-level scenarios to organize test cases hierarchically by dimensions such as time and context. This supports building realistic scenarios and corresponding cases, improving visibility, maintainability, and reusability.

1. Add Scenarios to Test Cases

1.1 Add a Scenario

In the dropdown menu of the Create Case button, a new option Add Scenario is available.

图1

On the Create Scenario form, you can set the Product, Module, and Parent Scenario.

The number of scenario levels is not limited. You can create scenarios with unlimited hierarchy levels (similar to how hierarchical structures are created in other tree-style features).

图2

1.2 Edit a Scenario

On the test case list page, click Edit in the action column on the right to edit a scenario.

1.3 Delete a Scenario

On the test case list page, click Delete in the right-side action column to delete a scenario. Deleted scenarios can be restored from Admin > System > Recycle Bin.

When deleting a scenario, if it contains child data, the system will prompt whether to delete all child items as well.

图3

1.4 Scenario and Case Lists

On the list page, you can choose to display Scenarios Only so users can better understand the scenario structure.

图4

The list page also supports hierarchical display of scenarios and test cases.

图5

Importing and exporting test cases also supports scenarios.

Sanplex also supports batch updating the Scenario field for test cases.

图6

1.5 Drag to Reorder

You can drag and move scenarios to reorder them.

You can also reorder items by dragging within the scenario’s case list page. Ordering is maintained within the scenario structure.

You can drag a test case or a scenario under another scenario to reorganize the hierarchy.

图7

2. Import and Export XMind Files

2.1 Export to XMind

Select a module under the product in the left panel to export the test cases and scenario structure of that module. If no module is selected, Sanplex exports the test cases and scenario structure of all modules.

图8

During export, modules and scenarios are identified using signature strings.

图9

When importing an XMind file later, you must configure fields such as the related requirement, priority, and type for test cases based on the exported signature-string settings.

2.2 Import XMind Data

XMind import is designed for teams that have already written scenarios and test cases in XMind and want to import them into Sanplex for management and execution.

The entry point for XMind import is the same as other file import types.

图10

Note: Supported XMind versions: XMind 8 Update 8.0 to XMind 2020.

2.2.1 Edit in the Import Page

On the import page, you can select any level and double-click to edit its content.

图11

2.2.2 Import an XMind File Without Signature Strings

图12

图13

If the imported file does not contain signature strings, you must configure scenarios and test cases on the import page after import.

• Set scenarios

  Select a non-top-level node, right-click, and choose Set as Scenario. The system will automatically configure scenario levels by retaining the last three levels; all levels up to the last configurable level will be set as scenarios.

图14

For a node already set as a scenario, you can choose Unset Scenario (Before) or Unset Scenario (After) to cancel scenario settings in bulk for easier operation.

图15

If the first-level node (product name) in the imported file does not match the product selected for import, Sanplex imports the test cases into the product selected in the level-1.5 product selector (product switcher).

• Set test cases

图16

Click the circle before a node to set the test case priority.

• If the remaining three levels are not configured, the third-from-last level is automatically treated as the group title for test cases.
• If the remaining two levels are not configured, they are treated as steps and expected results.

图17

Notes:

• The XMind hierarchy must contain at least five levels: product name, scenario name, case name, steps, and expected results.
• On the import page, if there are too many levels, drag horizontally to the right to view additional content.
• The same XMind file without signature strings can be imported repeatedly; the system does not provide a duplicate-check prompt and does not deduplicate automatically.

2.2.3 Import an XMind File With Signature Strings

When importing a file with signature strings, the signature strings in the file must match the settings in the import dialog.

On the import page, you cannot change the configured scenario/case/group assignments; you can only modify the text content within levels.

图18