Method, system, device and storage medium for building test scenario data

Abstract

The application relates to a method, system, device and storage medium for building test scene data, comprising the following steps: obtaining a first request instruction of a related tester, accepting the request instruction, and obtaining a type of a built test scene; calling corresponding test scene data by using the type of the built test scene, performing parameter output configuration, obtaining the corresponding test scene data and the data of the parameter output configuration, and returning to a controller; the controller processes the test scene data and the data of the parameter output configuration into a data structure in a specified form, and returns to a front-end page; the front-end page accepts the test scene data of the data structure, renders the data to a page, and completes building of the test scene. The application helps to solve the problems of low building efficiency of the test scene and inability to uniformly maintain test data scenes of various projects.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of software testing, in particular to a method, system, device and storage medium for building test scene data. BACKGROUND

[0002] In current test work, there are many automatic generation tools for project test data. These tools use different frameworks to implement and are difficult to manage uniformly, which also brings barriers to cross-system test data automatic generation. In addition, the implementation of test data manufacturing requires corresponding code development and programming capabilities, which brings challenges to the promotion of all system test data automation.

[0003] The existing technical solution is to use various framework-implemented tool systems to manufacture expected test data. If the business code changes, new business scenarios are added, personnel changes, etc., tool developers need to implement corresponding functions through code or guide new personnel to use the tool. This method is inefficient for building test scenes and is not easy to maintain uniformly.

[0004] That is, the existing test tools are inefficient for building test scenes, cannot uniformly maintain the test data scenes of various projects, and result in high maintenance costs. SUMMARY

[0005] To at least partially overcome the problems of the existing test tools in the related art, which are inefficient for building test scenes, cannot uniformly maintain the test data scenes of various projects, and result in high maintenance costs, the present application provides a method, system, device and storage medium for building test scene data.

[0006] The solution of the present application is as follows:

[0007] In one aspect, the present application provides a method for building test scene data, which comprises:

[0008] obtaining a first request instruction of a related test personnel;

[0009] accepting the request instruction to obtain the type of building test scene;

[0010] using the type of building test scene to call corresponding test scene data, perform parameter output configuration, obtain the corresponding test scene data and the data of the parameter output configuration, and return to a controller;

[0011] the controller processes the test scene data and the data of the parameter output configuration into a data structure of a specified form, and returns to a front-end page;

[0012] the front-end page accepts the test scene data of the data structure, renders the data to a page, and completes the building of the test scene.

[0013] Further, the receiving the request instruction obtains a type of the test scene to be built, including:

[0014] The receiving the request instruction calls a backend controller through Axios;

[0015] The backend controller is used to perform data analysis on the function and related parameter information in the first request instruction;

[0016] The type of the test scene to be built is obtained by using the result of the data analysis.

[0017] Further, the type of the test scene to be built is used to call corresponding test scene data, perform out-parameter configuration, obtain the corresponding test scene data and the data of the out-parameter configuration, and return to a controller, including:

[0018] The type of the test scene to be built is used to call corresponding test scene data and input a second request instruction;

[0019] The second request instruction is used to perform out-parameter configuration, and the corresponding test scene data and the data of the out-parameter configuration are returned to the controller, wherein the second request instruction includes a request parameter body and a configuration input parameter variable.

[0020] Further, the second request instruction is used to perform out-parameter configuration, including: if the request parameter body contains a function, entering a function management to wait for use;

[0021] Otherwise, it is determined whether the input parameter variable needs to be configured, if the input parameter variable is configured, the disabled, read-only and hidden element attributes can be selectively configured;

[0022] If the input parameter variable does not need to be configured, no input parameter is displayed.

[0023] Further, the test scene data includes HTTP test scene data, DUBBO test scene data, MQ test scene data and ES test scene data.

[0024] In a second aspect, the application provides a system for building test scene data, including:

[0025] An acquisition module is configured to acquire a first request instruction of a related test personnel;

[0026] A scene building module is configured to receive the request instruction and obtain a type of a test scene to be built;

[0027] The type of the test scene to be built is used to call corresponding test scene data, perform out-parameter configuration, obtain the corresponding test scene data and the data of the out-parameter configuration, and return to a controller.

[0028] a parsing module, configured to process the test scenario data and the data of the out-parameter configuration into a data structure in a specified form by the controller, and return a front-end page;

[0029] a rendering module, configured to render the test scenario data of the data structure to a page by the front-end page, and complete the building of the test scenario.

[0030] In a third aspect, the present application provides a device for building test scenario data, and the device comprises:

[0031] a memory, in which an executable program is stored;

[0032] a processor, configured to execute the executable program in the memory, so as to implement the steps of any one of the methods.

[0033] In a fourth aspect, the present application provides a computer readable storage medium, which stores computer instructions, and the computer instructions are used to make a computer execute the steps of any one of the methods.

[0034] The technical solution provided by the present application can have the following beneficial effects:

[0035] The present application obtains the first request instruction of the relevant test personnel, accepts the request instruction, and obtains the type of the built test scenario. The type of the built test scenario is used to call the corresponding test scenario data, perform out-parameter configuration, obtain the corresponding test scenario data and the data of the out-parameter configuration, and return to the controller. The controller processes the test scenario data and the data of the out-parameter configuration into a data structure in a specified form, and returns a front-end page. The front-end page accepts the test scenario data of the data structure, renders the data to a page, and completes the building of the test scenario. The present application helps to solve the problems of low efficiency of building test scenarios and inability to uniformly maintain the test data scenarios of various projects.

[0036] It should be understood that the foregoing general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. BRIEF DESCRIPTION OF DRAWINGS

[0037] The accompanying drawings incorporated in the specification and forming a part of the specification illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

[0038] Figure 1 is a method flow diagram for building test scenario data provided by an embodiment of the present application;

[0039] Figure 2is a system block diagram provided by another embodiment of the present application for building test scenario data;

[0040] Figure 3 is a device block diagram provided by another embodiment of the present application for building test scenario data;

[0041] Figure 4 is a method flow diagram provided by an embodiment of the present application for building test scenario data. DETAILED DESCRIPTION

[0042] The exemplary embodiments will be described in detail herein with reference to the attached drawings. In the following description, the same numbers refer to the same or similar elements throughout the drawings. The embodiments described in the following exemplary embodiments are not meant to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the appended claims.

[0043] Please refer to Figure 1 , Figure 1 is a method flow diagram provided by an embodiment of the present application for building test scenario data, the method comprising:

[0044] S1. obtaining a first request instruction of a relevant tester;

[0045] S2. accepting the request instruction to obtain a type of test scenario building;

[0046] S3. using the type of test scenario building to call corresponding test scenario data, performing parameter output configuration, obtaining the corresponding test scenario data and the parameter output configuration data and returning to a controller;

[0047] S4. the controller processes the test scenario data and the parameter output configuration data into a data structure of a specified form, and returns a front-end page;

[0048] S5. the front-end page accepts the test scenario data of the data structure, renders the data to a page, and completes the building of the test scenario.

[0049] In one embodiment, as described in step S2, the acceptance of the request instruction to obtain the type of test scenario building comprises:

[0050] accepting the request instruction to call a backend controller through Axios;

[0051] using the backend controller to perform data analysis on the functions and related parameter information in the first request instruction;

[0052] The type of the test scene is built by using the result of the data analysis.

[0053] In one embodiment, the type of the test scene is built, and corresponding test scene data is called, and the output parameter configuration is performed, and the data of the corresponding test scene data and the output parameter configuration are returned to the controller, as described in step S3.

[0054] The type of the test scene is built, and corresponding test scene data is called, and the second request instruction is recorded.

[0055] The output parameter configuration is performed by using the second request instruction, and the data of the corresponding test scene data and the output parameter configuration are returned to the controller, wherein the second request instruction includes a request parameter body and a configuration input parameter variable.

[0056] Specifically, the output parameter configuration is performed by using the second request instruction, including: if the request parameter body contains a function, entering the function management to wait for use.

[0057] Otherwise, it is determined whether the input parameter variable needs to be configured, and if the input parameter variable is configured, the disabled, read-only, and hidden element attributes can be selectively configured.

[0058] If the input parameter variable does not need to be configured, no input parameter display is performed.

[0059] In specific implementation, after the system is deployed, as shown in Figure 4 the relevant test personnel can access the system page through the browser, operate on the page, click the corresponding function button, and call the backend controller through Axios.

[0060] It should be noted that the controller calls the specific code implementation service, and the expected function is processed in the service interface. First, the function and the parameterized field in the request parameter are processed and replaced with the actual value after parameterization, and then various types are processed respectively, for example: the data in the database is obtained through MySql and MyBaitis, the data in the ElasticSearch cluster is obtained through ES and ElasticSearch service, the message sending and message query functions are implemented through the RocketMQ client interface, the interface of other systems is called to update or obtain data through the Dubbo and Zookeeper generalization call, the interface of other systems is called to update or obtain data through the Http client interface, and so on.

[0061] Specifically, after the data transmitted from the front end is processed in the interface service, the processing result including the request parameter of the interface, the return result, the input parameterization, and the out-parameter path corresponding value is returned to the controller.

[0062] Specifically, the controller converts the result data into a front-end easy-to-handle data structure and returns it to the front end. The front-end page accepts the data returned by the back end and re-renders the data to the page to display to the user for viewing and use.

[0063] In the embodiments of the present application, a corresponding tester or other user constructs a data sheet and builds an instance of a test scenario, including:

[0064] 1. The user accesses the system using a browser, enters an account and a password on a login page, and logs in successfully into the system if the account and password are correct, and the system defaults to display a data management page; otherwise, the user is prompted that the username or password is incorrect.

[0065] 2. After clicking a menu data management, the data management background page is entered, and all data sheets created by users are displayed on the page, and the data sheets can be queried according to conditions; the current login user can perform permission management on the user's own data sheet, and other users assigned with permissions can edit the data sheet.

[0066] 3. On the data management background page, a new button or an edit button is clicked to enter a data sheet new creation or editing page, wherein the data sheet information is automatically obtained when the editing page is entered, basic information is input, and a specific data service is selected by clicking an execution mode drop-down box, including HTTP, DUBBO, MQ, ES and the like. If HTTP is selected, the parameter information required by HTTP needs to be input; if DUBBO is selected, the parameter information required by DUBBO needs to be input; if MQ is selected, the parameter information required by MQ needs to be input; and if ES is selected, the parameter information required by ES needs to be input.

[0067] 4. The request parameter body and the configuration out-parameter variable need to be continuously input, wherein if the request parameter body contains a function, the parameter enters the function management for use; otherwise, if the input parameter parameterization is configured, the input parameter variable needs to be configured, and if the input parameter parameterization is not configured, the input parameter is not configured and is not displayed on the data management page.

[0068] 5. The input parameter (which can be configured or multiple parameters can be configured by clicking the plus sign) is configured, the type is input, the display name and the parameterized variable name associated with the request parameter are input, and the default value is input.

[0069] The type is input, the display name and the parameterized variable name associated with the request parameter are input, and the default value is input, and all data to be displayed in the drop-down box can be input in the attribute.

[0070] 6. Configure the input parameter attribute. If the attribute is not configured, the current input parameter can normally display a normal text box on the data management page. If the input parameter is configured, the disabled, read-only, hidden, and other element attributes can be selectively configured. If the hidden attribute is not selected, the input parameter text box is normally displayed on the data management page. If the hidden attribute is selected, the input parameter text box is not displayed on the data management page.

[0071] 7. Configure the output parameter (a plurality of output parameters can be configured by clicking the plus sign), input the display name and associated variable, and the output parameter path.

[0072] 8. Configure the output parameter attribute. If the attribute is not configured, the current output parameter can normally display a normal text box on the data management page. If the output parameter is configured, the disabled, read-only, hidden, and other element attributes can be selectively configured. If the hidden attribute is not selected, the output parameter text box is normally displayed on the data management page. If the hidden attribute is selected, the output parameter text box is not displayed on the data management page.

[0073] 9. Click the submit button to create or save the data sheet successfully, and the data sheet data enters the data management page for display.

[0074] 10. Select a displayed data sheet on the data management page and input the parameters.

[0075] 11. After clicking the submit button, the request data is sent to the system backend service.

[0076] 12. The system backend service returns the processing result to the data management page, and the page is re-rendered to display the returned data. Thus, the user obtains the desired data.

[0077] In one embodiment, the present application also provides an instance of a corresponding test personnel or other user constructing a scenario data sheet and building a test scenario, including:

[0078] 1. The user accesses the system using a browser, logs in after inputting the account and password on the login page, and enters the system. The default display is the data management page.

[0079] 2. Click the menu scenario management to enter the scenario management background page. The page displays all scenario data sheets created by users, and the scenario data sheets can be queried according to conditions. The current logged-in user can perform permission management on his own scenario data sheet, and the user assigned with the permission can edit the scenario data sheet.

[0080] 3. Click the new or edit button on the scenario management background page to enter the scenario data sheet new or edit page. After inputting the basic information, the sub-data sheet selection page can be popped up by clicking the add sub-data sheet.

[0081] 4. In the sub-data single selection page, all available single data singles are displayed by default, or specific single data singles can be queried based on conditions. According to the required scene, select specific data singles as the sub-data singles of the scene data single. After clicking confirm, the selected data singles are associated with the scene data single;

[0082] 5. In the scene data single new or edit page, the execution order of several sub-data singles can be sorted and modified. The request parameter body and the configuration of input and output parameters of each sub-data single are checked in turn. If the request parameter body needs to be modified, it can be modified. If the parameter contains a function, the parameter enters the function management for use. Otherwise, if the input parameterization is configured, the input parameter variable needs to be configured. If the input parameterization is not configured, it does not need to be configured and the input parameter is not displayed in the data management page.

[0083] 6. Configure input parameters (can not configure or click plus to configure multiple),

[0084] 1) If the input type is a text box, enter the display name and the parameterized variable name associated with the request parameter, as well as the default value. Continue to determine whether the input parameter needs to use the return result value of the previous sub-data single (determined according to the order) as the input parameter. If so, configure the parameterized variable name as the output parameter variable name of the previous sub-data single (determined according to the order). If the input type is a drop-down box, enter the display name and the parameterized variable name associated with the request parameter, as well as the default value. In addition, all data to be displayed in the drop-down box can be entered in the attribute. Continue to determine whether the input parameter needs to use the return result value of the previous sub-data single (determined according to the order) as the input parameter. If so, configure the parameterized variable name as the output parameter variable name of the previous sub-data single (determined according to the order).

[0085] 2) If the input type is a drop-down box, enter the display name and the parameterized variable name associated with the request parameter, as well as the default value. In addition, all data to be displayed in the drop-down box can be entered in the attribute. Continue to determine whether the input parameter needs to use the return result value of the previous sub-data single (determined according to the order) as the input parameter. If so, configure the parameterized variable name as the output parameter variable name of the previous sub-data single (determined according to the order).

[0086] 7. Configure input parameter attributes. If no attribute is configured, the current input parameter can be normally displayed as a normal text box in the data management page. If the input parameter is configured with attributes, optional attributes such as disabled, read-only, hidden, etc. can be configured. If the hidden attribute is not selected, the input parameter text box is normally displayed in the data management page. If the hidden attribute is selected, the input parameter text box is not displayed in the data management page.

[0087] 8. Configure output parameters (click plus to configure multiple), enter the display name, associated variable, and output parameter path.

[0088] 9. Configure the out-parameter attribute. If the attribute is not configured, the current out-parameter can normally display a normal text box on the data management page. If the out-parameter attribute is configured, the disabled, read-only, hidden, and other element attributes can be selectively configured. If the hidden attribute is not selected for configuration, the out-parameter text box is normally displayed on the data management page. If the hidden attribute is selected for configuration, the out-parameter text box is not displayed on the data management page;

[0089] 10. Click the submit button to create or save the scene data sheet successfully, and the scene data sheet enters the data management page for display;

[0090] 11. Select a displayed data sheet on the data management page and input parameters;

[0091] 12. After clicking the submit button, the request data is sent to the system backend service;

[0092] 13. The system backend service returns the processing result to the data management page, the page is re-rendered to display the returned data, and thus the user obtains the expected data.

[0093] In one embodiment, by performing the steps in the above method, the present application helps to quickly build a test data automatic scene and improves the test data manufacturing efficiency;

[0094] Various test tool systems are uniformly managed and maintained in one system, reducing labor costs and improving work efficiency.

[0095] Embodiment Two

[0096] Please refer to Figure 2 , Figure 2 is a system composition schematic diagram provided by another embodiment of the present application for building a test scene data, and the system comprises:

[0097] The acquisition module 101 is configured to acquire a first request instruction of a relevant test personnel;

[0098] The scene building module 102 is configured to accept the request instruction and obtain a type of building a test scene;

[0099] The type of building a test scene is used to call corresponding test scene data, configure an out-parameter, obtain data of the corresponding test scene and the out-parameter configuration, and return to the controller;

[0100] The analysis module 103 is configured to process the test scene data and the data of the out-parameter configuration into a data structure of a specified form by the controller, and return to a front-end page;

[0101] The rendering module 104 is configured to accept the test scene data of the data structure by the front-end page, render the data to the page, and complete the construction of the test scene.

[0102] Embodiment three

[0103] Please refer to Figure 3 , Figure 3 is a schematic diagram of a device for constructing test scene data according to another embodiment of the present application, and the device comprises:

[0104] The memory 31 has a stored executable program.

[0105] The processor 32 is configured to execute the executable program in the memory 31 to implement the steps of any one of the above methods.

[0106] In addition, the present application provides a computer readable storage medium, which stores computer instructions for making a computer execute the steps of any one of the above methods. The storage medium can be a magnetic disk, an optical disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a Flash Memory, a Hard Disk Drive (HDD) or a Solid-State Drive (SSD), etc. The storage medium can also include a combination of the above types of memories.

[0107] It can be understood that the same or similar parts in the above embodiments can be mutually referred to, and the content not described in detail in some embodiments can be referred to the same or similar content in other embodiments.

[0108] It should be noted that, in the description of the present application, the terms "first", "second", etc. are only used for the purpose of description, and cannot be understood as indicating or implying relative importance. In addition, in the description of the present application, unless otherwise specified, the meaning of "a plurality of" is at least two.

[0109] Any process or method descriptions in flow charts or otherwise described herein represent embodiments of examples that can be implemented as executable instructions stored in a computer readable storage medium (storage) or in memory of a machine that performs processes described by the instructions. Therefore, the present application's preferred embodiments can be embodied in a machine that has a processor that executes instructions, and other embodiments of the present application can be embodied in software modules, segments or portions of code that comprise the executable instructions for implementing the processes described by the instructions. Whether these software modules are stored in a computer readable storage medium or memory, the processes they implement can be implemented in the domain of the present application's preferred embodiments, and the scope of the present application's preferred embodiments includes other implementations that can not be in the order shown or discussed, including according to the functions involved in the implementation of the functions in a substantially simultaneous manner or in a reverse order, which should be understood by those skilled in the art to which the embodiments of the present application belong.

[0110] It should be understood that each of the elements of the present application can be implemented in hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, and in another embodiment, any of the following technologies known in the art or their combinations can be used: discrete logic circuitry having logic gates for implementing logic functions on data signals, application specific integrated circuits having appropriate combinational logic gates, programmable gate arrays (PGA), field programmable gate arrays (FPGA), etc.

[0111] Those skilled in the art of the present technology can understand that all or part of the steps carried out by the above-mentioned embodiment methods can be completed by programs instructing related hardware, and the programs can be stored in a computer readable storage medium, and when executed, include one or a combination of steps of the method embodiments.

[0112] In addition, each functional unit in each embodiment of the present application can be integrated into one processing module, or each unit can be physically present separately, or two or more units can be integrated into one module. The above-mentioned integrated module can be realized in the form of hardware or in the form of a software function module. The integrated module, if realized in the form of a software function module and sold or used as an independent product, can also be stored in a computer readable storage medium.

[0113] The storage medium mentioned above can be a read-only memory, a magnetic disk or an optical disk, etc.

[0114] In the description of the present specification, the description of the terms "one embodiment", "some embodiments", "an example", "a specific example", or "some examples" means that the specific features, structures, materials or characteristics described in conjunction with the embodiment or example are included in at least one embodiment or example of the present application. In the present specification, the illustrative description of the above terms does not necessarily mean the same embodiment or example. Moreover, the specific features, structures, materials or characteristics described can be combined in any one or more embodiments or examples in a suitable manner.

[0115] Although the embodiments of the present application have been shown and described above, it should be understood that the above embodiments are exemplary and cannot be understood as limiting the present application, and those skilled in the art can make changes, modifications, replacements and variations to the above embodiments within the scope of the present application.

Claims

1. A method for building test scenario data, characterized in that, The method includes: Obtain the first request instruction from the relevant testers; Accept the request instruction to obtain the type of test scenario to be built; Using the type of test scenario to build, call the corresponding test scenario data, configure the output parameters, obtain the corresponding test scenario data and the data configured for the output parameters, and send them back to the controller. The controller processes the test scenario data and the output parameter configuration data into a specified data structure and returns it to the front-end page; the specified data structure is a data structure that is easy for the front-end to process. The front-end page receives the test scenario data of the data structure, renders the data onto the page, and completes the construction of the test scenario; The step of utilizing the type of test scenario to build, calling the corresponding test scenario data, configuring output parameters, obtaining the corresponding test scenario data and the configured output parameters data, and sending them back to the controller includes: Using the type of test scenario to build, call the corresponding test scenario data and enter the second request command; The output parameters are configured using the second request instruction, and the corresponding test scenario data and the output parameter configuration data are sent back to the controller. The second request instruction includes: a request parameter body and configuration input parameter variables. Configuring output parameters using the second request instruction includes: if the request parameter body contains a function, then entering the function management and waiting for use; Otherwise, continue to determine whether the input parameter variable needs to be configured. If the input parameter variable is configured, the element attributes of disabling, reading-only, and hiding can be selectively configured. If no input parameters are required, then display the result without input parameters.

2. The method according to claim 1, characterized in that, The acceptance of the request instruction to obtain the type of test scenario to be built includes: Accept the request instruction and invoke the backend controller via Axios; The backend controller is used to parse the function and related parameter information in the first request instruction; Using the results of the data analysis, the type of test scenario to be built is determined.

3. The method according to claim 1, characterized in that, The test scenario data includes: HTTP test scenario data, DUBBO test scenario data, MQ test scenario data, and ES test scenario data.

4. A system for building test scenario data, applied to the method for building test scenario data according to any one of claims 1-3, characterized in that, The system includes: The acquisition module is used to acquire the first request instruction from the relevant testers; The scenario building module is used to receive the request instruction and obtain the type of test scenario to be built. Using the type of test scenario to be built, call the corresponding test scenario data, configure the output parameters, obtain the corresponding test scenario data and the data configured for the output parameters, and send them back to the controller. The step of utilizing the type of test scenario to build, calling the corresponding test scenario data, configuring output parameters, obtaining the corresponding test scenario data and the configured output parameters data, and sending them back to the controller includes: Using the type of test scenario to build, call the corresponding test scenario data and enter the second request command; The output parameters are configured using the second request instruction, and the corresponding test scenario data and the output parameter configuration data are sent back to the controller. The second request instruction includes: a request parameter body and configuration input parameter variables. Configuring output parameters using the second request instruction includes: if the request parameter body contains a function, then entering the function management and waiting for use; Otherwise, continue to determine whether the input parameter variable needs to be configured. If the input parameter variable is configured, the element attributes of disabling, reading-only, and hiding can be selectively configured. If no input parameters are required, then display the result without input parameters; The parsing module is used by the controller to process the test scenario data and the output parameter configuration data into a specified data structure and return it to the front-end page; the specified data structure is a data structure that is easy for the front-end to process; the rendering module is used by the front-end page to receive the test scenario data of the specified data structure, render the data onto the page, and complete the construction of the test scenario.

5. A device for building test scenario data, characterized in that, The device includes: Memory, on which executable programs are stored; A processor for executing the executable program in the memory to implement the steps of the method according to any one of claims 1-3.

6. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions for causing a computer to perform the steps of the method according to any one of claims 1-3.

Images