Operations 5 min read

Introduction to RunnerGo Automated Testing: Plan Management and Report Management

This article introduces RunnerGo's automated testing features, detailing plan management, report management, scene import, task configuration, and how to view multi‑dimensional test results, while providing links to the project's GitHub and Gitee repositories for further exploration.

php中文网 Courses
php中文网 Courses
php中文网 Courses
Introduction to RunnerGo Automated Testing: Plan Management and Report Management

The previous article introduced performance test report management and preset configurations; this article focuses on automated testing.

Automated testing is divided into two modules: plan management and report management.

Plan Management: This module includes functions such as plan list, search reports, and creating new plans.

Creating a New Plan: Click the "New Plan" button to open a dialog where you can enter the plan name and an optional description.

After entering a plan, there are three main sections: the plan task area, the scene area, and the scene body area.

Scene Area: You can search, create directories, import scenes, or create new scenes.

When importing a scene, a sidebar appears on the right where you can select the desired scene to import.

After importing the required scenes, you can open the test case set module of a scene to view and debug each test case.

Once you have debugged the test cases according to your needs, you can upload CSV or TXT parameter files in the scene settings; the data in these files correspond to the test cases in order, with both test cases and parameter rows processed sequentially.

Each plan can import multiple scenes, each with its own test case set. In automation, the scenes themselves do not run; only their test case sets are executed.

Task Configuration: Tasks can be set as regular tasks or scheduled tasks.

You can choose to run all scenes simultaneously or execute them sequentially.

After clicking "Run", you can view the test reports in the report list.

Within a report, you can view test results from multiple dimensions; each scene has its own test case results, and each test case includes interface execution status such as success, failure, or not tested.

This brief introduction covers the main functional modules of RunnerGo and how to use them; interested readers are encouraged to try it themselves.

GitHub repository: https://github.com/Runner-Go-Team/RunnerGo

Gitee repository: https://gitee.com/Runner-Go-Team/RunnerGo

If you appreciate the open‑source project, feel free to star it for support.

RunnerGo has been open‑source for two months, earning the GVP‑Gitee most valuable open‑source project award, and the team commits to continuous improvement to provide better testing solutions for testers.

automated testingDevOpssoftware testingtest managementRunnerGo
php中文网 Courses
Written by

php中文网 Courses

php中文网's platform for the latest courses and technical articles, helping PHP learners advance quickly.

0 followers
Reader feedback

How this landed with the community

login Sign in to like

Rate this article

Was this worth your time?

Sign in to rate
Discussion

0 Comments

Thoughtful readers leave field notes, pushback, and hard-won operational detail here.