CN117520145A - Automatic mixed scene test method for low-code assembled interface - Google Patents
Automatic mixed scene test method for low-code assembled interface Download PDFInfo
- Publication number
- CN117520145A CN117520145A CN202311271500.4A CN202311271500A CN117520145A CN 117520145 A CN117520145 A CN 117520145A CN 202311271500 A CN202311271500 A CN 202311271500A CN 117520145 A CN117520145 A CN 117520145A
- Authority
- CN
- China
- Prior art keywords
- scene
- test
- interface
- data
- low
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000010998 test method Methods 0.000 title claims abstract description 8
- 238000012360 testing method Methods 0.000 claims abstract description 123
- 238000013515 script Methods 0.000 claims abstract description 14
- 238000013461 design Methods 0.000 claims abstract description 7
- 230000004044 response Effects 0.000 claims description 19
- 238000000034 method Methods 0.000 claims description 17
- 238000000605 extraction Methods 0.000 claims description 6
- 230000008569 process Effects 0.000 claims description 6
- 238000005259 measurement Methods 0.000 claims description 4
- 238000012545 processing Methods 0.000 claims description 4
- 230000003068 static effect Effects 0.000 claims description 4
- 230000005540 biological transmission Effects 0.000 claims description 3
- 238000003780 insertion Methods 0.000 claims description 3
- 230000037431 insertion Effects 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000004519 manufacturing process Methods 0.000 description 3
- 238000012800 visualization Methods 0.000 description 2
- 241000677635 Tuxedo Species 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 238000011990 functional testing Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides a low-code assembled interface automatic mixed scene test method suitable for the insurance industry, which comprises the following steps: creating an entry for three interface test scenarios, the three interface test scenarios comprising: a conventional test scene, a rule test scene and a key number test scene; assembling one or more operations of the low codes to form a mixed test scene; and completing insurance service testing of different scenes through different data configuration items in the same set of scene scripts. The invention realizes the mixed scene application in the interface test in a low-code assembled interface script writing mode. The invention realizes the design of 'spindle type' business mode in the configuration form of the same set of script and different data sources, combines the application of scene scripts and meets the test of multiple scenes of insurance business.
Description
Technical Field
The invention belongs to the technical field of software, and particularly relates to a low-code assembled interface automatic mixed scene test method.
Background
In the software development process, an interface automation test is a necessary step for testing whether an interface of an application program can work as expected. Conventional manual testing methods typically require a significant amount of time and labor, and it is difficult to ensure the accuracy and integrity of the test. Therefore, a method is needed to automatically perform interface test, so as to improve test efficiency and accuracy by means of integrated test, accurate test and the like. The existing interface testing tool has the following defects:
first, currently mainstream interface test tools do not support assembled interface hybrid scenario testing. The operation of the interface testing tools popular in the market is aimed at one or several single matters of the interface testing process, such as interface management, single interface testing, simple link testing and other functions. Complex scenes and mixed scenes in the functional test cannot be completed, and comprehensive interface test planning and test execution cannot be performed.
Second, existing interface test tools do not have insurance industry attributes. Special tests in the insurance industry are commonly found in special tests such as premium measurement and calculation, insurance rule tests, quick insurance application/quick claim settlement (number of manufacturing) and the like, and the functions of interface tools in the market at present cannot meet the special tests in the insurance industry, so that the special tests in the insurance industry are low in efficiency and difficult to guarantee in accuracy for using the existing tools.
Disclosure of Invention
In order to solve the problems, the invention provides a low-code assembled interface automatic mixed scene test method suitable for the insurance industry.
In order to achieve the above purpose, the technical scheme of the invention is as follows:
a low-code assembly type interface automatic mixed scene test method comprises the following steps:
step 1, creating an entry of three interface test scenes, wherein the three interface test scenes comprise: a conventional test scene, a rule test scene and a key number test scene;
step 2, assembling one or more operations of the low codes to form a mixed test scene;
and step 3, completing insurance service testing of different scenes through different data configuration items in the same scene script. Further, the step 1 specifically includes the following sub-steps:
a) Creating a conventional test scene entry for premium testing in the insurance industry;
b) Creating a rule test scene entry for verifying the correctness of the business rule of the insurance company;
c) Creating a key number test scene entry for special testing in significant number requirements;
further, the assembling operation in step 2 includes one or more of the following operations:
a) Adding a protocol request, wherein at least one operation in the protocol request is realized by adopting a low-code mouse operation mode;
b) Adding an existing interface template/scene template of the platform, and rapidly completing the creation operation;
c) Adding a JDBC request;
d) A loop/if/while controller is added.
Further, the protocol request is an HTTP request, and comprises an interface request, an interface response, response assertion, variable extraction, a front operation and a rear operation; the extraction variable is extracted by a right mouse button JsonPath; the numerical value transmission between interfaces is carried out by taking the extracted variable as a parameter for context association, and the variables are associated through a mouse operation insertion form when the context of the interfaces is associated.
Further, when one field in the response message is quickly saved as a variable, the right key Copy JsonPath processing is performed on the field to be extracted in the text field of the response message, and the field is quickly saved as a variable and then provided for other messages to be used as a variable reference.
Further, the data configuration items are data sources, including "default static data" and "polling scenario data".
Further, the step 3 specifically includes the following three test scenarios:
d) Conventional test scenario: the method comprises the steps that polling scene data is used as a data source, interface association operation is carried out by taking a request message and a specific value of a table as variables, and a test scene of the premium and premium measurement of the insurance industry is met in a data-driven circulating table mode when a platform executes;
e) Rule test scenario: adding a specific column caseNumber, caseName, expectResult into a data source of the polling scene data, and enabling the platform to meet the test scene of rule test of the insurance industry through execution logic of a specific design and statistical processing logic after execution;
f) One key number test scenario: and performing enumeration configuration in the data source, and meeting the test scene of obtaining quick data output by executing according to the input of different fields.
Further, the execution logic of the specific design is as follows: when the data source of 'polling scene data' is used as data driving operation, the data of a specific column caseNumber, caseName, expectResult is loaded into the execution process, and when the operation is completed, the interface response result is compared with the expected result of the data source and is written into the test result according to the actual service requirement.
The beneficial effects of the invention are as follows:
the invention realizes the mixed scene application in the interface test in a low-code assembled interface script writing mode. The invention realizes the design of 'spindle type' business mode in the configuration form of the same set of script and different data sources, combines the application of scene scripts and meets the test of multiple scenes of insurance business.
Drawings
FIG. 1 is a schematic diagram of creating a test scenario entry.
FIG. 2 is a schematic diagram of the operation of the topology visualization editing tool.
Fig. 3 is a schematic diagram of a rapid variable save of a platform response message field.
Detailed Description
The technical scheme provided by the present invention will be described in detail with reference to the following specific examples, and it should be understood that the following specific examples are only for illustrating the present invention and are not intended to limit the scope of the present invention.
The invention is realized based on a Jettolinker platform, and is based on a JMET execution engine (open source), an interface script mode is written by self-developed page operation, and the assembled mixed scene meets the interface automation test of the insurance industry according to different test scenes of the insurance service.
The platform has complete automatic testing capability, and complete interface testing can be completed through low-code operation of the platform. The platform has the following functions:
a) Graphical interface: interface scene scripts are created through the visualization interface, including request parameters, response verification, assertions, and the like.
b) Template library: the platform provides interface templates and scene templates to help users quickly create test scenes.
c) Data configuration: the platform manages test data through default static data and scene polling data, and maintains the test data in modes of importing csv data, adding, deleting and the like.
d) Automated testing: the platform can test single interface joint debugging, can complete testing of mixed scenes according to different configurations of data sources, and generates a test log and a test report.
Specifically, the method for testing the low-code assembled interface automatic mixed scene provided by the invention has the overall flow shown in fig. 2, and comprises the following steps:
step one, as shown in fig. 1, creating an entry of three interface test scenes to cover special tests of insurance industry
a) Creating a conventional test scene entry: the method meets the business scenes of single-interface joint debugging test and multi-interface mixed scene test and is applied to the premium and premium test of the insurance industry;
b) Creating a rule test scene entry: the correctness of the business rules accumulated by the insurance company in operation for many years is verified. The method is mainly applied to upgrading of rule systems of insurance companies or special tests during business rule change.
c) Creating a key number test scene entry: one-key manufacturing is commonly found in significant manufacturing demands such as quick insurance applications, quick claims settlement, and the like in the insurance industry. The test scene assembled by the platform can meet the special test of different scenes such as quick insurance application/quick claim settlement and the like.
Based on each test scene entry (which may be implemented in the form of a button), it is possible to jump to the corresponding test function page,
subsequent mixed scene operations are supported in both of these pages.
And step two, combining the scene scripts into a mixed scene by one or more operations, and performing assembled mixed combination on the operations of the low codes to generate a complex mixed test scene. The operation object includes the following:
a) Adding HTTP requests, including interface requests, interface responses, response assertions, extracting variables, pre-operations, post-operations, etc.; the variable extraction operation mode is a mode of extracting variables by a right mouse button JsonPath; the numerical value transmission between interfaces is carried out by taking the extracted variable as a parameter for context association, and the variables are associated through a mouse operation insertion form when the context of the interfaces is associated. For example: as shown in fig. 3, when a certain field in the fast save response message is a variable, in the text field of the response message, the right key "copyjson path" process is performed on the field to be extracted, and the field can be fast saved as a variable and then provided for other messages to be used as a variable reference. Other operations can also use the low-code mouse operation mode, so that script development and maintenance efficiency is effectively improved, and data consistency and accuracy are effectively ensured. It should be noted that the foregoing HTTP request is merely an example, and other protocol requests are equally applicable to low-code mouse operation modes, such as TCP/DUBBO/WEBSERVICE/TUXEDO; the name of the right mouse button extraction variable is correspondingly changed when other protocols request, and is not JsonPath;
b) The interface template is added/the scene template is added, which is an existing interface/scene of the platform, and helps a user to quickly complete the creation operation;
c) Adding JDBC requests, including operations of multiple databases such as mysql, oracle and the like;
d) And a loop/if/while controller is added to meet the flow operation of the business demand branch.
Thirdly, completing insurance business testing of different scenes through different data configuration items in the same scene script
The data configuration item, i.e., the data source, is composed of "default static data" and "polling scene data". Wherein, both are the expression form of the form, the difference is that the content configuration of both is different when the scene is different;
a) Conventional test scenario: through scene polling data as a data source, the table form of the scene polling data has no specific format requirement, and rows or columns can be manually added to also check the imported csv file. Performing interface association operation by taking a specific value of the request message and a specific value of the form as a variable, and meeting test scenes of the premium and premium measurement of the insurance industry in the form of a data-driven circulation form when the platform executes;
b) Rule test scenario: different from a conventional test scene, a specific column caseNumber, caseName, expectResult is added in a data source of polling scene data, and when the platform executes, the test scene of rule test of the insurance industry is met through comparing execution logic of specific design with statistical processing logic after execution (the expected rule result and the actual rule of system response are processed); the execution logic of the platform is operated on the basis of an open source frame jmeter:
when the data source of 'polling scene data' is used as data driving operation, the data of a specific column caseNumber, caseName, expectResult is loaded into the execution process, and when the operation is completed, the interface response result is compared with the expected result of the data source and is written into the test result according to the actual service requirement, thereby achieving the purpose of testing the service rule.
c) One key number test scenario: different from the conventional test scene and the rule test scene, enumeration configuration is performed in the data source, and configuration content comprises a series of page operations such as names, keyword identification, default values, field states (whether to be started or not), whether to query items (text boxes/drop-down lists) and the like, so that the test scene of obtaining quick data output after input according to different fields can be satisfied.
It should be noted that the foregoing merely illustrates the technical idea of the present invention and is not intended to limit the scope of the present invention, and that a person skilled in the art may make several improvements and modifications without departing from the principles of the present invention, which fall within the scope of the claims of the present invention.
Claims (8)
1. The automatic mixed scene test method for the low-code assembled interface is characterized by comprising the following steps of:
step 1, creating an entry of three interface test scenes, wherein the three interface test scenes comprise: a conventional test scene, a rule test scene and a key number test scene;
step 2, assembling one or more operations of the low codes to form a mixed test scene;
and step 3, completing insurance service testing of different scenes through different data configuration items in the same scene script.
2. The method for testing the low-code assembled interface automatic mixed scene according to claim 1, wherein the step 1 specifically comprises the following sub-steps:
a) Creating a conventional test scene entry for premium testing in the insurance industry;
b) Creating a rule test scene entry for verifying the correctness of the business rule of the insurance company;
c) A bond number test scenario entry is created for special testing in significant bond number requirements.
3. The low code assembled interface automated mixed scenario testing method of claim 1, wherein the operations assembled in step 2 comprise one or more of the following operations:
a) Adding a protocol request, wherein at least one operation in the protocol request is realized by adopting a low-code mouse operation mode;
b) Adding an existing interface template/scene template of the platform, and rapidly completing the creation operation;
c) Adding a JDBC request;
d) A loop/if/while controller is added.
4. The method for testing the low-code assembled interface automation mixed scene according to claim 3, wherein the protocol request is an HTTP request, and comprises an interface request, an interface response, a response assertion, a variable extraction, a pre-operation and a post-operation; the extraction variable is extracted by a right mouse button JsonPath; the numerical value transmission between interfaces is carried out by taking the extracted variable as a parameter for context association, and the variables are associated through a mouse operation insertion form when the context of the interfaces is associated.
5. The method for automatically testing a hybrid scene of a low-code assembled interface according to claim 3, wherein when a certain field in the response message is quickly saved as a variable, a right key "Copy json path" process is performed on the field to be extracted in the text field of the response message, and the field is quickly saved as a variable and then provided for other messages to be used as a variable reference.
6. The low code assembled interface automated mixed scenario test method of claim 1, wherein the data configuration items are data sources comprising "default static data" and "poll scenario data".
7. The method for testing the low-code assembled interface automation mixed scene according to claim 1, wherein the step 3 specifically comprises the following three testing scenes:
a) Conventional test scenario: the method comprises the steps that polling scene data is used as a data source, interface association operation is carried out by taking a request message and a specific value of a table as variables, and a test scene of the premium and premium measurement of the insurance industry is met in a data-driven circulating table mode when a platform executes;
b) Rule test scenario: adding a specific column caseNumber, caseName, expectResult into a data source of the polling scene data, and enabling the platform to meet the test scene of rule test of the insurance industry through execution logic of a specific design and statistical processing logic after execution;
c) One key number test scenario: and performing enumeration configuration in the data source, and meeting the test scene of obtaining quick data output by executing according to the input of different fields.
8. The method of low code assembled interface automated mixed scenario testing of claim 7, wherein the specific design execution logic is: when operating with a "polling scene data" data source as a data drive, a particular column is selected
caseNumber, caseName, expectResult, comparing the interface response result with the expected result of the data source when the operation is completed, and writing the interface response result into the test result according to the actual service requirement.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311271500.4A CN117520145A (en) | 2023-09-28 | 2023-09-28 | Automatic mixed scene test method for low-code assembled interface |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311271500.4A CN117520145A (en) | 2023-09-28 | 2023-09-28 | Automatic mixed scene test method for low-code assembled interface |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117520145A true CN117520145A (en) | 2024-02-06 |
Family
ID=89750188
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311271500.4A Pending CN117520145A (en) | 2023-09-28 | 2023-09-28 | Automatic mixed scene test method for low-code assembled interface |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117520145A (en) |
-
2023
- 2023-09-28 CN CN202311271500.4A patent/CN117520145A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108614770B (en) | Automatic test assertion method, device, storage medium and equipment | |
| CN109739766B (en) | System and method for rapidly building FPGA digital simulation model | |
| CN112561370B (en) | Method and device for managing software release, computer equipment and storage medium | |
| CN109933521A (en) | Automated testing method, device, computer equipment and storage medium based on BDD | |
| CN111813661A (en) | Global service data drive automatic test method, device, equipment and medium | |
| CN111737152B (en) | Method and device for realizing WEB automatic test by inputting data through webpage | |
| CN110990274A (en) | Data processing method, device and system for generating test case | |
| CN112433948A (en) | Simulation test system and method based on network data analysis | |
| CN114385243B (en) | Method and device for automatically issuing instructions for controlling layout engine | |
| CN117520145A (en) | Automatic mixed scene test method for low-code assembled interface | |
| CN115827051A (en) | Software integration management system, method and server | |
| CN114969115A (en) | Data management method and system based on standardized metadata system | |
| CN113672509A (en) | Automatic testing method, device, testing platform and storage medium | |
| CN114297961A (en) | Chip test case processing method and related device | |
| CN114218105A (en) | UI automatic regression testing system based on configuration application mode | |
| CN112527655A (en) | Software version quality abnormity detection method and device, electronic equipment and storage medium | |
| CN111459809A (en) | Software testing method based on rapid demand version iteration | |
| Bicevskis et al. | Data quality model-based testing of information systems | |
| US20060277251A1 (en) | Information processing apparatus and system development method | |
| CN116661758B (en) | Method, device, electronic equipment and medium for optimizing log framework configuration | |
| CN114756217B (en) | Plug-in based script generation system | |
| CN112988555B (en) | Interface testing method, device, equipment and storage medium | |
| CN115098364A (en) | Single-interface robustness automatic test system and method thereof | |
| KR100656559B1 (en) | Program Automatic Generating Tools | |
| CN114461514A (en) | Automatic testing method and system based on low codes |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |