CN112231197A - Page testing method and device and storage medium - Google Patents
Page testing method and device and storage medium Download PDFInfo
- Publication number
- CN112231197A CN112231197A CN201910635406.XA CN201910635406A CN112231197A CN 112231197 A CN112231197 A CN 112231197A CN 201910635406 A CN201910635406 A CN 201910635406A CN 112231197 A CN112231197 A CN 112231197A
- Authority
- CN
- China
- Prior art keywords
- control element
- test
- tested
- operation type
- testing
- 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
Images
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
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 discloses a page testing method, a page testing device and a storage medium, and specifically comprises the steps of generating a testing script for a page to be tested, editing a testing case for each interface function to be tested of the page to be tested, wherein the testing case comprises testing steps for testing the interface function to be tested, each testing step comprises one control element related to the interface function to be tested and one operation type corresponding to the control element, an operation value corresponding to the operation type is added in each testing step, the control element, the operation type and the operation value in each testing step are input into the testing script according to the sequence of each testing step in the testing case, and the testing case is tested by the testing script. According to the method and the device, the test cases containing all the test steps are edited for the functions of the interface to be tested, the test scripts generated in advance are suitable for testing according to the sequence of the test steps in the test cases, the new test scripts do not need to be compiled, and the test efficiency is improved.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for testing a page, and a storage medium.
Background
The User Interface (UI) refers to the overall design of human-computer interaction, operation logic and beautiful Interface of software. By designing the UI interface on the web page, the software can become individual and tasteful, the operation of the software can become comfortable, simple and free, and the positioning and the characteristics of the software can be fully embodied.
After the UI is designed, the UI function needs to be tested to ensure normal operation of the UI function. Conventional UI testing typically performs UI function testing on web pages by writing test scripts. In general, the same test script can only test the UI function of the original fixed page. When the attribute of a certain control in a web page changes, or a certain control is newly added and deleted, or the operation sequence changes, the original test script cannot be used continuously, the code needs to be modified again, and the test script is redeployed after debugging. Most of the web pages, contents, functions and other interaction modes at the present stage cannot be fixed for a long time and may be frequently changed. Therefore, a large workload is caused to the testing personnel, the tested web page changes again after the new testing script is just modified and debugged, the original script cannot be used continuously, and the modification needs to be continued. Therefore, the conventional UI function testing method is high in writing cost and is not suitable for performing web function testing in the fast-paced Internet industry.
Disclosure of Invention
The embodiment of the application provides a page testing method, which overcomes the defect that a test script needs to be changed when a web page is maintained by editing a test case for updating, and improves the testing efficiency.
The specific method comprises the following steps:
generating a test script for the page to be tested;
editing a test case for each interface function to be tested of the page to be tested, wherein the test case comprises a test step for testing the interface function to be tested, and each test step comprises one control element related to the interface function to be tested and one operation type corresponding to the control element;
adding an operation value corresponding to the operation type in each test step;
and inputting the control element, the operation type and the operation value in each test step into the test script according to the sequence of each test step in the test case, and testing the test case by the test script.
Optionally, acquiring each control element contained in the page to be tested;
enumerating an operation type of each of the control elements;
and generating a test script according to each control element and each operation type corresponding to each control element.
And optionally, when the control element and the operation type corresponding to the control element are newly added to the page to be tested, writing the newly added control element and the operation type corresponding to the control element as the newly added test step into the test case of the interface function to be tested corresponding to the newly added control element and the operation type corresponding to the newly added control element.
Optionally, when the control element and the operation type corresponding to the control element are deleted from the page to be tested, the corresponding control element and the operation type are deleted from the test case of the interface function to be tested.
In another embodiment of the present invention, there is provided an apparatus for data testing, the apparatus including:
the generating module is used for generating a test script for the page to be tested;
the editing module is used for editing a test case for each interface function to be tested of the page to be tested, the test case comprises test steps for testing the interface function to be tested, and each test step comprises one control element related to the interface function to be tested and one operation type corresponding to the control element;
an adding module, configured to add an operation value corresponding to the operation type in each of the testing steps;
and the test module is used for inputting the control element, the operation type and the operation value in each test step into the test script according to the sequence of each test step in the test case, and testing the test case by the test script.
Optionally, the generating module includes:
the acquiring unit is used for acquiring each control element contained in the page to be detected;
the enumeration unit is used for enumerating the operation type of each control element;
and the generating unit is used for generating a test script according to each control element and each operation type corresponding to each control element.
Optionally, the apparatus further comprises:
and the adding module is used for taking the newly added control element and the operation type corresponding to the newly added control element as the newly added testing step when the control element and the operation type corresponding to the newly added control element are newly added to the page to be tested, and writing the newly added control element and the operation type corresponding to the newly added control element into the test case of the interface function to be tested.
Optionally, the apparatus further comprises:
and the deleting module is used for deleting the corresponding control element and the corresponding operation type in the test case of the interface function to be tested when the control element and the corresponding operation type are deleted from the page to be tested.
In another embodiment of the present invention, a non-transitory computer readable storage medium is provided, which stores instructions that, when executed by a processor, cause the processor to perform the steps of one of the data testing methods described above.
In another embodiment of the present invention, a terminal device is provided, which includes a processor for executing the steps of the data testing method.
As can be seen from the above, based on the data testing method provided in the foregoing embodiment, a test script is generated for a page to be tested, a test case is edited for each interface function to be tested of the page to be tested, the test case includes test steps for testing the interface function to be tested, each test step includes one of the control elements related to the interface function to be tested and one of the operation types corresponding to the control elements, an operation value corresponding to the operation type is added in each test step, the control elements, the operation types, and the operation values in each test step are input to the test script according to the sequence of each test step in the test case, and the test case is tested by the test script. According to the method and the device for testing the interface function, the test case containing each test step is edited for the interface function to be tested, and the test script generated in advance is suitable for testing according to the sequence of the test steps in the test case. And a new test script is not required to be compiled, so that the test efficiency is improved.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required to be used in the embodiments will be briefly described below, it should be understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered as limiting the scope, and for those skilled in the art, other related drawings can be obtained from the drawings without inventive effort.
Fig. 1 is a schematic flowchart illustrating a method for testing a page according to embodiment 10 of the present application;
fig. 2 is a schematic diagram illustrating a specific flow of a method for testing a page provided in embodiment 20 of the present application;
FIG. 3 is a schematic diagram illustrating functions of an interface to be tested in embodiment 30 of the present application;
FIG. 4 is a schematic diagram of an apparatus for data testing provided in embodiment 40 of the present application;
fig. 5 shows a schematic diagram of a terminal device provided in embodiment 50 of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is further described in detail below with reference to the accompanying drawings and examples.
The UI test aims at ensuring that the user interface can provide corresponding access or browse functions for the user through the functions of the test object, and the user interface meets the standards of companies or industries, and comprises user-friendly, humanized and easy-to-operate tests. Based on the problems in the prior art, embodiments of the present application provide a data testing method, which includes enumerating all control elements in a page to be tested and all operation types corresponding to each control element, marking a test case for each interface function to be tested, and testing the test case in a written test script. When the control elements are added or deleted subsequently, only the test cases need to be added or deleted, the test scripts do not need to be changed, and the test efficiency is improved.
The application field of the application is mainly in the technical field of computers and is generally suitable for software test scenes. As shown in fig. 1, a flowchart of a method for testing a page provided in embodiment 10 of the present application is schematically illustrated. Wherein, the detailed steps include:
and S11, generating a test script for the page to be tested.
In this step, the page to be tested includes a web page. The web page is a network service established on the Internet, provides a graphical and easily accessible visual interface for a browser to search and browse information on the Internet, and documents and hyperlinks organize information nodes on the Internet into a mutually-associated mesh structure. The generated test script may test for all possible operation types for all control elements in the web page. Specifically, all control elements in the page to be tested are enumerated, and then all operation types that each control element may perform are enumerated. Wherein a control element refers to a hypertext Markup Language object (HTML) in a web page. Such as an input box (text field), a button (button), a drop-down menu (select _ list), a link (link), etc. For each acquired control element, the operation types that each control may perform are listed. Further, an operation table is generated according to various control elements and corresponding operation types, as shown in table 1:
and converting the control elements and the corresponding operation types in the table 1 into test scripts. For example, for two possible operation types (input value and read value) of the control element "input box (text _ field)", the test script is:
if (web control ═ text field ") (c ═ f-
if (operation ═ input value')
Reading the operation value in the excel table, and inputting the operation value into the execution element
else if (operation ═ read value)
Reading the operation value content in the excel table
}
The script content of the test script into which the other types of control elements and corresponding operation types are translated is similar to the script content in the test script in the above example. Wherein the translated test script may be written using python, java, or other programming language.
And S12, editing a test case for each interface function to be tested of the page to be tested.
In this step, the page to be tested includes a plurality of interface functions to be tested. And the interface functions to be tested comprise UI functions to be tested. The UI function is a page function provided in a web page, such as a page login function. Optionally, editing the test case for each interface function to be tested. Each test case comprises a test step for testing the interface function to be tested, and each test step comprises one control element related to the interface function to be tested and one operation type corresponding to the control element.
S13, adding an operation value corresponding to the operation type in each test step.
In this step, in the test case written for each UI function, an operation value corresponding to the operation type is added to the test step included in each test case. The operation value is an input, output or display value corresponding to the operation type. If the operation type of the control element "input box (text _ field)" is an input value and the operation value can be testuser, the testuser is added as the operation value into the test step corresponding to the operation type of the input value of the input box (text _ field). The addition of operation values corresponding to operation types in other test steps is similar to the above example.
And S14, inputting the control element, the operation type and the operation value in each test step into the test script according to the sequence of each test step in the test case, and testing the test case by the test script.
In this step, the test steps are determined according to the test sequence in each test case corresponding to the interface function to be tested. The last test step of each test case is result verification. And inputting the control elements, the operation types and the corresponding operation values in each test step in the test case into the test script determined in the step S11, and testing the test case.
The method for testing the page includes the steps of generating a test script for the page to be tested, editing a test case for each interface function to be tested of the page to be tested, wherein the test case comprises test steps for testing the interface function to be tested, each test step comprises one control element related to the interface function to be tested and one operation type corresponding to the control element, adding an operation value corresponding to the operation type in each test step, inputting the control element, the operation type and the operation value in each test step into the test script according to the sequence of each test step in the test case, and testing the test case by the test script. According to the method and the device for testing the interface function, the test case containing each test step is edited for the interface function to be tested, and the test script generated in advance is suitable for testing according to the sequence of the test steps in the test case. And a new test script is not required to be compiled, so that the test efficiency is improved.
Fig. 2 is a schematic diagram of a specific flow in a page testing method according to embodiment 20 provided in the present application. Wherein, the detailed process of the specific flow is as follows:
and S21, generating a test script for the page to be tested.
And finally, generating a test script according to each control element and each operation type corresponding to each control element.
And S22, editing a test case for each interface function to be tested of the page to be tested.
Here, a test case is edited in the Excel table for each interface function to be tested in the page to be tested. Each test case uses a sheet, and each control element and the operation type and operation value thereof are used as a line of test steps. Fig. 3 is a schematic diagram illustrating functions of an interface to be tested according to an embodiment of the present application. In which a web page login function is tested. Editing a test case for the function of the interface to be tested, as shown in the following table 2:
| control element | Attribute name | Attribute value | Type of operation | Operation value | Remarks for note | |
| 1 | text_field | id | username | Input value | testuser | Entering a user name |
| 2 | text_field | Id | password | Input value | 11111111 | Inputting a password |
| 3 | button | value | Login to | Single click | Click-to-login | |
| 4 | span | id | Login_result | Result verification | Success of login | Result verification |
The test case for the login function of the interface function web page to be tested comprises four test steps as shown in test steps 1 to 4 in table 2, and the last test step is result verification.
S23, editing the test case for the changed control element.
In this step, when the control element in the test case of the interface function to be tested is changed, for example, the control element is added or deleted in the interface function to be tested. Optionally, when the control element and the operation type corresponding to the control element are newly added to the page to be tested, the newly added control element and the operation type corresponding to the control element are used as a newly added test step, and are written into the test case of the interface function to be tested corresponding to the newly added control element and the operation type corresponding to the newly added control element. For example, a check box is newly added, checking is required before login, additional script codes are not required to be modified, and a row of operation types of the newly added control elements, namely the check boxes, is added to the excel.
Optionally, when the control element and the operation type corresponding to the control element are deleted from the page to be tested, the corresponding control element and operation type are deleted from the test case of the interface function to be tested. Here, the operation of deleting a control element is similar to the operation of adding a control element newly described above.
S24, adding an operation value corresponding to the operation type in each test step.
And S25, testing the test case by using the test script.
Here, the test script generated in the aforementioned step S21 is executed in the order of the test steps in the test case, and each row parameter in the execl table is sequentially read in the order to perform the test. The operation type of the last test step of each test case is result verification. And when the last testing step is executed, reading the corresponding operation value and comparing the corresponding operation value with the preset content, wherein if the operation value is consistent, the test is passed, and if the operation value is inconsistent, the test is not passed.
The method for testing the page is achieved based on the steps. The data testing method provided in the embodiment of the application enumerates all control elements in a page to be tested (all web pages related to a system to be tested), enumerates all operation types which can be performed by each control element, and converts the operation types into a testing script written by a programming language. Furthermore, writing and post-maintenance are carried out on specific test cases corresponding to the interface functions to be tested through excel, one test case corresponds to one sheet in excel, each test step corresponds to one line of data in the table, and the test script successively reads each line in the table, executes the test and compares the test results. Under the same scene, for example, control elements and corresponding operations are newly added on the same page, the code of the test script is not required to be changed, and the test case can be updated only by editing excel (newly adding a line), so that the efficiency of daily maintenance of the UI automation test work is improved.
Based on the same inventive concept, as shown in fig. 4, a schematic diagram of a data testing apparatus provided in embodiment 40 of the present application is shown. Wherein, the device includes:
a generating module 41, configured to generate a test script for the page to be tested;
the editing module 42 is configured to edit a test case for each interface function to be tested of the page to be tested, where the test case includes a test step for testing the interface function to be tested, and each test step includes one of the control elements related to the interface function to be tested and one of the operation types corresponding to the control elements;
an adding module 43, configured to add an operation value corresponding to the operation type in each test step;
and the test module 44 is configured to input the control element, the operation type, and the operation value in each test step into the test script according to the sequence of each test step in the test case, and test the test case by the test script.
In this embodiment, specific functions and interaction modes of the generating module 41, the editing module 42, the adding module 43, and the testing module 44 may refer to the record of the embodiment corresponding to fig. 1, and are not described herein again.
Further, the generating module 41 includes:
the acquiring unit is used for acquiring each control element contained in the page to be detected;
the enumeration unit is used for enumerating the operation type of each control element;
and the generating unit is used for generating a test script according to each control element and each operation type corresponding to each control element.
Optionally, the apparatus further comprises:
and the adding module 45 is configured to, when the control element and the operation type corresponding to the control element are newly added to the page to be tested, write the newly added control element and the operation type corresponding to the newly added control element as a newly added testing step into a test case of the interface function to be tested corresponding to the newly added control element and the operation type corresponding to the newly added control element.
Optionally, the apparatus further comprises:
and a deleting module 46, configured to delete the corresponding control element and operation type in the test case of the interface function to be tested when the control element and the corresponding operation type are deleted from the page to be tested.
As shown in fig. 5, another embodiment 50 of the present application further provides a terminal device, which includes a processor 50, wherein the processor 50 is configured to execute the steps of the method for controlling a smart sound box.
As can also be seen from fig. 5, the terminal device provided by the above embodiment further includes a non-transitory computer readable storage medium 51, where the non-transitory computer readable storage medium 51 stores thereon a computer program, and the computer program is executed by the processor 50 to perform the steps of the above-mentioned method for page testing.
In particular, the storage medium can be a general-purpose storage medium, such as a removable disk, a hard disk, a FLASH, and the like, and when the computer program on the storage medium is executed, the computer program can perform the steps of the page testing method.
Finally, it should be noted that: the above-mentioned embodiments are only specific embodiments of the present application, and are used for illustrating the technical solutions of the present application, but not limiting the same, and the scope of the present application is not limited thereto, and although the present application is described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: any person skilled in the art can modify or easily conceive the technical solutions described in the foregoing embodiments or equivalent substitutes for some technical features within the technical scope disclosed in the present application; such modifications, changes or substitutions do not depart from the spirit and scope of the exemplary embodiments of the present application, and are intended to be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. A method of page testing, the method comprising:
generating a test script for the page to be tested;
editing a test case for each interface function to be tested of the page to be tested, wherein the test case comprises a test step for testing the interface function to be tested, and each test step comprises one control element related to the interface function to be tested and one operation type corresponding to the control element;
adding an operation value corresponding to the operation type in each test step;
and inputting the control element, the operation type and the operation value in each test step into the test script according to the sequence of each test step in the test case, and testing the test case by the test script.
2. The method of claim 1, wherein the step of generating a test script for the page to be tested comprises:
acquiring each control element contained in the page to be detected;
enumerating an operation type of each of the control elements;
and generating a test script according to each control element and each operation type corresponding to each control element.
3. The method according to claim 1, wherein between the step of editing the test case for each interface function to be tested of the page to be tested and the step of adding the operation value corresponding to the operation type in each test step, the method further comprises:
and when the control element and the operation type corresponding to the control element are newly added to the page to be tested, writing the newly added control element and the operation type corresponding to the newly added control element as the newly added test step into the test case of the interface function to be tested corresponding to the newly added control element and the operation type corresponding to the newly added control element.
4. The method according to claim 1, wherein between the step of editing the test case for each interface function to be tested of the page to be tested and the step of adding the operation value corresponding to the operation type in each test step, the method further comprises:
and when the control element and the operation type corresponding to the control element are deleted from the page to be tested, deleting the corresponding control element and the operation type from the test case of the interface function to be tested.
5. An apparatus for data testing, the apparatus comprising:
the generating module is used for generating a test script for the page to be tested;
the editing module is used for editing a test case for each interface function to be tested of the page to be tested, the test case comprises test steps for testing the interface function to be tested, and each test step comprises one control element related to the interface function to be tested and one operation type corresponding to the control element;
an adding module, configured to add an operation value corresponding to the operation type in each of the testing steps;
and the test module is used for inputting the control element, the operation type and the operation value in each test step into the test script according to the sequence of each test step in the test case, and testing the test case by the test script.
6. The apparatus of claim 5, wherein the generating module comprises:
the acquiring unit is used for acquiring each control element contained in the page to be detected;
the enumeration unit is used for enumerating the operation type of each control element;
and the generating unit is used for generating a test script according to each control element and each operation type corresponding to each control element.
7. The apparatus of claim 5, the apparatus further comprising:
and the adding module is used for taking the newly added control element and the operation type corresponding to the newly added control element as the newly added testing step when the control element and the operation type corresponding to the newly added control element are newly added to the page to be tested, and writing the newly added control element and the operation type corresponding to the newly added control element into the test case of the interface function to be tested.
8. The apparatus of claim 5, the apparatus further comprising:
and the deleting module is used for deleting the corresponding control element and the corresponding operation type in the test case of the interface function to be tested when the control element and the corresponding operation type are deleted from the page to be tested.
9. A non-transitory computer readable storage medium storing instructions that, when executed by a processor, cause the processor to perform the steps of the method of any of claims 1 to 4.
10. A terminal device, comprising a processor configured to perform the steps of the method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910635406.XA CN112231197A (en) | 2019-07-15 | 2019-07-15 | Page testing method and device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910635406.XA CN112231197A (en) | 2019-07-15 | 2019-07-15 | Page testing method and device and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112231197A true CN112231197A (en) | 2021-01-15 |
Family
ID=74111466
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910635406.XA Pending CN112231197A (en) | 2019-07-15 | 2019-07-15 | Page testing method and device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112231197A (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113127354A (en) * | 2021-04-21 | 2021-07-16 | 武汉思普崚技术有限公司 | Automatic testing method, device and equipment based on Web UI and storage medium |
| CN113238969A (en) * | 2021-06-23 | 2021-08-10 | 中国农业银行股份有限公司 | Interface automation test method, device, equipment and storage medium |
| CN113568843A (en) * | 2021-09-18 | 2021-10-29 | 深圳市明源云科技有限公司 | HTML element processing method and device and storage medium |
-
2019
- 2019-07-15 CN CN201910635406.XA patent/CN112231197A/en active Pending
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113127354A (en) * | 2021-04-21 | 2021-07-16 | 武汉思普崚技术有限公司 | Automatic testing method, device and equipment based on Web UI and storage medium |
| CN113127354B (en) * | 2021-04-21 | 2023-08-11 | 武汉思普崚技术有限公司 | Automatic test method, device, equipment and storage medium based on Web UI |
| CN113238969A (en) * | 2021-06-23 | 2021-08-10 | 中国农业银行股份有限公司 | Interface automation test method, device, equipment and storage medium |
| CN113238969B (en) * | 2021-06-23 | 2024-02-23 | 中国农业银行股份有限公司 | Interface automation test method, device, equipment and storage medium |
| CN113568843A (en) * | 2021-09-18 | 2021-10-29 | 深圳市明源云科技有限公司 | HTML element processing method and device and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4148527B2 (en) | Functional test script generator | |
| US8468391B2 (en) | Utilizing log event ontology to deliver user role specific solutions for problem determination | |
| CN106550038B (en) | Data configuration diagnosis system and method of digital control system | |
| CN109308254B (en) | Test method, test device and test equipment | |
| CN112231197A (en) | Page testing method and device and storage medium | |
| CN108923997B (en) | Cloud service node automatic testing method and device based on python | |
| CN110908894B (en) | Visual report tool automatic testing method and device based on vuex | |
| US20170300305A1 (en) | Executable guidance experiences based on implicitly generated guidance models | |
| CN105589959A (en) | Form processing method and form processing system | |
| CN114138244A (en) | Method and device for automatically generating model files, storage medium and electronic equipment | |
| CN110781091A (en) | Application program testing method and device, electronic equipment and storage medium | |
| CN116028028A (en) | Request function generation method, device, equipment and storage medium | |
| US20220143825A1 (en) | Automated process robotic system, method, non transitory computer readable recording medium and computer program product with integrated process and automated data analysis | |
| CN117033249B (en) | Test case generation method and device, computer equipment and storage medium | |
| US20210232495A1 (en) | System and method for executing a test case | |
| CN111126008A (en) | XSD-based code generation method and device, computer equipment and storage medium | |
| JP2020173570A (en) | Analysis apparatus, analysis method, and program | |
| JP7380851B2 (en) | Test script generation device, test script generation method and program | |
| KR101476536B1 (en) | The method and system for inspecting program | |
| CN114356783A (en) | Method and device for automatically generating unit test code, storage medium and equipment | |
| JP2011204069A (en) | Testing method, and automatic test specification and test data generation apparatus | |
| CN113343659B (en) | Analysis report generation method, device, equipment and storage medium | |
| JP7127601B2 (en) | Similar Transition Identifying Device, Similar Transition Identifying Method, and Program | |
| US12001324B2 (en) | Operation pattern generation apparatus, operation pattern generation method and program | |
| CN114168477A (en) | Automatic generation and test method and device of use case, electronic equipment and readable medium |
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 |