1. Interface test
Project address: Gitee / Github
The interface test module is the core of the entire Lim platform. The left side is the interface module tree, and the top right side is the use case operation function area, which lists the interface use case information:
Article Directory
2. Maintenance interface use cases
Detailed explanation of each step type
2. Maintenance interface use cases
Click the "New" button in the upper right corner or the modify button in the list to open the use case maintenance pop-up window, where the user can maintain the steps of the use case, edit, sort, copy, delete, debug and execute the use case:
Detailed explanation of each step type
Lim supports many types of steps, including interfaces, SQL, loop controllers, custom functions, global variables, global request headers, etc., to meet various business needs.
The following will give a detailed introduction to their usage in turn.
1) Execution steps
1. Interface steps
Click "Add Step-Execution Step-Interface" to open the pop-up window for creating an interface step, where the user can complete the interface request information:
Lim will match the historically entered interface records according to the input:
Clicking them will backfill back the interface information and request parameters entered last time:
In addition, when filling in the parameter value in list mode, its data type will be automatically set:
Sometimes, when the field values we need need to do some calculations or require code processing, we can use evalmethods to meet such needs, examples are as follows:
As you can see, we have just used variables. For the specific usage of variables, please refer to the rules of variable usage .
In actual situations, it is often not enough to support a single line of code. Lim also supports the writing of pure code mode:
In filling in the expected results and variable output, we don’t need to manually copy the parameters and fill them in one by one. Instead, double-click the field in the response result and it will be filled in the parameter list by default:
2. SQL statement
Click "Add Step-Execute Step-SQL Statement" to open the pop-up window for creating SQL steps. The query SQL also supports the use of variables. If you need to adapt to databases in multiple environments, remember to ensure that each environment is filled in the database connection information. Consistency of connection names:
3. Loop Controller
Click "Add Step-Execute Step-Loop Controller" to open the pop-up window for creating a loop controller step, where the user can configure the steps that need to be executed cyclically:
4. Citing test cases
Click "Add Step-Execution Step-Reference Test Case" to open the pop-up window for creating reference test case steps, where users can refer to other interface use cases, such as public use cases such as basic data preparation. It should be noted that: because the use case is Reference relationship, so modifying the following steps will directly modify the original use case, please modify carefully!
2) Configure components
1. Global variables
Click "Add Step-Configuration Component-Global Variable" to open the pop-up window for creating a global variable step, which is generally used to configure public or basic variables and supports multi-environment configuration:
2. Global request header
Click "Add Step-Configuration Component-Global Request Header" to open the pop-up window for creating a global request header step, which is generally used to configure public or basic request headers:
3. Global request address
Click "Add Step-Configuration Component-Global Request Address" to open the pop-up window for creating a global request address step, which is generally used to configure public or basic request addresses, so that you don't need to write each interface once, which is more recommended here Select the project configuration method to set the request address, which is easier to maintain and can adapt to multiple environments:
