CN117056211A - Low-code automatic test method and device, electronic equipment and storage medium - Google Patents
Low-code automatic test method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN117056211A CN117056211A CN202310953978.9A CN202310953978A CN117056211A CN 117056211 A CN117056211 A CN 117056211A CN 202310953978 A CN202310953978 A CN 202310953978A CN 117056211 A CN117056211 A CN 117056211A
- Authority
- CN
- China
- Prior art keywords
- test
- behavior
- cases
- template
- result
- 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 19
- 238000012360 testing method Methods 0.000 claims abstract description 397
- 230000006399 behavior Effects 0.000 claims abstract description 163
- 238000000034 method Methods 0.000 claims abstract description 30
- 230000008569 process Effects 0.000 claims abstract description 11
- 238000012163 sequencing technique Methods 0.000 claims abstract description 6
- 230000000007 visual effect Effects 0.000 claims description 17
- 238000012795 verification Methods 0.000 claims description 5
- 238000004590 computer program Methods 0.000 claims description 3
- 230000004044 response Effects 0.000 claims description 2
- 238000011161 development Methods 0.000 abstract description 5
- 238000004891 communication Methods 0.000 description 11
- 230000006870 function Effects 0.000 description 6
- 230000009286 beneficial effect Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000012423 maintenance Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000013522 software testing Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 239000008186 active pharmaceutical agent Substances 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004140 cleaning Methods 0.000 description 1
- 230000001419 dependent effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000002360 preparation method Methods 0.000 description 1
- 238000006467 substitution reaction 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/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- 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
-
- 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/3692—Test management for test results analysis
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 application provides a low-code automatic test method, a device, electronic equipment and a storage medium, comprising the following steps: creating a set of reusable test behavior templates, which comprise test behavior operation and configuration parameters, and defining pre-conditions and post-conditions of the test behavior operation; creating a test case flow chart, and executing test on the test behavior templates according to the set test behavior operation sequence; storing the verified test cases; loading the verified test cases, inversely sequencing the test cases into a test case model, instantiating test behaviors into objects according to the test case model, and executing the test behaviors according to a defined sequence; and collecting the execution result and log information of each test behavior template, and storing the execution result and log information to generate a test report. The method of the application can accelerate the test process, reduce artificial errors, improve the test repeatability, and provide detailed test results and log information, thereby improving the software quality and development efficiency.
Description
Technical Field
The application belongs to the field of software testing, and particularly relates to a low-code automatic testing method and device, electronic equipment and a storage medium.
Background
In the field of software testing, the automatic testing method is that a testing case writer adopts an automatic testing tool to write codes to call various APIs according to service scenes, so as to simulate user behaviors and achieve the set aim.
In the process of low-code automatic test, a tester needs to write a large number of repeated codes to meet the automatic test under different working conditions, so that the tester wastes a large amount of test case writing and maintenance time, and in the process of test execution, the received thought factors also have great influence on test results, thereby causing the problems of low software quality and development efficiency.
Disclosure of Invention
In view of this, the present application aims to provide a low-code automatic test method, a device, an electronic apparatus, and a storage medium, so as to solve the problem that in the low-code automatic test process, a tester needs to write a large amount of repeated codes, which results in that the tester wastes a large amount of test case writing and maintenance time, thereby affecting the software quality and development efficiency.
In order to achieve the above purpose, the technical scheme of the application is realized as follows:
in a first aspect, the present application provides a method, an apparatus, an electronic device, and a storage medium for low-code automated testing, where the method includes:
defining test behavior templates, creating a group of reusable test behavior templates, wherein each template comprises parameters corresponding to test behavior operation and configuration, and defining pre-conditions and post-conditions of the test behavior operation;
creating a test case flow chart, creating the test case flow chart by using a visual interface, and executing test on the test behavior template according to the set test behavior operation sequence;
verifying and storing the test cases, and storing the verified test cases;
loading and executing test cases, loading verified test cases, inversely sequencing the test cases into a test case model, instantiating test behaviors into objects according to the test case model, and executing the test behaviors according to a defined sequence;
collecting test results and logs, collecting execution results and log information of each test behavior template, and storing the execution results and log information to generate a test report.
In a second aspect, based on the same inventive concept, the present application also provides a low code automation test device, the device comprising:
the definition module is configured to define test behavior templates, a set of reusable test behavior templates is created, each template comprises test behavior operation and configuration corresponding parameters, and pre-conditions and post-conditions of the test behavior operation are defined;
the flow creation module is configured to create a test case flow chart, create the test case flow chart by using the visual interface and execute the test on the test behavior template according to the set test behavior operation sequence;
the verification module is configured to verify and save the test cases and save the verified test cases;
the model test module is configured to load and execute test cases, load the verified test cases, inverse sequence the test cases into a test case model, instantiate test behaviors into objects according to the test case model, and execute the test behaviors according to a defined sequence;
the test result module is configured to collect test results and logs, collect execution results and log information of each test behavior template, store the results and log information and generate a test report.
In a third aspect, based on the same inventive concept, the present application also provides an electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, said processor implementing the low code automated test method as described above when executing said program.
In a fourth aspect, based on the same inventive concept, the present application also provides a non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the low code automated test method as described above.
Compared with the prior art, the low-code automatic testing method, the device, the electronic equipment and the storage medium have the following beneficial effects:
according to the low-code automatic test method, the device, the electronic equipment and the storage medium, a set of reusable test behavior templates are created by defining the test behavior templates, each template comprises test behavior operation and configuration corresponding parameters, and pre-conditions and post-conditions of the test behavior operation are defined; creating a test case flow chart, creating the test case flow chart by using a visual interface, and executing test on the test behavior template according to the set test behavior operation sequence; verifying and storing the test cases, and storing the verified test cases; loading and executing test cases, loading verified test cases, inversely sequencing the test cases into a test case model, instantiating test behaviors into objects according to the test case model, and executing the test behaviors according to a defined sequence; the method can reduce the workload of manually writing test codes, greatly improve the test efficiency, quickly create and execute test cases by defining the test behavior templates and the test case flow charts without writing a large number of repeated codes, enable the tester to use the same template for executing the test for many times, reduce the influence of human factors in the test execution process on the test result, enable the tester to load and execute the saved test cases at any time, save the time and energy for writing and maintaining the test cases, and improve the software quality and development efficiency.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application. In the drawings:
FIG. 1 is a flow chart of a low code automation test method according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a low-code automated test equipment according to an embodiment of the present application;
fig. 3 is a schematic hardware structure of an electronic device according to an embodiment of the present application.
Detailed Description
The present application will be further described in detail below with reference to specific embodiments and with reference to the accompanying drawings, in order to make the objects, technical solutions and advantages of the present application more apparent.
It should be noted that unless otherwise defined, technical or scientific terms used in the embodiments of the present application should be given the ordinary meaning as understood by one of ordinary skill in the art to which the present application belongs. The terms "first," "second," and the like, as used in embodiments of the present application, do not denote any order, quantity, or importance, but rather are used to distinguish one element from another. The word "comprising" or "comprises", and the like, means that elements or items preceding the word are included in the element or item listed after the word and equivalents thereof, but does not exclude other elements or items. The terms "connected" or "connected," and the like, are not limited to physical or mechanical connections, but may include electrical connections, whether direct or indirect. "upper", "lower", "left", "right", etc. are used merely to indicate relative positional relationships, which may also be changed when the absolute position of the object to be described is changed.
Embodiments of the present application are described in detail below with reference to the accompanying drawings.
Referring to fig. 1, a low code automation test method according to an embodiment of the application includes the following steps:
step S101, defining test behavior templates, creating a set of reusable test behavior templates, wherein each template comprises parameters corresponding to test behavior operation and configuration, and defining pre-conditions and post-conditions of the test behavior operation.
In some embodiments, a test behavior template is defined to determine the targets and ranges of the test behavior template, and to determine test behavior operations to be performed and corresponding configuration parameters;
combining the test behavior operation and configuration parameters to form a reusable test behavior template;
the preconditions and the postconditions of the test behavior operation are defined to ensure the executability of the test behavior templates.
Specifically, the target and range of the test behavior templates are determined, such as login function test, registration function test and the like, required test behavior operation and corresponding configuration parameters are determined, the test behavior operation and the configuration parameters are combined to form a reusable test behavior template, the template should have definite input and output so as to accurately judge success or failure when being executed, the parameter required to be configured is determined for each test behavior operation, the parameter can be a fixed value or a value required to be dynamically generated or transmitted from outside, the precondition is a condition required to be met before the test behavior operation is executed, the precondition is a condition required to be met after the test behavior operation is executed, such as the pre-operation, the preparation of specific data and the like, the post-condition is a condition expected to be achieved after the test behavior operation is executed, such as a verification result, cleaning data and the like, through the steps, a set of reusable test behavior templates can be defined and created, and each template is ensured to contain the test behavior operation, the configuration parameter, the pre-condition and the post-condition. The following is an example of this step:
testing a behavior template: user login function test
1. Test behavior operation:
opening a login page;
inputting a user name and a password;
clicking the login button.
Configuration parameters:
user name (parameterized), password (parameterized).
3. The pre-condition is as follows:
the application has been opened.
4. Post conditions:
verifying whether login is successful;
the login information is cleared.
By defining the test behavior template, the template can be reused in different test cases, and parameterized configuration is carried out according to specific test requirements and scenes, so that the test efficiency and consistency can be improved, and the accuracy and maintainability of test behavior operation can be ensured.
Step S102, creating a test case flow chart, creating the test case flow chart by using a visual interface, and executing test on the test behavior template according to the set test behavior operation sequence.
In some embodiments, creating a visual interface through a test management tool, drawing a test case flow chart on the visual interface, and organizing the execution flow of a test behavior template according to a set test behavior operation sequence;
and importing the created test behavior template into a test case flow chart, and executing the test case flow chart according to the set test behavior operation sequence.
Specifically, a visual interface is created by using a test management tool to support visual design and execution of test case flows, a test case flow chart is drawn on the visual interface, the execution flows of test behavior templates are organized according to a set test behavior operation sequence, and proper image symbols and connecting lines are used for representing contents such as test behavior operation, branching, circulation and the like; the method comprises the steps of importing a test behavior template created before into a test case flow chart, wherein each test behavior template represents a test step, organizing the test behavior templates into sequences, parallel or conditional execution according to actual requirements, determining the execution sequence of test behavior operation according to the test requirements and logic relations, for example, logging in first and then performing other operations, and executing the test case flow by using functions provided by a visual interface. And sequentially executing the test behavior templates according to the set sequence, and recording the execution result of each test step.
Step S103, verifying and storing the test cases, and storing the verified test cases.
In some embodiments, verifying the result of the test case of the executed test case flow chart, and judging whether the result accords with a preset target result;
in response to the result being consistent, marking as pass;
if the result is not consistent, marking the result as failure, and recording the failure result;
and saving the verified test cases.
Specifically, according to the steps and the settings of the test cases, the test cases are gradually executed. Ensuring that each test step is performed as expected and recording the actual results, and for each test step, checking whether the actual results match the expected results. If the result meets the expectations, marking as passing; if the result does not meet the expectation, marking the test case as failure, recording the failure result, analyzing the failure reason according to the result, and recording the execution result of each test case, including the identification, description, execution state (passing/failing) and failure reason of the test case, wherein the test case can be recorded by using a test management tool, a spreadsheet or a document, and the like, the verified test case can be saved, and when the test case is saved, a test case library or a folder can be established, and each test case can be saved as an independent file or record, so that the version control and document management of the test case are ensured, and the subsequent test execution and maintenance are convenient.
And step S104, loading and executing the test cases, loading the verified test cases, inversely sequencing the test cases into a test case model, instantiating the test behaviors into objects according to the test case model, and executing the test behaviors according to a defined sequence.
In some embodiments, loading and executing a verified test case, and deserializing the loaded test case data into a test case model, wherein the test case model is a structured object and comprises the attribute and the behavior of the test case;
instantiating corresponding test behavior objects according to the test behaviors defined in the test case model, and ensuring that the test behaviors are executed according to a defined test sequence;
after the test behavior is performed, it is checked whether the execution result meets the expected result.
Specifically, test case data is loaded from a stored position, and can be loaded from a file, a database, a test management tool or the like, and the loaded test case data is deserialized into a test case model. The test case model is a structured object and comprises the attribute and the behavior of the test case, the corresponding test behavior object is instantiated according to the test behaviors defined in the test case model, the test behavior object can be a custom class or function and is used for executing specific test behaviors, the test behavior objects are executed one by one according to the sequence defined in the test case model, the test behaviors are ensured to be executed according to the predefined sequence so as to ensure the integrity and the repeatability of the test, and after each test behavior is executed, whether an execution result meets expectations is checked. And judging whether the test behavior passes or fails according to the expected result defined in the test case model, and recording an execution result.
Step 105, collecting test results and logs, collecting execution results and log information of each test behavior template, and storing the execution results and log information to generate a test report.
In some embodiments, after each test behavior template is executed, collecting and recording an execution result, judging an execution state of the test behavior template according to an expected result and an actual result, and recording;
in the execution process of each test behavior template, recording related log information, wherein the log information comprises an execution time stamp, an input parameter, an output result and an error message;
and generating a test report according to the stored execution result and the log information.
Specifically, in the execution process of each test behavior template, relevant log information including an execution time stamp, input parameters, output results, error messages and the like is recorded, so that the test results can be analyzed, debugged and analyzed through the log information, the execution results and the log information of each test behavior template are saved, a test report is generated according to the saved execution results and log information, the test report includes the number of the test passing behavior templates, the number of failed behavior templates, the execution time, error details and the like, and a test report generating tool or a custom script can be used for generating the test report.
According to the low-code automatic test method, a set of reusable test behavior templates is created by defining the test behavior templates, each template comprises test behavior operation and configuration corresponding parameters, and pre-conditions and post-conditions of the test behavior operation are defined; creating a test case flow chart, creating the test case flow chart by using a visual interface, and executing test on the test behavior template according to the set test behavior operation sequence; verifying and storing the test cases, and storing the verified test cases; loading and executing test cases, loading verified test cases, inversely sequencing the test cases into a test case model, instantiating test behaviors into objects according to the test case model, and executing the test behaviors according to a defined sequence; the method can reduce the workload of manually writing test codes, greatly improve the test efficiency, quickly create and execute test cases without writing a large number of repeated codes by defining the test behavior templates and the test case flow charts, the tester can use the same template for executing the test for multiple times, reduce the influence of human factors in the test execution process on the test result, load and execute the saved test cases at any time, save the time and energy of writing and maintaining the test cases, and the low-code automatic test method can accelerate the test process, reduce human errors, improve the test repeatability, provide detailed test results and log information, thereby improving the software quality and development efficiency.
It should be noted that the foregoing describes some embodiments of the present application. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments described above and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.
Based on the same inventive concept, the embodiment of the application also provides a low-code automatic testing device corresponding to the method of any embodiment.
As shown in fig. 2, the low-code automated test apparatus includes:
the definition module 11 is configured to define test behavior templates, create a set of reusable test behavior templates, each template contains test behavior operation and configuration corresponding parameters, and define pre-conditions and post-conditions of the test behavior operation;
the flow creation module 12 is configured to create a test case flow chart, create the test case flow chart by using the visual interface, and execute a test on the test behavior template according to the set test behavior operation sequence;
the verification module 13 is configured to verify and save the test cases, and save the verified test cases;
the model test module 14 is configured to load and execute test cases, load verified test cases, deserialize the test cases into a test case model, instantiate test behaviors into objects according to the test case model, and execute the test behaviors according to a defined sequence;
the test result module 15 is configured to collect test results and logs, collect execution results and log information of each test behavior template, and store the results and log information to generate a test report.
For convenience of description, the above devices are described as being functionally divided into various modules, respectively. Of course, the functions of each module may be implemented in the same piece or pieces of software and/or hardware when implementing an embodiment of the present application.
The device of the foregoing embodiment is configured to implement the corresponding low-code automated test method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiment, which is not described herein.
Based on the same inventive concept, corresponding to the method of any embodiment, the embodiment of the application further provides an electronic device, which comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the program to implement the low-code automatic test method according to any embodiment.
Fig. 3 shows a more specific hardware architecture of an electronic device according to this embodiment, where the device may include: a processor 1010, a memory 1020, an input/output interface 1030, a communication interface 1040, and a bus 1050. Wherein processor 1010, memory 1020, input/output interface 1030, and communication interface 1040 implement communication connections therebetween within the device via a bus 1050.
The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit ), microprocessor, application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, etc. for executing relevant programs to implement the technical solutions provided in the embodiments of the present disclosure.
The Memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory ), static storage device, dynamic storage device, or the like. Memory 1020 may store an operating system and other application programs, and when the embodiments of the present specification are implemented in software or firmware, the associated program code is stored in memory 1020 and executed by processor 1010.
The input/output interface 1030 is used to connect with an input/output module for inputting and outputting information. The input/output module may be configured as a component in a device (not shown) or may be external to the device to provide corresponding functionality. Wherein the input devices may include a keyboard, mouse, touch screen, microphone, various types of sensors, etc., and the output devices may include a display, speaker, vibrator, indicator lights, etc.
Communication interface 1040 is used to connect communication modules (not shown) to enable communication interactions of the present device with other devices. The communication module may implement communication through a wired manner (such as USB, network cable, etc.), or may implement communication through a wireless manner (such as mobile network, WIFI, bluetooth, etc.).
Bus 1050 includes a path for transferring information between components of the device (e.g., processor 1010, memory 1020, input/output interface 1030, and communication interface 1040).
It should be noted that although the above-described device only shows processor 1010, memory 1020, input/output interface 1030, communication interface 1040, and bus 1050, in an implementation, the device may include other components necessary to achieve proper operation. Furthermore, it will be understood by those skilled in the art that the above-described apparatus may include only the components necessary to implement the embodiments of the present description, and not all the components shown in the drawings.
The electronic device of the foregoing embodiment is configured to implement the corresponding low-code automated test method in any of the foregoing embodiments, and has the beneficial effects of the corresponding method embodiment, which is not described herein.
Based on the same inventive concept, the present application also provides a non-transitory computer readable storage medium storing computer instructions for causing the computer to perform the low code automated test method according to any of the embodiments above, corresponding to any of the embodiments above.
The computer readable media of the present embodiments, including both permanent and non-permanent, removable and non-removable media, may be used to implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device.
The storage medium of the foregoing embodiments stores computer instructions for causing the computer to execute the low-code automated test method according to any one of the foregoing embodiments, and has the advantages of the corresponding method embodiments, which are not described herein.
Those of ordinary skill in the art will appreciate that: the discussion of any of the embodiments above is merely exemplary and is not intended to suggest that the scope of the application (including the claims) is limited to these examples; the technical features of the above embodiments or in the different embodiments may also be combined within the idea of the application, the steps may be implemented in any order, and there are many other variations of the different aspects of the embodiments of the application as described above, which are not provided in detail for the sake of brevity.
Additionally, well-known power/ground connections to Integrated Circuit (IC) chips and other components may or may not be shown within the provided figures, in order to simplify the illustration and discussion, and so as not to obscure the embodiments of the present application. Furthermore, the devices may be shown in block diagram form in order to avoid obscuring the embodiments of the present application, and also in view of the fact that specifics with respect to implementation of such block diagram devices are highly dependent upon the platform within which the embodiments of the present application are to be implemented (i.e., such specifics should be well within purview of one skilled in the art). Where specific details (e.g., circuits) are set forth in order to describe example embodiments of the application, it should be apparent to one skilled in the art that embodiments of the application can be practiced without, or with variation of, these specific details. Accordingly, the description is to be regarded as illustrative in nature and not as restrictive.
While the application has been described in conjunction with specific embodiments thereof, many alternatives, modifications, and variations of those embodiments will be apparent to those skilled in the art in light of the foregoing description. For example, other memory architectures (e.g., dynamic RAM (DRAM)) may use the embodiments discussed.
The present embodiments are intended to embrace all such alternatives, modifications and variances which fall within the broad scope of the appended claims. Therefore, any omissions, modifications, equivalent substitutions, improvements, and the like, which are within the spirit and principles of the embodiments of the application, are intended to be included within the scope of the application.
Claims (10)
1. A method of low code automated testing, the method comprising:
defining test behavior templates, creating a group of reusable test behavior templates, wherein each template comprises parameters corresponding to test behavior operation and configuration, and defining pre-conditions and post-conditions of the test behavior operation;
creating a test case flow chart, creating the test case flow chart by using a visual interface, and executing test on the test behavior template according to the set test behavior operation sequence;
verifying and storing the test cases, and storing the verified test cases;
loading and executing test cases, loading verified test cases, inversely sequencing the test cases into a test case model, instantiating test behaviors into objects according to the test case model, and executing the test behaviors according to a defined sequence;
collecting test results and logs, collecting execution results and log information of each test behavior template, and storing the execution results and log information to generate a test report.
2. The method of claim 1, wherein defining the test behavior templates, creating a set of reusable test behavior templates, each template including parameters corresponding to the test behavior operation and configuration, and defining pre-conditions and post-conditions for the test behavior operation, comprises:
defining a test behavior template to determine the target and range of the test behavior template, and determining the test behavior operation to be executed and the corresponding configuration parameters;
combining the test behavior operation and configuration parameters to form a reusable test behavior template;
the preconditions and the postconditions of the test behavior operation are defined to ensure the executability of the test behavior templates.
3. The method for automatically testing the low code according to claim 1, wherein creating the test case flowchart and creating the test case flowchart using the visual interface, and performing the test on the test behavior templates according to the set test behavior operation sequence, comprises:
creating a visual interface through a test management tool, drawing a test case flow chart on the visual interface, and organizing the execution flow of a test behavior template according to a set test behavior operation sequence;
and importing the created test behavior template into a test case flow chart, and executing the test case flow chart according to the set test behavior operation sequence.
4. The method for automatically testing low code according to claim 3, wherein said verifying and saving test cases, saving the verified test cases, comprises:
performing result verification on the test cases of the executed test case flow chart, and judging whether the test cases are consistent with a preset target result;
in response to the result being consistent, marking as pass;
if the result is not consistent, marking the result as failure, and recording the failure result;
and saving the verified test cases.
5. The method for automatically testing low code according to claim 1, wherein the loading and executing test cases, loading verified test cases, de-ordering the test cases into a test case model, instantiating test behaviors into objects according to the test case model, and executing the test behaviors in a defined order, comprises:
loading and executing the verified test case, and deserializing the loaded test case data into a test case model, wherein the test case model is a structured object and comprises the attribute and the behavior of the test case;
and instantiating corresponding test behavior objects according to the test behaviors defined in the test case model, and ensuring that the test behaviors are executed according to the defined test sequence.
6. The low code automated test method of claim 5, further comprising:
after the test behavior is performed, it is checked whether the execution result meets the expected result.
7. The method of claim 6, wherein the collecting test results and logs, collecting and storing execution results and log information of each test behavior template, and generating test reports comprises:
after each test behavior template is executed, collecting and recording an execution result, judging the execution state of the test behavior template according to an expected result and an actual result, and recording;
in the execution process of each test behavior template, recording related log information, wherein the log information comprises an execution time stamp, an input parameter, an output result and an error message;
and generating a test report according to the stored execution result and the log information.
8. A low code automated test equipment, said equipment comprising:
the definition module is configured to define test behavior templates, a set of reusable test behavior templates is created, each template comprises test behavior operation and configuration corresponding parameters, and pre-conditions and post-conditions of the test behavior operation are defined;
the flow creation module is configured to create a test case flow chart, create the test case flow chart by using the visual interface and execute the test on the test behavior template according to the set test behavior operation sequence;
the verification module is configured to verify and save the test cases and save the verified test cases;
the model test module is configured to load and execute test cases, load the verified test cases, inverse sequence the test cases into a test case model, instantiate test behaviors into objects according to the test case model, and execute the test behaviors according to a defined sequence;
the test result module is configured to collect test results and logs, collect execution results and log information of each test behavior template, store the results and log information and generate a test report.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the low code automated test method of any of claims 1-7 when the program is executed by the processor.
10. A non-transitory computer readable storage medium, wherein the non-transitory computer readable storage medium stores computer instructions for causing the computer to perform the low code automated test method of any of claims 1-7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310953978.9A CN117056211A (en) | 2023-07-31 | 2023-07-31 | Low-code automatic test method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310953978.9A CN117056211A (en) | 2023-07-31 | 2023-07-31 | Low-code automatic test method and device, electronic equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117056211A true CN117056211A (en) | 2023-11-14 |
Family
ID=88668433
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310953978.9A Pending CN117056211A (en) | 2023-07-31 | 2023-07-31 | Low-code automatic test method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117056211A (en) |
-
2023
- 2023-07-31 CN CN202310953978.9A patent/CN117056211A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109871326B (en) | Script recording method and device | |
| US9465718B2 (en) | Filter generation for load testing managed environments | |
| US8799875B2 (en) | Streamlining unit testing through hot code swapping | |
| JP2022537620A (en) | artificial intelligence chip verification | |
| CN110716870B (en) | Automatic service testing method and device | |
| CN107832059B (en) | Code static analysis method and device based on Makefile | |
| CN107526676B (en) | Cross-system test method and device | |
| CN111124870A (en) | Interface testing method and device | |
| CN115658529A (en) | Automatic testing method for user page and related equipment | |
| CN107622017B (en) | Analysis method for universal automation software test | |
| CN114579452A (en) | Interface influence detection method and related equipment | |
| CN117421217A (en) | Automatic software function test method, system, terminal and medium | |
| CN112231206A (en) | Script editing method for application program test, computer readable storage medium and test platform | |
| CN110134598B (en) | Batch processing method, device and system | |
| CN111680463A (en) | File checking method and device | |
| CN117370217A (en) | Automatic interface test result generation method based on python | |
| CN116860608A (en) | Interface testing method and device, computing equipment and storage medium | |
| CN116841898A (en) | Test case and test script generation method, device, system and medium | |
| US20130283238A1 (en) | Testing system for an integrated software system | |
| CN113378502B (en) | Test method, device, medium and equipment for verifying signal trend code matching | |
| CN115033434A (en) | Kernel performance theoretical value calculation method and device and storage medium | |
| CN117056211A (en) | Low-code automatic test method and device, electronic equipment and storage medium | |
| CN111949510B (en) | Test processing method, device, electronic equipment and readable storage medium | |
| CN113535581A (en) | Test script generation method, device, equipment and computer readable storage medium | |
| CN114756217B (en) | Plug-in based script generation system |
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 |