Scene Management in RunnerGo: Overview and Usage

The previous article explained how to use interface management and added some supplements; in interface management, interfaces are only referenced in other modules, so changes in interface management do not affect interfaces elsewhere.

This article mainly explains the scene management part.

First, enter the scene management module. The left side is the directory/group area where you can search groups and scenes, as well as create new directories, groups, and scenes.

The right side is the scene main area. After creating a new scene, the left side shows the corresponding scene name, and the right side displays the matching content; clicking a scene on the left switches the main area. The scene also shows a collapsed test‑case set directory.

Scene main area: includes scene name, scene settings, save, scene debugging (start debugging), create new interface, add controller, import interface.

Create or import one or more interfaces (controllers) to form a business scenario, as shown below.

By connecting with lines, you build a scene and set execution order (interfaces or controllers on the same level execute simultaneously). For example, the first order is the login random‑value interface 1; the second order consists of two conditional controllers; the third order includes login interface 1 and test interface 1; the fourth order includes news list 1 and comment‑news interface; the fifth order is the favorite‑news interface. If an IF controller fails, the interfaces beneath it will not execute.

At the same time, you can use the association extraction function described earlier to extract response data from an interface and reuse it in other interfaces using the variable syntax {{variable_name}}.

Scene settings: support uploading parameterized files (txt, csv) and defining custom variables for use within the scene.

Start debugging (debug scene): after finishing, you can view results under the interface node to see execution details; the right side will pop up the request and response information, and you can debug the interface in the right‑hand panel.

Debugging a single interface runs only that interface, not the whole scene; therefore, variables extracted by association will be invalid in this mode.

Scene settings only apply to the current scene.

Test case set: after expanding the test‑case set collapse bar, you can create new test cases, copy, delete, and debug them.

Create new test case: it copies the scene as a template to generate a test case, which you can then modify according to your design.

The test case uses variables or parameterized files defined in scene settings, reading values from the parameterized file according to the test case order.

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

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

If you appreciate the RunnerGo open‑source project, you can give it a star to support it.

RunnerGo has been open source for two months, received the GVP‑Gitee most valuable open‑source project award, and will continue to improve and provide better testing software solutions for testers.