CN115658463A - Use case management method and device, computer equipment and storage medium - Google Patents
Use case management method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN115658463A CN115658463A CN202211102091.0A CN202211102091A CN115658463A CN 115658463 A CN115658463 A CN 115658463A CN 202211102091 A CN202211102091 A CN 202211102091A CN 115658463 A CN115658463 A CN 115658463A
- Authority
- CN
- China
- Prior art keywords
- test
- case
- generating
- case test
- document
- 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
- 238000007726 management method Methods 0.000 title claims abstract description 48
- 238000012360 testing method Methods 0.000 claims abstract description 380
- 230000006870 function Effects 0.000 claims abstract description 86
- 238000000034 method Methods 0.000 claims abstract description 24
- 238000012795 verification Methods 0.000 claims description 28
- 238000004590 computer program Methods 0.000 claims description 13
- 238000006243 chemical reaction Methods 0.000 claims description 4
- 230000000694 effects Effects 0.000 abstract description 6
- 230000008569 process Effects 0.000 description 15
- 238000010606 normalization Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 238000011161 development Methods 0.000 description 3
- 230000008439 repair process Effects 0.000 description 3
- 230000007547 defect Effects 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000003631 expected effect Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 238000013522 software testing Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000013024 troubleshooting Methods 0.000 description 1
Images
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
- Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
- Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
- Y02P90/30—Computing systems specially adapted for manufacturing
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention relates to the technical field of system test, in particular to a case management method, a case management device, computer equipment and a storage medium, wherein the case management method comprises the following steps: acquiring a plurality of application functions to be tested, and generating corresponding function operation flow data according to each application function to be tested; generating case test document data according to each function operation flow data, and generating case batch test instructions according to the case test document data; acquiring a case test identifier corresponding to each case test document data, and acquiring a corresponding case actual test result and a corresponding case test expected result according to the case test identifier; and generating a case test report according to the actual case test result and the expected case test result of each case test identifier, and generating a report approval instruction according to the case test report. The method and the device have the effect of perfecting the test management of the application system software.
Description
Technical Field
The present invention relates to the field of system testing technologies, and in particular, to a method and an apparatus for case management, a computer device, and a storage medium.
Background
With the rapid development of computer technology, the software type is rapidly increased, the software requirement and the software service logic are more and more complex, the requirement on the function test management level of the application system software is also continuously improved, the traditional manual management seriously wastes labor cost and time cost, and high efficiency, standardization, normalization and process cannot be realized. The software testing system and the testing work are very important in the network environment, the continuous change of information forces the software function testing management level, tools, methods and the like of the application system to be rapidly updated, the third party of the informatization project accepts the test, the internal supervision and control are required to be accepted in the detection process, the detected problems are required to be confronted with the question from a trust unit or a development unit, and the system for disclosing the transparent testing result and the testing process is very important in the face of various stresses in the testing work, so that the supervision of internal and external personnel is facilitated, and the working efficiency of the testing personnel is improved.
At present, due to practical problems such as limited resources and the like, automatic test work cannot be effectively carried out in the traditional third-party acceptance test of the information project, only a manual test mode can be selected for function test, test software is divided into a plurality of parts and handed to different testers for taking charge, a function troubleshooting test system is sequentially used by manpower to find problems, test cases are recorded in a table in the test process, test execution results are recorded in the table, and after test results of all test items are collected, the test results are manually gathered and test reports are written. However, the testing efficiency of the testing process is low, and the problems of calculation error, data redundancy or data loss and the like are easy to occur when the testing data are summarized. The mode not only consumes a large amount of human resources and has low working efficiency, but also enables testers to check functional problems by experience, test execution results cannot be completely shared, and similar problems possibly existing in the system cannot be found. Meanwhile, test execution processes such as test case design, test plan design and test execution results are still managed in a document form, so that the test process is difficult to control, the test results cannot be directly analyzed, and the informatization management effect cannot be achieved. Therefore, it is very important to build a complete application system software function test case management system.
Disclosure of Invention
In order to perfect the test management of application system software, the application provides a use case management method, a device, computer equipment and a storage medium.
The above object of the present invention is achieved by the following technical solutions:
a use case management method comprises the following steps:
acquiring a plurality of application functions to be tested, and generating corresponding function operation flow data according to each application function to be tested;
generating case test document data according to each function operation flow data, and generating case batch test instructions according to the case test document data;
acquiring a case test identifier corresponding to each case test document data, and acquiring a corresponding case actual test result and a case test expected result according to the case test identifier;
and generating a case test report according to the actual case test result and the expected case test result of each case test identifier, and generating a report approval instruction according to the case test report.
By adopting the technical scheme, corresponding function operation flow data can be generated according to each application function to be tested in the system, so that corresponding use case test document data can be generated based on different software functions, and further, use case tests can be performed on each software function in the system in batches; after the case test results are obtained, the corresponding actual test results are obtained based on the case test identification of each case test document data, and are compared with the expected test results according to the actual test results, so that the case tests of the whole system can be automatically tested, the case tests can be uniformly managed on line, the repair of the tested results can be tracked and analyzed timely, and the management capability of the case tests of the application system is improved.
The application may be further configured in a preferred example to: the generating of case test document data according to each function operation flow data and the generating of case batch test instructions according to the case test document data specifically comprises:
according to the application function to be tested, performing normative verification on the case test document data;
and if the normative verification is passed, generating the use case batch test instruction.
By adopting the technical scheme, the normalization verification is carried out on the case test document data, and the normalization of the compilation of the case test document can be verified, so that the case test can be normally executed, and the problem that the test result is influenced because the document of the case test is not normalized is solved.
The present application may be further configured in a preferred example to: the step of performing normative verification on the case test document data according to the application function to be tested specifically comprises the following steps:
performing character recognition on each case test document data to obtain case test character data, and converting the case test character data into a to-be-converted document in an xml format;
acquiring interval characters from the document to be converted, acquiring test content classification data according to the interval characters, generating an Excel test document from the content classification data according to the functional operation flow data, and performing normalization verification on the Excel document.
By adopting the technical scheme, when a tester creates a case test document, the tester can create a corresponding case test document according to the requirements and habits of the tester, identify the content in the case test document in a character recognition mode, and convert the case test document into the document to be converted in the xml format, so that the content type can be identified by utilizing the space characters in the document in the xml format, and further the Excel test document is converted, and the test accuracy can be improved while the convenience of operation is improved for the tester.
The application may be further configured in a preferred example to: the generating a case test report according to the actual case test result and the expected case test result of each case test identifier, and generating a report approval instruction according to the case test report specifically includes:
comparing the actual test result corresponding to each case test identification with the expected result of case test, and generating a case execution state according to the comparison result;
and generating the case test report according to the case execution state.
By adopting the technical scheme, the result of the actual use case test and the expected result of the use case test are compared, so that the result of the actual test can be compared, whether the executed action accords with the expected effect when each function in the software system is executed can be compared, statistics is convenient, meanwhile, format conversion and verification are carried out on the data of the use case test document by combining the above steps, the difference between the number of the obtained actual test results and the number of the data of the use case test document can be made to be as small as possible, the test effect is improved, and management of the use case test is facilitated.
The application may be further configured in a preferred example to: the comparing the actual test result corresponding to each use case test identifier with the expected result of use case test, and generating a use case execution state according to the comparison result specifically includes:
judging whether the case test document data corresponding to each case test identification is executed or not, if so, recording the corresponding actual test result, and if not, generating a test failure state;
and generating the case execution state according to the comparison result and the test failure state.
By adopting the technical scheme, the case executing state can be generated together with the test failure state by judging whether the case side corresponding to the case test identification is the document to be executed, so that the case executing state is enriched, and the subsequent analysis and management are facilitated.
The second purpose of the invention of the application is realized by the following technical scheme:
a use case management apparatus, the use case management apparatus comprising:
the function flow acquisition module is used for acquiring a plurality of application functions to be tested and generating corresponding function operation flow data according to each application function to be tested;
the batch test module is used for generating case test document data according to each function operation flow data and generating case batch test instructions according to the case test document data;
the result acquisition module is used for acquiring a case test identifier corresponding to each case test document data and acquiring a corresponding case actual test result and a case test expected result according to the case test identifier;
and the result approval module is used for generating a case test report according to the actual case test result and the expected case test result of each case test identifier, and generating a report approval instruction according to the case test report.
By adopting the technical scheme, corresponding function operation flow data can be generated according to each application function to be tested in the system, so that corresponding use case test document data can be generated based on different software functions, and further, use case tests can be performed on each software function in the system in batches; after the case test results are obtained, the corresponding actual test results are obtained based on the case test identification of each case test document data, and are compared with the expected test results according to the actual test results, so that the case tests of the whole system can be automatically tested, the case tests can be uniformly managed on line, the repair of the tested results can be tracked and analyzed timely, and the management capability of the case tests of the application system is improved.
The third purpose of the present application is achieved by the following technical solutions:
a computer device comprises a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the steps of the use case management method when executing the computer program.
The fourth purpose of the present application is achieved by the following technical solutions:
a computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned use case management method.
In summary, the present application includes at least one of the following beneficial technical effects:
1. the corresponding function operation flow data can be generated according to each application function to be tested in the system, so that corresponding case test document data can be generated based on different software functions, and case tests can be performed on each software function in the system in batches;
2. after the case test result is obtained, the corresponding actual test result is obtained based on the case test identification of each case test document data, and is compared with the expected test result according to the actual test result, so that the case test of the whole system can be automatically tested, the case test can be uniformly managed on line, the repair of the tested result can be tracked and analyzed in time, and the management capability of the case test of the application system is improved;
3. the method has the advantages that when a tester creates the case test document, the corresponding case test document can be created according to the self requirement and habit, the content in the case test document is identified in a character identification mode and is converted into the document to be converted in the xml format, so that the content type can be identified by using the space characters in the document in the xml format, the document is further converted into the Excel test document, and the test accuracy can be improved while the convenience of operation is improved for the tester.
Drawings
FIG. 1 is a flow chart of a method of use case management in one embodiment of the present application;
FIG. 2 is a flowchart illustrating an implementation of step S20 in the case management method according to an embodiment of the present application;
FIG. 3 is a flowchart illustrating an implementation of step S21 in a case management method according to an embodiment of the present application;
FIG. 4 is a flowchart illustrating an implementation of step S40 in a case management method according to an embodiment of the present application;
FIG. 5 is a flowchart illustrating an implementation of step S41 in the case management method according to an embodiment of the present application;
FIG. 6 is a schematic block diagram of a use case management apparatus according to an embodiment of the present application;
fig. 7 is a schematic diagram of an apparatus in an embodiment of the present application.
Detailed Description
The present application is described in further detail below with reference to the attached drawings.
In an embodiment, as shown in fig. 1, the present application discloses a use case management method, which specifically includes the following steps:
s10: and acquiring a plurality of application functions to be tested, and generating corresponding function operation flow data according to each application function to be tested.
In this embodiment, the application function to be tested refers to a functional module whose performance needs to be tested in a software system. Functional operational flow data refers to the flow of data iterations in which the functional module processes data when executing.
Specifically, based on specific service requirements, when a software system is developed and needs to be tested, a functional module related to the software is obtained, where the functional module may be a module with a single function, such as a login module, or based on a certain service scenario, a plurality of functional units associated with each other are combined to form a functional module capable of implementing the service scenario, and the functional module obtained through statistics is used as an application function to be tested.
Further, after the application function to be tested is obtained, a data processing flow corresponding to each functional module is obtained, for example, for a login module, the data processing flow may be a flow for verifying a login account password after the login account password is obtained to determine whether login is possible, or based on a certain service scenario, a functional module composed of a plurality of functional units associated with each other, and the data processing flow may be a data processing flow between the functional units when each functional unit meets the requirements of the service scenario. And taking the flow of data processing obtained by statistics as functional operation flow data.
S20: and generating case test document data according to the operation flow data of each function, and generating case batch test instructions according to the case test document data.
Specifically, case test document data are generated based on function operation flow data corresponding to each application function to be tested, case batch test instructions are generated after case test document data corresponding to each application function to be tested are obtained, that is, all the case test document data are input into the software system, and data executed by the software system are recorded from a background code end.
S30: and acquiring a case test identifier corresponding to the data of each case test document, and acquiring a corresponding case actual test result and a case test expected result according to the case test identifier.
In this embodiment, the actual test result refers to the condition that the software system executes after each application function to be tested is tested. The expected result of the case test is the specific effect that each application function to be tested can realize in the software system.
Specifically, a corresponding use case test identifier is set for each piece of use case test document data, the execution state and the execution effect of the use case test identifier are tracked in real time according to the use case test identifier to serve as the actual test result of the use case, and the use case test expected result corresponding to the use case test identifier is obtained, wherein the use case test expected result can be input by related workers, and can also be automatically generated by identifying the application function to be tested.
S40: and generating a case test report according to the actual case test result and the expected case test result of each case test identifier, and generating a report approval instruction according to the case test report.
Specifically, a corresponding use case test report is generated according to the difference between the result shown by the actual use case test of each use case test identifier and the expected result of the corresponding use case test, the defect condition occurring in the system is obtained from the use case test report, and the report approval instruction is generated according to the defect condition.
In an embodiment, as shown in fig. 2, in step S20, that is, generating use case test document data according to each function operation flow data, and generating use case batch test instructions according to the use case test document data specifically include:
s21: and performing normative verification on the case test document data according to the application function to be tested.
Specifically, the case test document data corresponding to each application function to be tested is subjected to normative verification one by one, that is, whether the document data to be tested meets the corresponding template requirement is verified, that is, whether the document data to be tested can be identified by the test platform of the software system.
S22: and if the normative verification is passed, generating a case batch test instruction.
Specifically, the case test document data passing the normative verification is counted to generate the case batch test instruction.
In an embodiment, as shown in fig. 3, in step S21, according to the application function to be tested, performing a normative verification on the case test document data specifically includes:
s211: and performing character recognition on the document data of each case test to obtain case test character data, and converting the case test character data into a document to be converted in an xml format.
Specifically, after the relevant staff edit the corresponding force test document, the corresponding text is recognized from each case test document data in a text recognition mode, so as to obtain case test text data.
Further, using an xml format conversion tool to convert each case test text data into a document to be converted in an xml format.
S212: acquiring interval characters from a document to be converted, acquiring test content classification data according to the interval characters, generating an Excel test document from the content classification data according to the function operation flow data, and performing normative verification on the Excel document.
Specifically, in the document to be converted in the xml format, space characters for separating different characters, that is, space characters between each line of characters or each group of character strings in the use case test document data for representation in the xml document, are acquired.
Further, after the interval characters are obtained, characters between every two interval characters are used as content classification data, and the content classification data are filled to corresponding positions according to the Excel template document corresponding to the application function to be tested, so that the Excel test document is obtained.
Further, normative verification is carried out on the Excel test documents corresponding to different Excel templates, so that whether content is missing or wrong is verified.
In an embodiment, as shown in fig. 4, in step S40, generating a use case test report according to the actual test result of the use case identified by each use case test and the expected test result of the use case test, and generating a report approval instruction according to the use case test report specifically includes:
s41: and comparing the actual test result corresponding to each case test identification with the expected result of the case test, and generating a case execution state according to the comparison result.
In this embodiment, the use case execution state refers to operation feedback corresponding to each piece of use case test document data when the piece of use case test document data is input into the software system for testing.
Specifically, after the case test document data corresponding to each case test identifier is input into the software system for testing, the corresponding test result is obtained according to the case test identifier, that is, the operating state of the software system when the contents in the case test document data are operated is taken as the actual test result.
Furthermore, the actual test result is compared with the expected result of the corresponding use case test, and the comparison result is used as the execution state of the use case.
S42: and generating a case test report according to the case execution state.
Specifically, the case execution states are classified according to the corresponding case test identifications, and then the case test reports of the batch are obtained.
In an embodiment, as shown in fig. 5, in step S41, comparing the actual test result corresponding to each use case test identifier with the expected result of use case test, and generating a use case execution state according to the comparison result specifically includes:
s411: and judging whether the case test document data corresponding to each case test identification is executed, if so, recording a corresponding actual test result, and if not, generating a test failure state.
Specifically, in the process of case testing, if a serious bug or other problem occurs in the development of software functions, case testing document data cannot be executed, so that when each case testing document data is tested, whether the case testing document data is executed or not is judged first, if yes, the actual testing result is recorded, and if not, the testing fails.
S412: and generating a case execution state according to the comparison result and the test failure state.
Specifically, the comparison results of all actual test results and the corresponding expected test result quality checks of the use case test and the test failure state in the batch test instruction are counted as the execution state of the use case.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by functions and internal logic of the process, and should not constitute any limitation to the implementation process of the embodiments of the present application.
In an embodiment, a use case management apparatus is provided, and the use case management apparatus corresponds to the use case management method in the above embodiment one to one. As shown in fig. 6, the use case management apparatus includes a functional process acquisition module, a batch test module, a result acquisition module, and a result approval module. The functional modules are explained in detail as follows:
the function flow acquisition module is used for acquiring a plurality of application functions to be tested and generating corresponding function operation flow data according to each application function to be tested;
the batch test module is used for generating case test document data according to the operation flow data of each function and generating case batch test instructions according to the case test document data;
the result acquisition module is used for acquiring a case test identifier corresponding to the data of each case test document and acquiring a corresponding case actual test result and a case test expected result according to the case test identifier;
and the result approval module is used for generating a case test report according to the actual case test result and the expected case test result of each case test identifier, and generating a report approval instruction according to the case test report.
Optionally, the batch test module includes:
the document verification submodule is used for performing normative verification on the case test document data according to the application function to be tested;
and the batch execution submodule is used for generating a case batch test instruction if the normative verification is passed.
Optionally, the document verification sub-module includes:
the document conversion unit is used for carrying out character recognition on the data of each case test document to obtain case test character data and converting the case test character data into a document to be converted in an xml format;
the document checking unit is used for acquiring interval characters from the document to be converted, acquiring test content classification data according to the interval characters, generating an Excel test document from the content classification data according to the functional operation flow data, and performing normalization verification on the Excel document.
Optionally, the result approving module includes:
the result comparison submodule is used for comparing the actual test result corresponding to each case test identification with the case test expected result and generating a case execution state according to the comparison result;
and the report generation submodule is used for generating a case test report according to the case execution state.
Optionally, the result comparing module includes:
the execution judging unit is used for judging whether the case testing document data corresponding to each case testing mark is executed, if so, recording a corresponding actual testing result, and if not, generating a testing failing state;
and the state generating unit is used for generating a case execution state from the comparison result and the test failure state.
For specific limitations of the use case management device, reference may be made to the above limitations on the use case management method, which is not described herein again. The modules in the use case management apparatus may be implemented in whole or in part by software, hardware, and a combination thereof. The modules can be embedded in a hardware form or independent of a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, the internal structure of which may be as shown in fig. 7. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operating system and the computer program to run on the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a use case management method.
In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
acquiring a plurality of application functions to be tested, and generating corresponding function operation flow data according to each application function to be tested;
generating case test document data according to the operation flow data of each function, and generating case batch test instructions according to the case test document data;
acquiring a case test identifier corresponding to the data of each case test document, and acquiring a corresponding case actual test result and a case test expected result according to the case test identifier;
and generating a case test report according to the actual case test result and the expected case test result of each case test identifier, and generating a report approval instruction according to the case test report.
In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when executed by a processor, performs the steps of:
acquiring a plurality of application functions to be tested, and generating corresponding function operation flow data according to each application function to be tested;
generating case test document data according to the operation flow data of each function, and generating case batch test instructions according to the case test document data;
acquiring a case test identifier corresponding to the data of each case test document, and acquiring a corresponding case actual test result and a case test expected result according to the case test identifier;
and generating a case test report according to the actual case test result and the expected case test result of each case test identifier, and generating a report approval instruction according to the case test report.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can include non-volatile and/or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), rambus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
It should be clear to those skilled in the art that, for convenience and simplicity of description, the foregoing division of the functional units and modules is only used for illustration, and in practical applications, the above function distribution may be performed by different functional units and modules as needed, that is, the internal structure of the apparatus may be divided into different functional units or modules to perform all or part of the above described functions.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A use case management method is characterized by comprising the following steps:
acquiring a plurality of application functions to be tested, and generating corresponding function operation flow data according to each application function to be tested;
generating case test document data according to each function operation flow data, and generating case batch test instructions according to the case test document data;
acquiring a case test identifier corresponding to each case test document data, and acquiring a corresponding case actual test result and a corresponding case test expected result according to the case test identifier;
and generating a case test report according to the actual case test result and the expected case test result of each case test identifier, and generating a report approval instruction according to the case test report.
2. The use case management method according to claim 1, wherein the generating use case test document data according to each piece of function operation flow data and generating use case batch test instructions according to the use case test document data specifically includes:
according to the application function to be tested, performing normative verification on the case test document data;
and if the normative verification is passed, generating the use case batch test instruction.
3. The use case management method according to claim 2, wherein the performing a normative verification on the use case test document data according to the application function to be tested specifically includes:
performing character recognition on each case test document data to obtain case test character data, and converting the case test character data into a to-be-converted document in an xml format;
acquiring interval characters from the document to be converted, acquiring test content classification data according to the interval characters, generating an Excel test document from the content classification data according to the functional operation flow data, and performing normative verification on the Excel document.
4. The method for case management according to claim 1, wherein the generating a case test report according to the actual test result and the expected test result of the case of each case test identifier and generating a report approval instruction according to the case test report specifically includes:
comparing the actual test result corresponding to each case test identification with the expected result of the case test, and generating a case execution state according to the comparison result;
and generating the case test report according to the case execution state.
5. The method for managing use cases according to claim 4, wherein the comparing the actual test result corresponding to each use case test identifier with the expected result of use case test, and generating a use case execution state according to the comparison result specifically includes:
judging whether the case test document data corresponding to each case test identification is executed or not, if so, recording the corresponding actual test result, and if not, generating a test failure state;
and generating the case execution state according to the comparison result and the test failure state.
6. A use case management apparatus, comprising:
the function flow acquisition module is used for acquiring a plurality of application functions to be tested and generating corresponding function operation flow data according to each application function to be tested;
the batch test module is used for generating case test document data according to each function operation flow data and generating case batch test instructions according to the case test document data;
the result acquisition module is used for acquiring a case test identifier corresponding to each case test document data and acquiring a corresponding case actual test result and a case test expected result according to the case test identifier;
and the result approval module is used for generating a case test report according to the actual case test result and the expected case test result of each case test identifier, and generating a report approval instruction according to the case test report.
7. The use case management apparatus according to claim 6, wherein the batch test module includes:
the document verification submodule is used for performing normative verification on the case test document data according to the application function to be tested;
and the batch execution sub-module is used for generating the use case batch test instruction if the normative verification is passed.
8. The use case management device according to claim 6, wherein the document verification sub-module includes:
the document conversion unit is used for carrying out character recognition on each case test document data to obtain case test character data and converting the case test character data into a document to be converted in an xml format;
and the document verification unit is used for acquiring interval characters from the document to be converted, acquiring test content classification data according to the interval characters, generating an Excel test document from the content classification data according to the function operation flow data, and performing normative verification on the Excel document.
9. A computer device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the steps of the use case management method according to any one of claims 1 to 5 are implemented when the computer program is executed by the processor.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the steps of the use case management method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211102091.0A CN115658463A (en) | 2022-09-09 | 2022-09-09 | Use case management method and device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211102091.0A CN115658463A (en) | 2022-09-09 | 2022-09-09 | Use case management method and device, computer equipment and storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115658463A true CN115658463A (en) | 2023-01-31 |
Family
ID=84984351
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211102091.0A Pending CN115658463A (en) | 2022-09-09 | 2022-09-09 | Use case management method and device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115658463A (en) |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104484419A (en) * | 2014-12-17 | 2015-04-01 | 上海斐讯数据通信技术有限公司 | Test case document conversion system and test case document conversion method |
| US9111030B1 (en) * | 2008-10-03 | 2015-08-18 | Federal Home Loan Mortgage Corporation | Systems and methods for testing a software application |
| CN110941546A (en) * | 2019-10-12 | 2020-03-31 | 平安健康保险股份有限公司 | Automatic test method, device, equipment and storage medium for WEB page case |
| CN114780420A (en) * | 2022-04-28 | 2022-07-22 | 武汉思普崚技术有限公司 | Method, device, equipment and storage medium for automatic test based on test case |
-
2022
- 2022-09-09 CN CN202211102091.0A patent/CN115658463A/en active Pending
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9111030B1 (en) * | 2008-10-03 | 2015-08-18 | Federal Home Loan Mortgage Corporation | Systems and methods for testing a software application |
| CN104484419A (en) * | 2014-12-17 | 2015-04-01 | 上海斐讯数据通信技术有限公司 | Test case document conversion system and test case document conversion method |
| CN110941546A (en) * | 2019-10-12 | 2020-03-31 | 平安健康保险股份有限公司 | Automatic test method, device, equipment and storage medium for WEB page case |
| CN114780420A (en) * | 2022-04-28 | 2022-07-22 | 武汉思普崚技术有限公司 | Method, device, equipment and storage medium for automatic test based on test case |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107862327B (en) | Security defect identification system and method based on multiple features | |
| KR100898748B1 (en) | Testing method for software safety evaluation of train control system | |
| CN113282513B (en) | Interface test case generation method and device, computer equipment and storage medium | |
| CN113282514A (en) | Problem data processing method and device, computer equipment and storage medium | |
| CN113051180A (en) | Test task monitoring method, device, equipment and storage medium | |
| CN115952081A (en) | Software testing method, device, storage medium and equipment | |
| CN117421217A (en) | Automatic software function test method, system, terminal and medium | |
| CN115114064A (en) | Micro-service fault analysis method, system, equipment and storage medium | |
| CN117391306A (en) | Homeland space planning result examination method, device, equipment and storage medium | |
| CN117493188A (en) | Interface testing method and device, electronic equipment and storage medium | |
| JP2019194818A (en) | Software trouble prediction device | |
| Gao et al. | Research on software defect classification | |
| CN116662203A (en) | Test method, test device, computer equipment and storage medium | |
| CN115658463A (en) | Use case management method and device, computer equipment and storage medium | |
| CN115934559A (en) | Testing method of intelligent form testing system | |
| CN116627804A (en) | Test method, system, electronic equipment and storage medium based on artificial intelligence | |
| CN113535581B (en) | Test script generation method, device, equipment and computer readable storage medium | |
| Yan et al. | Revisiting the correlation between alerts and software defects: A case study on myfaces, camel, and cxf | |
| CN113886262A (en) | Software automation test method and device, computer equipment and storage medium | |
| CN113051582A (en) | Computer software technology development and debugging system | |
| CN113282496A (en) | Automatic interface test method, device, equipment and storage medium | |
| CN113176995A (en) | Interface testing method, device, equipment and medium based on testing scene | |
| CN114756217B (en) | Plug-in based script generation system | |
| Rexhepi et al. | Software testing techniques and principles | |
| CN113568831B (en) | Self-supervision deep learning type defect positioning method based on metamorphic test |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20230131 |
|
| RJ01 | Rejection of invention patent application after publication |