Testing
1. Introduction of Sanplex features
1.1. Core Management Framework
1.1.1 Program
1.1.2 Project
1.1.3 Product
1.1.4 Execution
1.1.5 Management Models
1.2. Dashboard
1.2.1 Getting Started with Tutorials
1.2.2 Quick Add
1.2.3 Notification Center
1.2.4 Effort Tracking
1.2.5 Dashboard - Project and Execution
1.2.6 Dashboard - My Work, Contribution, and Recents
1.2.7 Dashboard - Approval
1.2.8 Contacts
1.3. Program
1.3.1 Program List
1.3.2 Program Kanban
1.3.3 Create Program
1.3.4 Create Sub-Programs
1.3.5 Project Charter Management
1.4. Product
1.4.1 Create Product
1.4.2 Manage Modules
1.4.3 Multi-Branch and Multi-Platform Management
1.4.4 Manage Plans
1.4.5 Manage Requirements
1.4.6 Requirement Reviews
1.4.7 Requirement Status and Phase
1.4.8 Create Releases
1.4.9 Track Progress
1.4.10 Business Requirements and Multi-Level Requirements
1.5. Project
1.5.1 Scrum Project
1.5.2. Waterfall Project
1.5.2.1 Manage Project Phases
1.5.2.2 Project Design
1.5.2.3 Project Matrix
1.5.2.4 Project Reports and Earned Value Management
1.5.2.5 Project Baselines
1.5.2.6 Project Change
1.5.3. Kanban Project
1.5.3.1 Set Up Kanban Projects
1.5.3.2 Configure Kanban Boards
1.5.3.3 Use Kanban Boards
1.5.4 Hybrid Agile Project
1.5.5 Hybrid Waterfall Project
1.5.6. Project Settings
1.5.6.1 Project Setup
1.5.6.2 Project Executions
1.5.6.3 Project Requirements
1.5.6.4 Project Builds
1.5.6.5 Project Tests
1.5.6.6 Project Docs
1.5.6.7 Project Releases
1.5.6.8 Project Reports
1.5.6.9 Project Risks
1.5.6.10 Project Issues
1.5.6.11 Project Opportunities
1.5.6.12 Project Deliverables
1.5.6.13 Project Reviews
1.5.6.14 Project Process
1.5.6.15 Deliverables
1.5.6.16 Quality Assurance
1.5.6.17 Project-specific Workflow Management
1.5.7 Project Templates
1.6. Execution
1.6.1 Product Planning and Task Breakdown
1.6.2 Task Assignment and Daily Tracking
1.6.3 Build Creation and Test Requests
1.6.4 Bug Confirmation and Resolution
1.6.5 Execution Kanban Boards
1.7. Admin Settings
1.7.1. System Settings
1.7.1.1 Mode
1.7.1.2 Backup
1.7.1.3 Trash
1.7.1.4 License
1.7.1.5 Security
1.7.1.6 Cron Job
1.7.1.7 Time Zone
1.7.1.8 Rebuild Index
1.7.1.9 LDAP
1.7.1.10 Table Engine
1.7.2 Feature Options
1.7.3. Permission Management and Access Control
1.7.4. Agent Configuration
1.8. Asset Library (Premium)
1.8.1 Asset Library Management (Premium)

Execute Test Cases

2026-09-28 00:17:50
Sanplex Content
330
Last edited by Jing WANG on 2026-09-28 09:25:11
Share links
Summary: Learn how to run test cases, record step-level results and details, attach supporting evidence, review execution history, and report bugs from failed test results or directly from the Test Case list.

Catalog

Testers’ primary responsibilities include writing test cases and executing tests.

In Test > Test Case, use the actions in the Actions column to run test cases, review execution results, and report bugs when issues are found.

I. Execute a Test Case

Click Run in the Actions column to execute a test case.

Sanplex Test Case list with the Run action highlighted in the Actions column for each test case.

The Run Case dialog displays the test case prerequisite, steps, expectations, and fields for recording the execution result and details.

For each step, select the appropriate result. Sanplex supports the following execution results:

  • Skip
  • Pass
  • Fail
  • Blocked

The default result is Pass.

You can also enter additional information in Details for each step.

Run Case dialog showing the test case prerequisite, steps, expectations, Result fields, Details fields, Save and Next buttons, and previous execution results.

To attach supporting files to a test step, click the attachment icon beside the Details field. In the Upload dialog, select or drag a file into the upload area, and then click Save.

Upload dialog opened from a Run Case step, showing the Select File upload area and Save button.

After completing the execution, click Save to record the results. You can use Next to continue to the next test case.

II. Report a Bug from a Test Case

When a test step fails, the execution result is recorded in the test case history. The result details show the executed steps, expectations, case version, and result.

For failed results, select the relevant failed step and click Report Bug to create a bug from the test result.

Test case execution results showing one failed step and a Report Bug button for creating a bug from the failed result.

Sanplex opens the Report Bug page and carries relevant information from the test case into the bug, including the test case context and reproduction information.

Complete the required bug fields and click Save.

Report Bug page populated from a test case, showing Product, Project, Execution, Name, Type, Severity, Priority, and Repro Steps.

After the bug is created, its Basic Info panel displays the originating test case in the Source Test Case field.

Bug detail page showing the Source Test Case field linked to the test case that generated the bug.

You can also use the Report Bug action directly from the Test Case list.

Sanplex Test Case list with the Report Bug action highlighted in the Actions column.

III. View Execution Results

In the Test Case list, click Results in the Actions column to review the execution history for a test case.

Sanplex Test Case list with the Results action highlighted in the Actions column.

The execution history records previous runs and their results, including step-level expectations, results, details, attachments, and case versions.

Write a Comment
Comment will be posted after it is reviewed.