CN112015658A - Method and device for generating software integration test case - Google Patents
Method and device for generating software integration test case Download PDFInfo
- Publication number
- CN112015658A CN112015658A CN202010911948.8A CN202010911948A CN112015658A CN 112015658 A CN112015658 A CN 112015658A CN 202010911948 A CN202010911948 A CN 202010911948A CN 112015658 A CN112015658 A CN 112015658A
- Authority
- CN
- China
- Prior art keywords
- interface
- relation table
- software
- interface relation
- test case
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 103
- 238000000034 method Methods 0.000 title claims abstract description 49
- 230000010354 integration Effects 0.000 title claims abstract description 45
- 238000013461 design Methods 0.000 claims abstract description 77
- 230000007547 defect Effects 0.000 claims abstract description 65
- 238000004590 computer program Methods 0.000 claims description 14
- 238000004458 analytical method Methods 0.000 claims description 5
- 230000002950 deficient Effects 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 230000003287 optical effect Effects 0.000 description 3
- 238000005516 engineering process Methods 0.000 description 2
- 238000004880 explosion Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 239000000047 product Substances 0.000 description 1
- 238000013522 software testing Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
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
Abstract
The invention discloses a method and a device for generating a software integration test case, which relate to the technical field of signal system product software test, check the correctness of a software summary design description in advance, and then automatically generate the test case by utilizing an interface relation contained in the software summary design description, thereby ensuring the test integrity and correctness of a software interface, wherein the main technical scheme of the invention is as follows: acquiring a software outline design description and a corresponding target source code thereof; analyzing the software summary design description and the target source code respectively to obtain a first interface relation table corresponding to the software summary design description and a second interface relation table corresponding to the target source code; judging whether the first interface relation table has defects or not by utilizing the second interface relation table; and if not, generating a test case for software integration by using the first interface relation table. The method and the device are applied to generating the test case for the interface test.
Description
Technical Field
The invention relates to the technical field of software testing of signal system products, in particular to a method and a device for generating a software integration test case.
Background
Software integration test, also called assembly test or joint test. On the basis of unit testing, all modules are assembled into a subsystem or a system according to design requirements, and integrated testing is performed. Practice shows that some modules can work independently, but the connection cannot be guaranteed to work normally. Some problems that are not reflected locally are likely to be revealed globally.
Currently, the main purpose of software integration testing is to verify the correctness and integrity of software module interfaces. The traditional test case design method is mainly characterized in that interfaces between modules are screened out according to software outline design description, then reasonable module layers are analyzed and worked out layer by layer according to the layer calling relation between the modules, and cases are designed according to the traditional software integration test case design method (such as top-down, bottom-up and large explosion).
However, the software summary design description provided by the developer often has the situations of simple interface description and incomplete reference or call between interfaces, if the test case is completely designed according to the software summary design description, the interface test design is lacked, and the obtained existing test case also misses/wrongly tests the interface relationship of the module.
Disclosure of Invention
In view of this, the present invention provides a method and an apparatus for generating a software integration test case, and the main purpose of the present invention is to check the correctness of the software summary design description in advance, and then automatically generate a test case by using the interface relationship included in the software summary design description, so as to ensure the integrity and correctness of the software interface test.
In order to solve the above problems, the present invention mainly provides the following technical solutions:
in a first aspect, the present invention provides a method for generating a software integration test case, where the method includes:
acquiring a software outline design description and a corresponding target source code thereof;
analyzing the software summary design description and the target source code respectively to obtain a first interface relation table corresponding to the software summary design description and a second interface relation table corresponding to the target source code;
judging whether the first interface relation table has defects or not by utilizing the second interface relation table;
and if not, generating a test case for software integration by using the first interface relation table.
Optionally, the determining, by using the second interface relationship table, whether the first interface relationship table has a defect includes:
judging whether the first interface relation table is consistent with the second interface relation table or not;
if not, judging whether the interfaces existing among the modules recorded by the first interface relation table and the association existing among the interfaces are contained in the second interface relation table or not;
if not, determining that the first interface relation table has defects.
Optionally, the generating a test case for software integration by using the first interface relationship table includes:
presetting test case generation strategies, wherein each generation strategy corresponds to a packaged script file;
and when a target generation strategy appointed by a user is received, calling a script file corresponding to the target generation strategy, importing the first interface relation table and generating a corresponding test case according to the target generation strategy.
Optionally, if it is determined that the first interface relationship table has a defect, the method further includes:
marking the defects and displaying characteristics;
and displaying and outputting a checking report according to the defects and the characteristics, and submitting defect management.
In a second aspect, the present invention further provides an apparatus for generating a software integration test case, where the apparatus includes:
the acquisition unit is used for acquiring the software outline design description and the corresponding target source code;
the analysis unit is used for respectively analyzing the software summary design description acquired by the acquisition unit and the target source code acquired by the acquisition unit to obtain a first interface relation table corresponding to the software summary design description and a second interface relation table corresponding to the target source code;
the judging unit is used for judging whether the first interface relation table obtained by the analyzing unit has defects or not by utilizing the second interface relation table obtained by the analyzing unit;
and the generating unit is used for generating a test case for software integration by using the first interface relation table when the judging unit judges that the first interface relation table has no defects.
Optionally, the determining unit includes:
the first judging module is used for judging whether the first interface relation table is consistent with the second interface relation table or not;
a second judging module, configured to, when the first judging module judges that the first interface relationship table is not consistent with the second interface relationship table, judge whether interfaces existing between modules recorded in the first interface relationship table and associations existing between the interfaces are included in the second interface relationship table;
and the determining module is used for judging that the first interface relation table has defects when determining that the interfaces existing among the modules recorded by the first interface relation table and the associations existing among the interfaces are not contained in the second interface relation table.
Optionally, the generating unit includes:
the setting module is used for presetting test case generation strategies, and each generation strategy corresponds to a packaged script file;
and the execution module is used for calling the script file corresponding to the target generation strategy, importing the first interface relation table and generating a corresponding test case according to the target generation strategy when receiving the target generation strategy specified by the user trigger.
Optionally, the apparatus further comprises:
the marking unit is used for marking the defects and displaying the characteristics if the first interface relation table is judged to have the defects;
and the output unit is used for displaying and outputting a checking report according to the defects and the characteristics and submitting defect management.
In a third aspect, the present invention also provides an electronic device, including: memory, processor and program stored on the memory and capable of running on the processor, when the processor executes the program, the method for generating the software integration test case is realized
In a fourth aspect, the present invention further provides a computer-readable storage medium, on which a computer program is stored, where the computer program implements the method for generating the software integration test case as described above when running.
By the technical scheme, the technical scheme provided by the invention at least has the following advantages:
the invention provides a method and a device for generating a software integration test case, which respectively analyze a software summary design description and a target source code corresponding to the software summary design description and respectively obtain a first interface relation table corresponding to the software summary design description and a second interface relation table corresponding to the target source code, so that the first interface relation table is checked by using the second interface relation table, and if defects are not found in the checking, the first interface relation table is used for generating the test case for the software integration test. Compared with the prior art, the method solves the technical problem that interface testing is not complete and correct enough due to the fact that the interface testing case is constructed by utilizing the software summary design description with defects.
The foregoing description is only an overview of the technical solutions of the present invention, and the embodiments of the present invention are described below in order to make the technical means of the present invention more clearly understood and to make the above and other objects, features, and advantages of the present invention more clearly understandable.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the invention. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
fig. 1 is a flowchart of a method for generating a software integration test case according to an embodiment of the present invention;
fig. 2 is a flowchart of another method for generating a software integration test case according to an embodiment of the present invention;
fig. 3 is a block diagram of a device for generating a software integration test case according to an embodiment of the present invention;
fig. 4 is a block diagram of another apparatus for generating a software integration test case according to an embodiment of the present invention.
Detailed Description
Exemplary embodiments of the present invention will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the invention are shown in the drawings, it should be understood that the invention can be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the invention to those skilled in the art.
The embodiment of the invention provides a method for generating a software integration test case, as shown in fig. 1, the method checks an interface relation table contained in a software summary design description in advance, and generates a test case for software integration test by depending on the interface relation table if no defect exists, so as to ensure the integrity and correctness of the interface test, and the following specific steps are provided for the embodiment of the invention:
101. a software summary design description and its corresponding target source code are obtained.
The software summary design description refers to summary design description for target source code provided by a developer, and interfaces between modules are recorded in the summary design description.
In the embodiment of the invention, the software outline design description is equivalent to a document explanation of the interface relation between the target source code containing modules, and the software outline design description and the target source code have a one-to-one correspondence relation.
102. And analyzing the software summary design description and the target source code respectively to obtain a first interface relation table corresponding to the software summary design description and a second interface relation table corresponding to the target source code.
In the embodiment of the invention, the software summary design description including the interfaces between the modules is sorted out by using an analysis tool, so that a first interface relation table is obtained, the table at least includes the names of the interfaces between the modules and the association between different interfaces, and further, the level calling relation between the modules is obtained by utilizing the association between the interfaces.
Furthermore, the target source code can be analyzed by using a code analysis tool to obtain the interface name between the modules and the hierarchy call relationship between the modules contained in the target source code, and a second interface relationship table is obtained by storing.
103. And judging whether the first interface relation table has defects or not by utilizing the second interface relation table.
In the embodiment of the invention, the software summary design description is equivalent to a document explanation of the interface relationship between the target source code containing modules, and a one-to-one correspondence relationship exists between the software summary design description and the target source code, so that the interface recorded by the software summary design description should exist in the target source code. Therefore, the invention can utilize the second interface relation table corresponding to the target source code to check the first interface relation table, and mainly judges whether the first interface relation table has the defects of incorrect interface reference or call, missing/error interface name and the like or not compared with whether the interface name and the interface relation are consistent or not or whether the interface relation exists in the second interface relation table.
104. And if the first interface relation table is judged to have no defects, generating a test case for software integration by using the first interface relation table.
In the embodiment of the invention, after the first interface relation table is judged to have no defects in advance, namely the software summary design description is checked to be complete and correct in advance, the content of the first interface relation table corresponding to the software summary design description is utilized to generate the test case for the software integration test, so that the integrity and the correctness of the interface test are ensured.
The embodiment of the invention provides a method for generating a software integration test case, which is characterized in that a software summary design description and a target source code corresponding to the software summary design description are respectively analyzed, a first interface relation table corresponding to the software summary design description and a second interface relation table corresponding to the target source code are respectively obtained, so that the first interface relation table is checked by using the second interface relation table, and if defects are not found in the checking, the first interface relation table is used for generating the test case for the software integration test. Compared with the prior art, the method and the device solve the technical problem that interface testing is incomplete and correct due to the fact that the interface testing case is constructed by utilizing the software summary design description with defects.
In order to describe the above embodiment in more detail, the embodiment of the present invention further provides another method for generating a software integration test case, as shown in fig. 2, which details and supplements the above embodiment, and for this embodiment of the present invention, the following specific steps are provided:
201. a software summary design description and its corresponding target source code are obtained.
In the embodiment of the invention, the software outline design description is equivalent to a document explanation of the interface relation between the target source code containing modules, and the software outline design description and the target source code have a one-to-one correspondence relation.
It should be noted that, in order to avoid redundant operations of interface testing and meet different specific testing requirements of a user at the same time, a specific module in the software summary design description may be labeled in advance, so that a first interface relation table corresponding to the software summary design description is obtained as an interface between modules including a labeled module, and then only interfaces and interface relations between the labeled modules are checked in a subsequent implementation.
202. And analyzing the software summary design description and the target source code respectively to obtain a first interface relation table corresponding to the software summary design description and a second interface relation table corresponding to the target source code.
In the embodiment of the present invention, it should be noted that all modules included in the target source code are recorded in the second interface relationship table corresponding to the target source code, and there are interfaces and associations between the interfaces between the modules. However, the software outline design description may have two cases, specifically: one condition is that all modules contained in the software outline design description are recorded in the first interface relation table, and interfaces and the association between the interfaces exist among the modules; in another case, to avoid redundant operations of interface testing, a specific module in the software summary design description is labeled in advance, so that only the labeled modules, interfaces between the labeled modules and associations between the interfaces exist in the first interface relation table.
203. And judging whether the first interface relation table has defects or not by utilizing the second interface relation table.
In the embodiment of the present invention, mainly aiming at two situations of the software summary design description mentioned in step 202, checking whether the first interface relation table has a defect is implemented, and the following concrete statements are provided:
one case is that if all modules contained in the software summary design description are recorded in the first interface relation table, and interfaces and associations between the interfaces exist between the modules, whether the first interface relation table is consistent with the second interface relation table is judged, and if so, the software summary design description is checked to have no defects of interface reference or incorrect calling, interface name omission/errors and the like. Otherwise, judging that the first interface relation table has defects.
In another case, to avoid redundant operations of interface testing, a specific module in the software summary design description is labeled in advance, so that only the labeled modules, interfaces between the labeled modules and associations between the interfaces exist in the first interface relation table. Then judging whether the interfaces existing among the modules recorded in the first interface relation table and the associations existing among the interfaces are contained in the second interface relation table, if so, checking whether the software summary design shows that the defects of interface reference or incorrect calling, interface name omission/errors and the like do not exist. Otherwise, judging that the first interface relation table has defects.
204a, if the first interface relation table is judged to have no defects, presetting test case generation strategies, wherein each generation strategy corresponds to a packaged script file.
For the embodiment of the invention, in order to meet the requirement of test diversity, a mapping relation between a test case generation strategy and each trigger control can be preset, the preset test case generation strategy can be a bottom-up test strategy, a top-down test strategy or a major explosion test strategy, and the trigger control is a packaged script file and is used for automatically calling the corresponding script file to execute automatic operation when a user triggers the control.
205a, when receiving a target generation policy specified by a user trigger, calling a script file corresponding to the target generation policy, importing a first interface relation table, and generating a corresponding test case according to the target generation policy.
For the embodiment of the invention, when it is detected that the user triggers a test case generation strategy, the control can be specifically triggered in a manner of touch control icons, buttons and the like (that is, corresponding to a test generation strategy), and then a script file corresponding to a target generation strategy is called, the first interface relation table is imported into a generator, and according to the triggered test generation strategy, the automatic generation of the test case for the software integration test is realized.
And 204b, if the first interface relation table is judged to have defects, marking the defects, displaying the characteristics, outputting a checking report according to the defects and the characteristics, and submitting defect management.
In addition, for the embodiment of the invention, if the first interface relation table is judged to have defects, that is, the checking software summary design shows that the defects exist, the defects are marked and feature display is carried out, the specific feature display mode can be highlight, bold mark, pop frame selection and the like, so that a checking report can be output according to the defects and the feature display, defect management is automatically submitted, the checking report can clearly display the defects and associated information, and therefore, the problem of the defects can be conveniently solved by checking personnel.
Further, as an implementation of the methods shown in fig. 1 and fig. 2, an embodiment of the present invention provides a device for generating a software integration test case. The embodiment of the apparatus corresponds to the embodiment of the method, and for convenience of reading, details in the embodiment of the apparatus are not repeated one by one, but it should be clear that the apparatus in the embodiment can correspondingly implement all the contents in the embodiment of the method. The device is applied to generating a test case for testing an interface, and specifically as shown in fig. 3, the device includes:
an obtaining unit 31, configured to obtain a software summary design description and a target source code corresponding to the software summary design description;
an analyzing unit 32, configured to analyze the software summary design description obtained by the obtaining unit 31 and the target source code obtained by the obtaining unit 31, respectively, to obtain a first interface relationship table corresponding to the software summary design description and a second interface relationship table corresponding to the target source code;
a determining unit 33, configured to determine whether the first interface relationship table obtained by the analyzing unit 32 has a defect by using the second interface relationship table obtained by the analyzing unit 32;
a generating unit 34, configured to generate a test case for software integration by using the first interface relationship table when the determining unit 33 determines that the first interface relationship table has no defect.
Further, as shown in fig. 4, the judging unit 33 includes:
the first judging module 331, configured to judge whether the first interface relationship table is consistent with the second interface relationship table;
a second determining module 332, configured to determine whether interfaces existing between modules recorded in the first interface relationship table and associations existing between the interfaces are included in the second interface relationship table when the first determining module 331 determines that the first interface relationship table is not consistent with the second interface relationship table;
a determining module 333, configured to determine that the first interface relationship table has a defect when it is determined that the interfaces existing between the modules recorded in the first interface relationship table and the associations existing between the interfaces are not included in the second interface relationship table.
Further, as shown in fig. 4, the generating unit 34 includes:
a setting module 341, configured to preset test case generation policies, where each generation policy corresponds to a packaged script file;
and the execution module 342 is configured to, when a target generation policy specified by a user trigger is received, call a script file corresponding to the target generation policy, import the first interface relationship table, and generate a corresponding test case according to the target generation policy.
Further, as shown in fig. 4, the apparatus further includes:
the marking unit 35 is configured to mark the defect and perform feature display if it is determined that the first interface relationship table has the defect;
and the output unit 36 is used for displaying and outputting a checking report according to the defects and the characteristics and submitting defect management.
In summary, in the embodiments of the present invention, the software summary design description and the target source code corresponding to the software summary design description are respectively analyzed, and the first interface relationship table corresponding to the software summary design description and the second interface relationship table corresponding to the target source code are respectively obtained, so that the first interface relationship table is checked by using the second interface relationship table, and if no defect is found in the checking, the test case for the software integration test is generated by using the first interface relationship table. Compared with the prior art, the method and the device solve the technical problem that interface testing is incomplete and correct due to the fact that the interface testing case is constructed by utilizing the software summary design description with defects.
The generation device for the software integration test case comprises a processor and a memory, wherein the acquisition unit, the analysis unit, the judgment unit, the generation unit and the like are stored in the memory as program units, and the processor executes the program units stored in the memory to realize corresponding functions.
The processor comprises a kernel, and the kernel calls the corresponding program unit from the memory. The kernel can be set to one or more than one, the correctness of the software outline design description is checked in advance by adjusting kernel parameters, and then the test case is automatically generated by utilizing the contained interface relation, so that the test integrity and correctness of the software interface are ensured.
The memory may include volatile memory in a computer readable medium, Random Access Memory (RAM) and/or nonvolatile memory such as Read Only Memory (ROM) or flash memory (flash RAM), and the memory includes at least one memory chip.
An embodiment of the present invention provides an electronic device, including: the software integration test case generation method comprises a memory, a processor and a program which is stored on the memory and can run on the processor, wherein when the processor executes the program, the generation method for the software integration test case is realized.
The embodiment of the invention provides a computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and the program realizes the generation method for the software integration test case when running.
The device herein may be a server, a PC, a PAD, a mobile phone, etc.
The present application further provides a computer program product adapted to perform program code for initializing the following method steps when executed on a data processing device: acquiring a software outline design description and a corresponding target source code thereof; analyzing the software summary design description and the target source code respectively to obtain a first interface relation table corresponding to the software summary design description and a second interface relation table corresponding to the target source code; judging whether the first interface relation table has defects or not by utilizing the second interface relation table; and if not, generating a test case for software integration by using the first interface relation table.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include transitory computer readable media (trahsity media) such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The above are merely examples of the present application and are not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (10)
1. A method for generating a software integration test case, the method comprising:
acquiring a software outline design description and a corresponding target source code thereof;
analyzing the software summary design description and the target source code respectively to obtain a first interface relation table corresponding to the software summary design description and a second interface relation table corresponding to the target source code;
judging whether the first interface relation table has defects or not by utilizing the second interface relation table;
and if not, generating a test case for software integration by using the first interface relation table.
2. The method of claim 1, wherein said determining whether the first interface relationship table has a defect by using the second interface relationship table comprises:
judging whether the first interface relation table is consistent with the second interface relation table or not;
if not, judging whether the interfaces existing among the modules recorded by the first interface relation table and the association existing among the interfaces are contained in the second interface relation table or not;
if not, determining that the first interface relation table has defects.
3. The method according to claim 1, wherein the generating a test case for software integration by using the first interface relationship table comprises:
presetting test case generation strategies, wherein each generation strategy corresponds to a packaged script file;
and when a target generation strategy appointed by a user is received, calling a script file corresponding to the target generation strategy, importing the first interface relation table and generating a corresponding test case according to the target generation strategy.
4. The method of claim 1, wherein if the first interface relationship table is determined to be defective, the method further comprises:
marking the defects and displaying characteristics;
and displaying and outputting a checking report according to the defects and the characteristics, and submitting defect management.
5. An apparatus for generating a software integration test case, the apparatus comprising:
the acquisition unit is used for acquiring the software outline design description and the corresponding target source code;
the analysis unit is used for respectively analyzing the software summary design description acquired by the acquisition unit and the target source code acquired by the acquisition unit to obtain a first interface relation table corresponding to the software summary design description and a second interface relation table corresponding to the target source code;
the judging unit is used for judging whether the first interface relation table obtained by the analyzing unit has defects or not by utilizing the second interface relation table obtained by the analyzing unit;
and the generating unit is used for generating a test case for software integration by using the first interface relation table when the judging unit judges that the first interface relation table has no defects.
6. The apparatus according to claim 5, wherein the judging unit includes:
the first judging module is used for judging whether the first interface relation table is consistent with the second interface relation table or not;
a second judging module, configured to, when the first judging module judges that the first interface relationship table is not consistent with the second interface relationship table, judge whether interfaces existing between modules recorded in the first interface relationship table and associations existing between the interfaces are included in the second interface relationship table;
and the determining module is used for judging that the first interface relation table has defects when determining that the interfaces existing among the modules recorded by the first interface relation table and the associations existing among the interfaces are not contained in the second interface relation table.
7. The apparatus of claim 5, wherein the generating unit comprises:
the setting module is used for presetting test case generation strategies, and each generation strategy corresponds to a packaged script file;
and the execution module is used for calling the script file corresponding to the target generation strategy, importing the first interface relation table and generating a corresponding test case according to the target generation strategy when receiving the target generation strategy specified by the user trigger.
8. The apparatus of claim 5, further comprising:
the marking unit is used for marking the defects and displaying the characteristics if the first interface relation table is judged to have the defects;
and the output unit is used for displaying and outputting a checking report according to the defects and the characteristics and submitting defect management.
9. An electronic device, comprising: the device comprises a memory, a processor and a program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the method for generating the software integration test case according to any one of claims 1 to 4.
10. A computer-readable storage medium, on which a computer program is stored, which when executed implements a method for generating software integration test cases according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010911948.8A CN112015658A (en) | 2020-09-02 | 2020-09-02 | Method and device for generating software integration test case |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010911948.8A CN112015658A (en) | 2020-09-02 | 2020-09-02 | Method and device for generating software integration test case |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112015658A true CN112015658A (en) | 2020-12-01 |
Family
ID=73515331
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010911948.8A Pending CN112015658A (en) | 2020-09-02 | 2020-09-02 | Method and device for generating software integration test case |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112015658A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112905486A (en) * | 2021-03-26 | 2021-06-04 | 建信金融科技有限责任公司 | Service integration test method, device and system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106528100A (en) * | 2015-08-05 | 2017-03-22 | 通用电气公司 | System and method for model based technology and process for safety-critical software development |
| CN107391368A (en) * | 2017-07-13 | 2017-11-24 | 中国航发控制系统研究所 | Source code and the analysis method of object code uniformity in a kind of airborne software |
| US10084819B1 (en) * | 2013-03-13 | 2018-09-25 | Hrl Laboratories, Llc | System for detecting source code security flaws through analysis of code history |
| CN110309051A (en) * | 2019-05-22 | 2019-10-08 | 深圳壹账通智能科技有限公司 | Method, system, equipment and the storage medium of management of test cases |
| CN111274120A (en) * | 2018-12-05 | 2020-06-12 | 北京奇虎科技有限公司 | Interface document verification method and device |
-
2020
- 2020-09-02 CN CN202010911948.8A patent/CN112015658A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10084819B1 (en) * | 2013-03-13 | 2018-09-25 | Hrl Laboratories, Llc | System for detecting source code security flaws through analysis of code history |
| CN106528100A (en) * | 2015-08-05 | 2017-03-22 | 通用电气公司 | System and method for model based technology and process for safety-critical software development |
| CN107391368A (en) * | 2017-07-13 | 2017-11-24 | 中国航发控制系统研究所 | Source code and the analysis method of object code uniformity in a kind of airborne software |
| CN111274120A (en) * | 2018-12-05 | 2020-06-12 | 北京奇虎科技有限公司 | Interface document verification method and device |
| CN110309051A (en) * | 2019-05-22 | 2019-10-08 | 深圳壹账通智能科技有限公司 | Method, system, equipment and the storage medium of management of test cases |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112905486A (en) * | 2021-03-26 | 2021-06-04 | 建信金融科技有限责任公司 | Service integration test method, device and system |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8397104B2 (en) | Creation of test plans | |
| US7293213B1 (en) | Method for detecting software errors and vulnerabilities | |
| US10209984B2 (en) | Identifying a defect density | |
| CN111026080A (en) | Hardware-in-loop test method and device for controller | |
| CN108038039A (en) | The method and micro services system of record log | |
| CA2811617C (en) | Commit sensitive tests | |
| CN111209206A (en) | Automatic test method and system for software product | |
| CN115080398A (en) | Automatic interface test system and method | |
| CN110879781A (en) | Program debugging method and device, electronic equipment and computer readable storage medium | |
| US9779014B2 (en) | Resilient mock object creation for unit testing | |
| CN112015658A (en) | Method and device for generating software integration test case | |
| CN111367710B (en) | eMMC problem reduction method and device | |
| CN116860608A (en) | Interface testing method and device, computing equipment and storage medium | |
| CN115795489A (en) | Software vulnerability static analysis method and device based on hardware-level process tracking | |
| CN111880078A (en) | Method and equipment for automated instruction testing | |
| CN111078574A (en) | Method and device for generating influence analysis report | |
| CN110874315B (en) | Test method, test device, electronic equipment and storage medium | |
| CN114817078B (en) | Automatic testing method and device and storage medium | |
| CN112559370A (en) | Front-end-based React project unit testing method and related equipment | |
| CN117724436A (en) | Test method and device for DCS system, storage medium and electronic equipment | |
| CN116756037A (en) | Abnormal code positioning system, method, equipment and computer readable storage medium | |
| CN116166544A (en) | Recording method and device of test script, computer storage medium and electronic device | |
| CN116991726A (en) | Service testing method, device and medium based on interface automation | |
| CN115758377A (en) | Container vulnerability processing method and device, storage medium and electronic equipment | |
| CN113722214A (en) | Test method, test equipment and test 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 |