CN117234948A - Method for generating automatic use cases based on manual use cases - Google Patents
Method for generating automatic use cases based on manual use cases Download PDFInfo
- Publication number
- CN117234948A CN117234948A CN202311493750.2A CN202311493750A CN117234948A CN 117234948 A CN117234948 A CN 117234948A CN 202311493750 A CN202311493750 A CN 202311493750A CN 117234948 A CN117234948 A CN 117234948A
- Authority
- CN
- China
- Prior art keywords
- configuration
- use case
- automation
- list
- script
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 32
- 238000013515 script Methods 0.000 claims abstract description 58
- 238000012360 testing method Methods 0.000 claims abstract description 35
- 238000013519 translation Methods 0.000 claims abstract description 18
- 238000013507 mapping Methods 0.000 claims abstract description 15
- 238000006243 chemical reaction Methods 0.000 claims description 22
- 238000007689 inspection Methods 0.000 claims description 7
- 238000012545 processing Methods 0.000 claims description 7
- 230000009471 action Effects 0.000 claims description 6
- 230000006870 function Effects 0.000 description 15
- 230000005540 biological transmission Effects 0.000 description 4
- 102100033189 Diablo IAP-binding mitochondrial protein Human genes 0.000 description 3
- 101710101225 Diablo IAP-binding mitochondrial protein Proteins 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 101150098958 CMD1 gene Proteins 0.000 description 2
- 101100382321 Caenorhabditis elegans cal-1 gene Proteins 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000003672 processing method Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000000605 extraction Methods 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000011084 recovery Methods 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
- 238000012956 testing procedure Methods 0.000 description 1
- 238000012546 transfer Methods 0.000 description 1
- 230000001960 triggered effect Effects 0.000 description 1
- 238000011144 upstream manufacturing Methods 0.000 description 1
Classifications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention provides a method for generating an automatic use case based on a manual use case, which comprises the following steps: dividing the manual use case into a plurality of use case steps; respectively acquiring keywords and instructions of the multiple use case steps; matching the keywords to a translation mapping list to obtain a parameter format corresponding to the keywords; generating an automation command of the use case step based on the parameter format and the instruction; integrating the automation commands of the multiple use case steps to obtain an automation use case script and a configuration command file; the automation use case script comprises an automation configuration script and an automation pre-configuration script; the automatic test script can be generated immediately after the manual case writing is completed without the case writing personnel to learn complex programming languages, so that the testers can conveniently and rapidly conduct iterative product testing.
Description
Technical Field
The invention relates to the technical field of network equipment and chips, in particular to a method for generating an automatic use case based on a manual use case.
Background
Automated testing in chip testing is an important part of the overall testing effort, with several advantages over manual testing, including: efficiency is improved, cost is saved, test is repeated, expandability is improved, test coverage rate is improved, and the like. Although automated testing has many advantages, there are some disadvantages, firstly, it is difficult to write automated test scripts, the difficulty of a common tester to get up is high, and secondly, the speed of writing automated scripts is very slow compared with the speed of writing manual cases. Because the iteration update of the product is fast, the update change speed of the manual use case is faster and faster, and because two defects of automatic writing cause that many products needing quick iteration test do not have enough manpower and time to write the automatic use case, only manual test can be selected, thereby causing the problems that the test efficiency is low, the quick coverage in version iteration is not realized, and the release quality of the products cannot be ensured.
In view of the above, the invention provides a method for generating an automatic use case based on manual use case, which generates an automatic test script by innovatively translating the manual use case, does not require use case writers to learn complex programming languages, can immediately generate the automatic test script after the manual use case is written, and is convenient for testers to quickly carry out iterative testing on products.
Disclosure of Invention
The invention aims to provide a method for generating an automatic use case based on a manual use case, which comprises the following steps: dividing the manual use case into a plurality of use case steps; respectively acquiring keywords and instructions of the multiple use case steps; matching the keywords to a translation mapping list to obtain a parameter format corresponding to the keywords; generating an automation command of the use case step based on the parameter format and the instruction; integrating the automation commands of the multiple use case steps to obtain an automation use case script and a configuration command file; the automation use case scripts include an automation configuration script and an automation pre-configuration script.
Further, the method further comprises classifying the use case steps based on configuration and expectation of the use case steps to obtain a configuration item list and a pre-configuration item list.
Further, for the configuration entry list, obtaining the automation configuration script includes: obtaining keywords and instructions of a plurality of use case steps in the configuration item list to obtain a configuration conversion information list; based on the configuration conversion information list, circularly calling the translation mapping list to obtain a parameter format corresponding to the keyword; and respectively converting the instructions in the configuration conversion information list based on the corresponding parameter formats to obtain the automatic configuration script.
Further, the key words of the case steps in the configuration entry list are configuration, and the configuration command of the case steps is a call issuing configuration function, and the command needing to issue configuration is issued to the connection object of the corresponding device to be tested.
Further, the key words of the case steps in the configuration item list are echo configuration, the configuration command of the case steps is a call issuing configuration function, and after the configuration command is issued, the corresponding echo is acquired to judge whether the echo is matched with the expected value.
Further, the keywords of the use case step in the configuration item list also comprise streaming; the streaming includes creating a stream, sending the stream, and stream inspection.
Further, the step of creating the flow includes the flow name, the port of the flow to be sent, the header of the flow and the value of the field; the example steps of the sending flow comprise sending actions, sending speed and sending modes; the use case step of the flow check includes a flow check tag and an expected result.
Further, for the preconfiguration entry list, obtaining the automation preconfiguration script includes: processing the instruction of the use case step in the preconfigured entry list to obtain variable information; extracting the keywords and the variable information to obtain a plurality of pre-configuration conversion information lists; based on the pre-configuration conversion information list, circularly calling the translation mapping list to obtain a parameter format corresponding to the keyword; and respectively converting the variable information in the preconfigured conversion information list based on the corresponding parameter format to obtain the automatic preconfigured script.
Further, the method further comprises the step of storing the preconfiguration command of the use case step in the preconfiguration entry list into a step corresponding to an excel file to obtain the configuration command file; the pre-configuration command comprises a step number of a use case step and the variable information.
Further, the method further comprises the steps of marking test remarks into the automation case script, and writing library files required by executing the automation case script and pre-execution steps of the manual case into the automation case script.
The technical scheme of the embodiment of the invention has at least the following advantages and beneficial effects:
the method for generating the automatic case based on the manual case does not need a tester to have a code work bottom and a test platform script to use the work bottom, after the automatic test case is generated, the test case is graphically executed, so that the time for developing the automatic script can be saved, the missing of the test or the test redundancy can be avoided, and the purpose of improving the efficiency of writing the automatic test script case is realized. The invention can realize the rapid translation of the manual use case into the automatic test script so as to realize the automatic test in the version of rapid iteration.
Drawings
FIG. 1 is an exemplary flow chart of a method for generating an automated use case based on a manual use case, provided by some embodiments of the invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. The components of the embodiments of the present invention generally described and illustrated in the figures herein may be arranged and designed in a wide variety of different configurations.
FIG. 1 is an exemplary flow chart of a method for generating an automated use case based on a manual use case, provided by some embodiments of the invention. As shown in fig. 1, the process 100 includes the following:
step 110, decomposing the manual use case into a plurality of use case steps.
Manual use cases may refer to manually performed test steps and test data. For example, the manual use case may include the steps of testing, expected results, actual results, and the like. In some embodiments, the manual use cases may be written according to the requirements documentation and design specifications. Use case steps may refer to a series of instructions or operational flows when performing a software test. In some embodiments, the division may be based on a manual use case testing procedure, resulting in multiple use case procedures.
Step 120, obtaining the keywords and instructions of the multiple use case steps respectively.
Keywords may be used to indicate the operation of the use case step. For example, the keywords may include "configuration" and "tester send message" and the like; the configuration can be subdivided into fine classifications of 'configuration issuing', 'echo matching', 'echo non-matching', 'echo sequence matching', 'keyword equality', and the like; the "tester send message" can be subdivided into "streaming", "stop streaming" and "stream check", etc. An instruction may refer to a command to be issued. For example, describing the "configuration" class, a configuration instruction needs to be issued to a device under test, and first, in this use case step, the configuration instruction is written in a manner of < key > + instruction, and illustratively, the manual use case is written as follows, where < configuration > is a key, and the rest is an instruction that needs to be issued:
step 1< configuration ]
vlan
vlan 100,200 ports {port1},{port2}
In some embodiments, the keywords in the use case step may be captured by automatic translation software.
And 130, matching the keywords to a translation mapping list to obtain a parameter format corresponding to the keywords.
The translation map list refers to a list of saved keywords and their parameter formats. The parameter format refers to the processing method for the keyword. In some embodiments, the keywords of the manual use case may be captured, so as to obtain a plurality of keywords and operations corresponding to each keyword; based on the operation corresponding to each keyword, a parameter format of each keyword is made; and storing the keywords and the parameter formats corresponding to the keywords in a list to obtain a translation mapping list. In some embodiments, the keywords may be coarsely classified according to the testing steps of the manual case, and then finely classified. For example, the steps of manual testing of the data communication chip are generally classified into configuration issuing, back display processing, streaming of the tester, capturing of the tester, and the like, and after coarse classification is completed, fine classification is performed, for example, the "configuration" class may be subdivided into the fine classification of "configuration issuing", "back display matching", "back display non-matching", "back display sequence matching", "keyword equality", and the like, and the "tester sending message" class may be subdivided into the fine classification of "streaming", "stopping streaming", "streaming inspection", and the like, thereby defining all the fine classification to form a translation mapping list.
In some embodiments, the translation map list may be looked up based on keywords, resulting in a parameter format.
And 140, generating an automation command of the use case step based on the parameter format and the instruction.
The automation command may refer to an automation use case of the use case step. For example, the keyword is "configuration", the translation software reads that the keyword of the use case step is "configuration", and searches in the translation mapping table defined by the software, and the processing method of the keyword is used for collecting and processing the instruction and converting the instruction into the corresponding automation use case instruction.
Step 150, integrating the automation commands of the multiple use case steps to obtain an automation use case script and a configuration command file; the automation use case scripts include an automation configuration script and an automation pre-configuration script. For example, when processing a < configuration > class key, a "vlan" has been set in the pre-configuration phase
vlan 100,200 ports { port1}, { port2} "these instructions that need to be issued are saved into excel (i.e., the configuration command file).
An automation use case script may refer to a program for automatically testing software. The configuration command file may be used to hold instructions that need to be issued. For example, in a command match entry, the < configuration > key will find the config_send function in the mapping table, which will convert it to an automation script "$ { back } DUT_set_config $ { cmd1} $ { ser }, according to the method of the config_send function. Similar to the automatic case for generating the configuration, other classification rules are also written in the manual case steps according to the regulations, so that a manual case writing specification is formed, and the automatic translation software can normally identify keywords and parameters and translate the keywords and parameters into an automatic script as long as the manual case writing specification is written in a specification format.
An automation configuration script may be used to process specific actions that need to be performed by a configuration command. The automatic pre-configuration script can be used for storing the pre-configuration command to be issued by the corresponding variable, and storing the pre-configuration command in the step corresponding to the excel file. In some embodiments, classifying the use case steps based on configuration and expectation of the use case steps results in a list of configuration entries and a list of pre-configuration entries. The list of configuration entries may be a list of steps consisting of configuration class commands. The list of preconfigured entries may be a list of steps consisting of preconfigured class commands. The pre-configuration class command may include a configuration class command and a callback processing command. For example, the configuration step in the manual use case is performed through the pre-configuration process, the command and the echo information required by the configuration are collected, and the command and the echo information are stored in excel according to a specified format.
In some embodiments, for the list of configuration entries, deriving the automation configuration script includes: obtaining keywords and instructions of a plurality of use case steps in the configuration item list to obtain a configuration conversion information list; based on the configuration conversion information list, circularly calling the translation mapping list to obtain a parameter format corresponding to the keyword; and respectively converting the instructions in the configuration conversion information list based on the corresponding parameter formats to obtain the automatic configuration script.
The configuration conversion information list may refer to a list storing correspondence of keywords of use case steps and instructions thereof in the configuration entry list. In some embodiments, the key of the use case step in the configuration entry list may be "configuration", and the configuration command of the use case step is a call to issue a configuration function, and issues a command to issue the configuration to a connection object of the corresponding device to be tested. In other embodiments, the key of the use case step in the configuration entry list may be "echo configuration", where the configuration command of the use case step is a call to issue a configuration function, and after issuing the configuration command, the corresponding echo is acquired to determine whether the echo matches the expected value. Each of the different keywords invokes a different function to generate a corresponding automation command, thereby converting the configuration command into a corresponding automation script command. The relevant code flow is referred to as an automatic preconfigured script part, and will not be described herein.
In some embodiments, the keywords of the use case step in the configuration entry list further include streaming; the streaming includes creating a stream, sending the stream, and stream inspection.
For creating a stream, an exact desired stream can be created by a use case sentence for creating a stream, specifying the stream name, the port on which the stream needs to be sent, the header of the stream, and the value of the field. To freely create streams of arbitrary network protocols and fields in a more convenient way. For example, the name, port, and parameters of the flow to be created are fetched through regular expressions and converted into sentences of an automation script to call the underlying library functions, converted into a code format conforming to the created flow of the python interface of the tester, and the tester is operated to generate the flow. Illustratively, (1) step command: triggering is performed in the step by the keyword of the "< streaming >" word, which indicates that streaming is required in the step, and the label can include a streaming establishment part and a streaming transmission part. (2) The stream creation format is that a stream is created by a row included in a middle bracket "[ ]", the name of the stream needs to be specified in the middle bracket, the port of the stream is created, the header of the stream (included in brackets), and the field parameters of the created message are connected by "=".
Examples:
[name=stream1,port=port1,header=(eth ipv4),smac=00:00:00:00:00:01]
if multiple streams need to be created, the brackets include the stream content in the new line
Examples:
[name=stream1,port=port1,header=(eth ipv4),smac=00:00:00:00:00:01]
[name=stream2,port=port1,header=(eth ipv4),smac=00:00:00:00:00:02]
for the transmission stream, a stream to be transmitted may be specified by one send statement, and the speed and transmission mode may be specified. For example, the usage method of the transmission stream is: streaming format: the row included in the brackets "{ }" indicates a streaming action, and the name of the stream to be typed (corresponding to the created stream, the name of the stream included in the brackets), and parameters such as mode, speed, etc. are designated after the action is typed.
Examples:
{send:(stream1),time=30,speed_per=90}
for stream inspection, an upstream inspection tag may be written in the step, the desired result may be judged by writing the desired result in the stream inspection tag among the desired results, and the results may be arbitrarily logically combined. For example, the method of use includes: (1) expected outcome command: triggering by using a keyword of a "< stream check >" word in the step, indicating that the streaming result needs to be judged in the step, and not writing other contents under the label in the step; (2) expected format: the row included in the parenthesis "{ }" indicates the judgment of one streaming action, triggered in the expectation by the word < streaming check >, and the parenthesis needs to write the expected result when checking.
Examples:
{port1_txpkts==port2_rxpkts}
for multiple judgment conditions, commas can be used for separation in brackets, or a row can be put in another bracket
Examples:
{port1_txpkts==port2_rxpkts,port1_txpkts!=0}
or (b)
{port1_txpkts==port2_rxpkts}
{port1_txpkts!=0}
The judgment condition may use a python function
Such as
{int(port1_txpkts/port2_rxpkts)==0}
Or (b)
{round(port1_txpkts/port2_rxpkts)==0}
In some embodiments, for the list of preconfigured entries, deriving the automated preconfigured script includes: processing the instruction of the use case step in the preconfigured entry list to obtain variable information; extracting the keywords and the variable information to obtain a plurality of pre-configuration conversion information lists; based on the pre-configuration conversion information list, circularly calling the translation mapping list to obtain a parameter format corresponding to the keyword; and respectively converting the variable information in the preconfigured conversion information list based on the corresponding parameter format to obtain the automatic preconfigured script.
The variable information may include key information in use case steps. In some embodiments, key information of the instruction in the use case step may be extracted and packaged into variables to obtain variable information. The preconfigured conversion information list may refer to a list storing correspondence and contents of keywords of a plurality of use case steps and variable information thereof in the preconfigured entry list. For the pre-configuration command, the translated keywords can comprise configuration, echo matching, echo keywords, recovery and the like, and the keywords have the common property of issuing corresponding instructions to the device to be tested.
For example, the actual application flow for obtaining the automated pre-configuration script may be: the get_list_stepnum function obtains all step numbers of the use case, returns the step numbers to a list (i.e., a list of preconfigured entries) to be saved, for example, returns [ 'step 1', 'step 2', 'step 3' ]; the Trans_step_info_list_temp function adds the same steps of configuration and expectations to one list through the obtained step list, e.g., put one list for step 1, put a second list for step two, and so on to obtain all steps for the use case; the Trans_pre_config_info_list function imports the Trans_step_info_list_temp integrated list, calls Trans_pre_config_info for keyword extraction, returns a custom list (i.e., a pre-configured conversion information list), such as [ { ' configuration ' [ [ (' $ { cmd1} ', ' $ { cmd1_fed }) ], ' QOS ', [ (' step 1', ' step 1_fed ') ], ' TC_L2_001.0.01' ], [ (' $ { cmd1_1} ', ' $ { cmd1_1_fed ') ], ' QOS ' ], ' and [ (step 1_1_fed ') ] ], ' TC_L2_001.0.01' ], which is used by the pre-configured conversion function; the output_pre_config function loops to call the translation mapping table, fetches the keys and values of the dictionary for incoming tran_list, and gives them to the final transfer function execution, thus generating a pre-configuration file (i.e., an automated pre-configuration script).
The pre-configuration command translation module may generate a pre-configuration command and a configuration command file. In some embodiments, the method further includes storing the preconfiguration command of the use case step in the preconfiguration entry list in a step corresponding to an excel file, so as to obtain the configuration command file; the pre-configuration command comprises a step number of a use case step and the variable information. For example, the whole automation comprises a running control script, a command file which needs to be issued in a step and the like, and the command file is stored in excel according to a use case number and a step number, so that information such as an excel reading configuration command, a back display and the like can be conveniently called when the script runs. When the automation use case is operated, the method can be executed according to the steps, and when the configuration is required to be issued when the automation use case is operated, the instruction required to be issued by the steps is read from excel.
In some embodiments, the method further comprises marking test remarks into the automation case script, and writing library files required for executing the automation case script and pre-execution steps of the manual case into the automation case script. The test remarks may include test priority and module name, etc.
The above is only a preferred embodiment of the present invention, and is not intended to limit the present invention, but various modifications and variations can be made to the present invention by those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims (10)
1. A method for generating an automated use case based on a manual use case, comprising:
dividing the manual use case into a plurality of use case steps;
respectively acquiring keywords and instructions of the multiple use case steps;
matching the keywords to a translation mapping list to obtain a parameter format corresponding to the keywords;
generating an automation command of the use case step based on the parameter format and the instruction;
integrating the automation commands of the multiple use case steps to obtain an automation use case script and a configuration command file; the automation use case scripts include an automation configuration script and an automation pre-configuration script.
2. The method of generating automated use cases based on manual use cases of claim 1, further comprising classifying the use case steps based on configuration and expectation of the use case steps to obtain a list of configuration entries and a list of pre-configuration entries.
3. The method for generating an automation use case based on a manual use case of claim 2, wherein obtaining the automation configuration script for the list of configuration entries comprises:
obtaining keywords and instructions of a plurality of use case steps in the configuration item list to obtain a configuration conversion information list;
based on the configuration conversion information list, circularly calling the translation mapping list to obtain a parameter format corresponding to the keyword;
and respectively converting the instructions in the configuration conversion information list based on the corresponding parameter formats to obtain the automatic configuration script.
4. The method for generating an automated use case based on a manual use case according to claim 3, wherein the key words of the use case step in the configuration entry list are configuration, and the configuration command of the use case step is a call to issue a configuration function, and issues the command to issue the configuration to the connection object of the corresponding device to be tested.
5. The method for generating an automated use case based on a manual use case according to claim 3, wherein the key words of the use case step in the configuration item list are echo configuration, the configuration command of the use case step is a call issue configuration function, and after issuing the configuration command, the corresponding echo is acquired to determine whether the echo matches with the expected value.
6. The method for generating automated use cases based on manual use cases according to claim 3, wherein the keywords of use case steps in the configuration entry list further comprise streaming; the streaming includes creating a stream, sending the stream, and stream inspection.
7. The method for generating an automated use case based on a manual use case of claim 6, wherein the step of creating a stream comprises values of a stream name, a port on which the stream is to be sent, a header of the stream, and a field;
the example steps of the sending flow comprise sending actions, sending speed and sending modes;
the use case step of the flow check includes a flow check tag and an expected result.
8. The method for generating an automated use case based on a manual use case of claim 2, wherein obtaining the automated pre-configuration script for the list of pre-configuration entries comprises:
processing the instruction of the use case step in the preconfigured entry list to obtain variable information;
extracting the keywords and the variable information to obtain a plurality of pre-configuration conversion information lists;
based on the pre-configuration conversion information list, circularly calling the translation mapping list to obtain a parameter format corresponding to the keyword;
and respectively converting the variable information in the preconfigured conversion information list based on the corresponding parameter format to obtain the automatic preconfigured script.
9. The method for generating an automation case based on a manual case according to claim 8, further comprising storing a preconfiguration command of a case step in the preconfiguration entry list in a step corresponding to an excel file to obtain the configuration command file; the pre-configuration command comprises a step number of a use case step and the variable information.
10. The method of generating an automation case based on a manual case of claim 1, further comprising marking test remarks into the automation case script and writing library files required to execute the automation case script and pre-execution steps of the manual case into the automation case script.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311493750.2A CN117234948B (en) | 2023-11-10 | 2023-11-10 | Method for generating automatic use cases based on manual use cases |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311493750.2A CN117234948B (en) | 2023-11-10 | 2023-11-10 | Method for generating automatic use cases based on manual use cases |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN117234948A true CN117234948A (en) | 2023-12-15 |
| CN117234948B CN117234948B (en) | 2024-01-23 |
Family
ID=89098603
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311493750.2A Active CN117234948B (en) | 2023-11-10 | 2023-11-10 | Method for generating automatic use cases based on manual use cases |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117234948B (en) |
Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102135938A (en) * | 2011-03-21 | 2011-07-27 | 中国工商银行股份有限公司 | Software product testing method and system |
| CN104484269A (en) * | 2014-11-27 | 2015-04-01 | 北京广利核系统工程有限公司 | Method for automatically generating testing script |
| US20160188437A1 (en) * | 2013-03-15 | 2016-06-30 | International Business Machines Corporation | Testing functional correctness and idempotence of software automation scripts |
| CN106649106A (en) * | 2016-12-09 | 2017-05-10 | 北京锐安科技有限公司 | Test case generation method and device |
| CN109446059A (en) * | 2018-09-12 | 2019-03-08 | 北京邮电大学 | The generation method and device of test template script |
| CN111581090A (en) * | 2020-04-30 | 2020-08-25 | 重庆富民银行股份有限公司 | Automatic test case generation method and system based on NLP and RF framework |
| CN112948264A (en) * | 2021-03-30 | 2021-06-11 | 完美世界(重庆)互动科技有限公司 | Test task execution method, device, system, storage medium and electronic device |
| US20220100159A1 (en) * | 2020-09-29 | 2022-03-31 | Rockwell Automation Technologies, Inc. | Application code manager and intellicenter integration |
| US20220121807A1 (en) * | 2020-10-16 | 2022-04-21 | Bioinventors & Entrepreneurs Network, Llc | Programmatic Creation of Dynamically Configured, Hierarchically Organized Hyperlinked XML Documents For Presenting Data and Domain Knowledge From Diverse Sources |
| CN116431517A (en) * | 2023-04-26 | 2023-07-14 | 深圳证券通信有限公司 | Intelligent keyword prompting method and device for automatic test platform |
-
2023
- 2023-11-10 CN CN202311493750.2A patent/CN117234948B/en active Active
Patent Citations (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102135938A (en) * | 2011-03-21 | 2011-07-27 | 中国工商银行股份有限公司 | Software product testing method and system |
| US20160188437A1 (en) * | 2013-03-15 | 2016-06-30 | International Business Machines Corporation | Testing functional correctness and idempotence of software automation scripts |
| CN104484269A (en) * | 2014-11-27 | 2015-04-01 | 北京广利核系统工程有限公司 | Method for automatically generating testing script |
| CN106649106A (en) * | 2016-12-09 | 2017-05-10 | 北京锐安科技有限公司 | Test case generation method and device |
| CN109446059A (en) * | 2018-09-12 | 2019-03-08 | 北京邮电大学 | The generation method and device of test template script |
| CN111581090A (en) * | 2020-04-30 | 2020-08-25 | 重庆富民银行股份有限公司 | Automatic test case generation method and system based on NLP and RF framework |
| US20220100159A1 (en) * | 2020-09-29 | 2022-03-31 | Rockwell Automation Technologies, Inc. | Application code manager and intellicenter integration |
| US20220121807A1 (en) * | 2020-10-16 | 2022-04-21 | Bioinventors & Entrepreneurs Network, Llc | Programmatic Creation of Dynamically Configured, Hierarchically Organized Hyperlinked XML Documents For Presenting Data and Domain Knowledge From Diverse Sources |
| CN112948264A (en) * | 2021-03-30 | 2021-06-11 | 完美世界(重庆)互动科技有限公司 | Test task execution method, device, system, storage medium and electronic device |
| CN116431517A (en) * | 2023-04-26 | 2023-07-14 | 深圳证券通信有限公司 | Intelligent keyword prompting method and device for automatic test platform |
Non-Patent Citations (3)
| Title |
|---|
| REFAT OTHMAN 等: "Test Case Auto-Generation For Web Applications: A Model-Based Approach", 《2022 INTERNATIONAL SYMPOSIUM ON MULTIDISCIPLINARY STUDIES AND INNOVATIVE TECHNOLOGIES (ISMSIT)》, pages 18 - 25 * |
| 彭洪超: "基于Android系统的自动化测试用例的实现和优化", 《中国优秀硕士学位论文全文数据库 信息科技辑》, pages 138 - 399 * |
| 王正兵: "大型软件公司极速全量验证平台的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》, pages 138 - 212 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN117234948B (en) | 2024-01-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109522225B (en) | Automatic test assertion method and device, test platform and storage medium | |
| CN100512163C (en) | Device and method for forming topological map and detecting topological structure | |
| US10261967B2 (en) | Data extraction | |
| US20130125098A1 (en) | Transformation of Computer Programs | |
| US20060156137A1 (en) | Test program set generation tool | |
| CN104391796B (en) | A kind of test case analytic method | |
| CN111124892A (en) | Automatic testing method and system based on command line | |
| CN114173355B (en) | Method and system for dynamically executing network instruction with separated design running states | |
| JP2010140408A (en) | Source code converting device | |
| CN114692532A (en) | Chip system integration method and device and computer readable storage medium | |
| CN117234948B (en) | Method for generating automatic use cases based on manual use cases | |
| CN114443466A (en) | Method for converting executable script by using case file, terminal equipment and storage medium | |
| CN111797618A (en) | Log analysis method and device based on syntax tree analysis | |
| CN117194255A (en) | Test data maintenance method, device, equipment and storage medium | |
| JP2010140407A (en) | Source code inspection device | |
| CN108521350A (en) | A kind of industrial gateway equipment automatization test method driving script based on XML | |
| CN113312485B (en) | Log automatic classification method and device and computer readable storage medium | |
| CN109471637A (en) | The examination script debugging method of circuit diagram | |
| CN109240926A (en) | A kind of software compatibility system safety testing device and method | |
| CN108803561A (en) | The program automatic check method and system of program are controlled for white body wire body | |
| CN112559339A (en) | Automatic test verification method based on data template engine and test system thereof | |
| CN111176993A (en) | Code static detection method based on abstract syntax tree | |
| US9342500B2 (en) | Object memory management system | |
| JPH06195216A (en) | Automatic generation device for verification program | |
| CN116795685A (en) | Verilog code defect detection method and 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |