CN110750447B - Software testing method and related equipment - Google Patents
Software testing method and related equipment Download PDFInfo
- Publication number
- CN110750447B CN110750447B CN201910880742.0A CN201910880742A CN110750447B CN 110750447 B CN110750447 B CN 110750447B CN 201910880742 A CN201910880742 A CN 201910880742A CN 110750447 B CN110750447 B CN 110750447B
- Authority
- CN
- China
- Prior art keywords
- software
- tested
- target
- types
- test
- 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.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3684—Test management for test design, e.g. generating new test cases
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/3688—Test management for test execution, e.g. scheduling of test suites
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application relates to an improvement of a test flow in the technical field of software testing, in particular to a software testing method and related equipment, wherein the method comprises the following steps: acquiring first software to be tested and second software to be tested, wherein the first software to be tested is the software to be tested after version updating, and the second software to be tested is the software to be tested before version updating; determining N target demand types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, wherein N is an integer greater than 1; inputting N target demand types into a test strategy model for processing, outputting N target test strategies, wherein the N target test strategies are in one-to-one correspondence with the N target demand types; and testing the first software to be tested by adopting N target test strategies to obtain a software test result corresponding to the first software to be tested. The embodiment of the application is beneficial to improving the test efficiency of software test.
Description
Technical Field
The application relates to the technical field of software testing, in particular to a software testing method and related equipment.
Background
At present, the process of testing the software to be tested is as follows: and manually determining a plurality of target demand types corresponding to the software to be tested, manually selecting a plurality of target test strategies corresponding to the plurality of target demand types, and touching the test button to enable the electronic equipment to test the software to be tested according to the plurality of target test strategies so as to obtain a software test result of the software to be tested. This approach results in a lower test efficiency for software testing.
Disclosure of Invention
The embodiment of the application provides a software testing method and related equipment, which are used for improving the testing efficiency of software testing.
In a first aspect, an embodiment of the present application provides a software testing method, where the method includes:
acquiring first software to be tested and second software to be tested, wherein the first software to be tested is software to be tested after version updating, and the second software to be tested is software to be tested before version updating;
determining N target demand types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, wherein N is an integer greater than 1;
inputting the N target demand types into a test strategy model for processing, and outputting N target test strategies, wherein the N target test strategies are in one-to-one correspondence with the N target demand types;
and testing the first software to be tested by adopting the N target test strategies to obtain a software test result corresponding to the first software to be tested.
In a second aspect, embodiments of the present application provide a software testing apparatus, the apparatus including:
the system comprises an acquisition unit, a storage unit and a control unit, wherein the acquisition unit is used for acquiring first software to be tested and second software to be tested, the first software to be tested is software to be tested after version updating, and the second software to be tested is software to be tested before version updating;
The determining unit is used for determining N target demand types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, wherein N is an integer greater than 1;
the processing unit is used for inputting the N target demand types into the test strategy model for processing, outputting N target test strategies, and the N target test strategies are in one-to-one correspondence with the N target demand types;
and the testing unit is used for testing the first software to be tested by adopting the N target testing strategies to obtain a software testing result corresponding to the first software to be tested.
In a third aspect, embodiments of the present application provide an electronic device comprising a processor, a memory, a communication interface, and one or more programs stored in the memory and configured to be executed by the processor, the programs including instructions for performing part or all of the steps in the method of the first aspect of embodiments of the present application.
In a fourth aspect, embodiments of the present application provide a computer readable storage medium storing a computer program for execution by a processor to implement some or all of the steps described in the method according to the first aspect of embodiments of the present application.
It can be seen that, compared with the method of manually determining a plurality of target requirement types corresponding to the software to be tested and a plurality of target test strategies corresponding to the plurality of target requirement types, and testing the software to be tested according to the plurality of target test strategies to obtain a software test result of the software to be tested, in the embodiment of the application, the electronic device determines N target requirement types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, inputs the N target requirement types into the test strategy model for processing, outputs the N target test strategies, and tests the first software to be tested by adopting the N target test strategies to obtain the software test result corresponding to the first software to be tested, thereby being beneficial to improving the test efficiency of the software test.
These and other aspects of the present application will be more readily apparent from the following description of the embodiments.
Drawings
In order to more clearly describe the technical solutions in the embodiments or the background of the present application, the following description will describe the drawings that are required to be used in the embodiments or the background of the present application.
FIG. 1 is a schematic diagram of a software testing system according to an embodiment of the present application;
FIG. 2 is a schematic flow chart of a software testing method according to an embodiment of the present application;
FIG. 3 is a flow chart of another software testing method according to an embodiment of the present application;
FIG. 4 is a functional block diagram of a software testing apparatus according to an embodiment of the present application;
fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed description of the preferred embodiments
In order to make the present application solution better understood by those skilled in the art, the following description will be made in detail and with reference to the accompanying drawings in the embodiments of the present application, it is apparent that the described embodiments are only some embodiments of the present application, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, shall fall within the scope of the present application.
The following will describe in detail.
The terms "first," "second," "third," and "fourth" and the like in the description and in the claims of this application and in the drawings, are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, system, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the present application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.
The embodiments of the present application are described in detail below.
Referring to fig. 1, fig. 1 is a schematic structural diagram of a software testing system according to an embodiment of the present application, where the software testing system includes a processor, and:
the processor is used for acquiring first software to be tested and second software to be tested, wherein the first software to be tested is the software to be tested after version updating, and the second software to be tested is the software to be tested before version updating;
the processor is used for determining N target demand types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, wherein N is an integer greater than 1;
the processor is used for inputting N target demand types into the test strategy model for processing, outputting N target test strategies, and the N target test strategies are in one-to-one correspondence with the N target demand types;
And the processor is used for testing the first software to be tested by adopting N target test strategies to obtain a software test result corresponding to the first software to be tested.
Referring to fig. 2, fig. 2 is a flowchart of a software testing method according to an embodiment of the present application, where the software testing method includes steps 201 to 204, specifically as follows:
201: the electronic equipment acquires first software to be tested and second software to be tested, wherein the first software to be tested is software to be tested after version updating, and the second software to be tested is software to be tested before version updating.
In one possible example, before the electronic device obtains the first software to be tested and the second software to be tested, the method further includes:
the electronic equipment acquires a target software type, a target software test period and a target software aiming crowd corresponding to the first software to be tested;
the electronic equipment determines a first software score corresponding to the target software type according to the mapping relation between the software type and the software score;
the electronic equipment determines a second software score corresponding to the target software test period according to the mapping relation between the software test period and the software score;
the electronic equipment determines a third software score corresponding to the target software aiming at the crowd according to the mapping relation of the software aiming at the crowd and the software score;
The electronic equipment determines a target software score corresponding to the first software to be tested according to the first software score, the second software score, the third software score and a software score formula;
and the electronic equipment adjusts the test sequence of the first software to be tested in the software test queue according to the target software score.
Specifically, the electronic device includes a display screen, and the electronic device obtains a target software type, a target software test period, and an implementation manner of the target software for the crowd corresponding to the first software to be tested may be: the electronic equipment displays a to-be-tested software information interface on a display screen, wherein the to-be-tested software information interface comprises a software type input box, a software test period input box and a software aiming crowd input box; when the first touch operation aiming at the software type input box, the software testing period input box and the crowd input box is detected, the electronic equipment acquires a target software type, a target software testing period and a target software aiming at the crowd corresponding to the first touch operation.
The mapping relation between the software types and the software scores, the mapping relation between the software test periods and the software scores and the mapping relation between the software and the population and the software scores are pre-stored in the electronic equipment.
The software score formula is as follows:
S＝A1×α1+A2×α2+A3×α3，
s is a target software score corresponding to a first software to be tested, A1 is a first software score corresponding to a target software type, α1 is a weight corresponding to the target software type, A2 is a second software score corresponding to a target software test period, α2 is a weight corresponding to the target software test period, A3 is a third software score corresponding to a crowd of target software, α3 is a weight corresponding to the crowd of target software, and α1+α2+α3=1.
In this example, the electronic device determines, according to the type of the target software corresponding to the first software to be tested, the test period of the target software, and the target software score corresponding to the first software to be tested for the population, and adjusts the test sequence of the first software to be tested in the software test queue according to the target software score, so that the duration of testing the first software to be tested is shortened, and the release rate of the first software to be tested is accelerated.
In one possible example, the electronic device obtains first software to be tested and second software to be tested, including:
when a software testing request is detected, the electronic equipment acquires a first software version number and a second software version number which are included in the software testing request, wherein the first software version number is the version number of software to be tested after version updating, and the second software version number is the version number of the software to be tested before version updating;
The electronic equipment respectively determines a first storage position corresponding to the first software version number and a second storage position corresponding to the second software version number according to the mapping relation between the pre-stored software version number and the storage position of the software to be tested;
the electronic equipment respectively selects first software to be tested corresponding to the first storage position and second software to be tested corresponding to the second storage position from a plurality of software to be tested included in the software library to be tested.
The mapping relation between the software version number and the storage position of the software to be tested is stored in the electronic equipment in advance.
The software library to be tested is stored in the electronic equipment in advance.
202: the electronic equipment determines N target demand types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, wherein N is an integer greater than 1.
The requirement types include functional requirement, performance requirement, security requirement and reliability requirement. Compatibility requirements, etc.
In one possible example, the determining, by the electronic device, N target requirement types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested includes:
The electronic equipment respectively acquires a first program code set corresponding to the first software to be tested and a second program code set corresponding to the second software to be tested;
the electronic device determining N target program code segments of the first set of program code that are different from the second set of program code;
the electronic equipment acquires N target program annotations corresponding to the N target program code segments, wherein the N target program annotations are in one-to-one correspondence with the N target program code segments;
and the electronic equipment determines N target demand types corresponding to the first software to be tested according to the mapping relation between the pre-stored program comments and the demand types, wherein the N target demand types are in one-to-one correspondence with the N target program comments.
Wherein the program notes are entered by a developer when writing the program code segments.
In particular, an implementation of the electronic device determining N target program code segments, where the first set of program code is different from the second set of program code, may be: the electronic device commands N object program code segments of the first set of program code different from the second set of program code according to the gitdiff.
The gitdiff HEAD- < filename > command is used for comparing the change information of the software to be tested of the different versions submitted last two times in the software library to be tested.
Specifically, the mapping relation between the program annotation and the requirement type is pre-stored in the electronic device.
In one possible example, the determining, by the electronic device, N target requirement types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested includes:
the electronic equipment respectively acquires a first program code set corresponding to the first software to be tested and a second program code set corresponding to the second software to be tested;
the electronic device determining N target program code segments of the first set of program code that are different from the second set of program code;
the electronic equipment acquires N target program annotations corresponding to the N target program code segments, wherein the N target program annotations are in one-to-one correspondence with the N target program code segments;
the electronic equipment determines N first demand types according to a mapping relation between pre-stored program comments and demand types, wherein the N first demand types are in one-to-one correspondence with the N target program comments;
the electronic equipment acquires N second requirement types corresponding to the first software to be tested, wherein the N second requirement types are input by a tester aiming at the N target program code sections;
If the N second requirement types are the same as the N first requirement types, the electronic equipment determines the N first requirement types as N target requirement types corresponding to the first software to be tested.
Specifically, the implementation manner of the electronic device obtaining N second requirement types corresponding to the first software to be tested may be: the electronic equipment displays a demand type information interface on a display screen, wherein the demand type information interface comprises N target program code sections and N demand type input boxes, and the N demand type input boxes are in one-to-one correspondence with the N target program code sections; when a second touch operation aiming at the N requirement type input boxes is detected, the electronic equipment acquires N target requirement types corresponding to the second touch operation.
In one possible example, the method further comprises:
if the N second requirement types are different from the N first requirement types, the electronic equipment sends a requirement type request carrying the N target program code segments to a requirement type platform, wherein the requirement type request is used for indicating the requirement type platform to feed back the requirement type corresponding to each target program code segment in the N target program code segments;
The electronic equipment receives N third requirement types sent by the requirement type platform aiming at the requirement type request;
if the N third requirement types are the same as the N first requirement types and the N third requirement types are different from the N second requirements, the electronic device determines the N first requirement types as N target requirement types corresponding to the first software to be tested;
if the N third requirement types are different from the N first requirement types and the N third requirement types are the same as the N second requirement types, the electronic device determines the N second requirement types as N target requirement types corresponding to the first software to be tested.
In one possible example, the method further comprises:
if the N third requirement types are different from the N first requirement types and the N third requirement types are different from the N second requirement types, the electronic device determines the N third requirement types as N target requirement types corresponding to the first software to be tested.
In one possible example, the determining, by the electronic device, N target requirement types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested includes:
The electronic equipment respectively acquires a first program code set corresponding to first software to be tested and a second program code set corresponding to second software to be tested;
the electronic device determining N target program code segments of the first set of program code that are different from the second set of program code;
the electronic equipment acquires N target program comments corresponding to N target program code sections, wherein the N target program comments are in one-to-one correspondence with the N target program code sections;
the electronic equipment determines N first requirement types according to the mapping relation between the annotation program and the requirement types, wherein the N first requirement types are in one-to-one correspondence with N target program annotations;
the electronic equipment sends a demand type request carrying N target program code segments to a demand type platform, wherein the demand type request is used for indicating the demand type platform to feed back the demand type corresponding to each target program code segment in the N target program code segments;
the electronic equipment receives N third requirement types sent by a requirement type platform aiming at a requirement type request;
if the N third requirement types are the same as the N first requirement types, the electronic equipment determines the N first requirement types as N target requirement types corresponding to the first software to be tested;
If the N third requirement types are different from the N first requirement types, the electronic device determines the N third requirement types as N target requirement types corresponding to the first software to be tested.
203: the electronic equipment inputs the N target demand types into a test strategy model for processing, and outputs N target test strategies, wherein the N target test strategies are in one-to-one correspondence with the N target demand types.
The test strategy model is used for selecting a test strategy matched with the requirement type.
In one possible example, the electronic device inputs the N target requirement types into a test policy model for processing, outputs N target test policies, and includes:
the electronic equipment inputs the N target demand types into a test strategy model, wherein the test strategy model comprises a mapping relation between the demand types and test strategy names and a mapping relation between the test strategy names and storage positions of the test strategies;
the electronic equipment determines N target test strategy names according to the mapping relation between the requirement types and the test strategy names, wherein the N target test strategy names are in one-to-one correspondence with the N target requirement types;
the electronic equipment determines N third storage positions according to the mapping relation between the test strategy names and the storage positions of the test strategies, wherein the N third storage positions are in one-to-one correspondence with the N target test strategy names;
The electronic equipment selects N target test strategies corresponding to the N third storage positions from a plurality of test strategies included in the test strategy library, and the N target test strategies are in one-to-one correspondence with the N third storage positions.
The test strategy library is stored in the electronic equipment in advance.
204: and the electronic equipment adopts the N target test strategies to test the first software to be tested to obtain a software test result corresponding to the first software to be tested.
In one possible example, the electronic device tests the first software to be tested by adopting the N target test policies to obtain a software test result corresponding to the first software to be tested, including:
the electronic equipment adopts an ith target test strategy to test the first software to be tested to obtain an ith software part test result corresponding to the ith target test strategy;
after the test result of the ith software part is obtained, the electronic equipment adopts the (i+1) th target test strategy to test the first software to be tested, and the (i+1) th software part test result corresponding to the (i+1) th target test strategy is obtained;
until i=n, stopping testing the first software to be tested by the electronic device to obtain N software part test results, wherein i is an increasing integer with an initial value of 1 and 1 as an interval;
And the electronic equipment determines the N software part test results as software test results corresponding to the first software to be tested.
It can be seen that, compared with the method of manually determining a plurality of target requirement types corresponding to the software to be tested and a plurality of target test strategies corresponding to the plurality of target requirement types, and testing the software to be tested according to the plurality of target test strategies to obtain a software test result of the software to be tested, in the embodiment of the application, the electronic device determines N target requirement types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, inputs the N target requirement types into the test strategy model for processing, outputs the N target test strategies, and tests the first software to be tested by adopting the N target test strategies to obtain the software test result corresponding to the first software to be tested, thereby being beneficial to improving the test efficiency of the software test.
In one possible example, the electronic device includes a display screen, and after the electronic device adopts N target test strategies to test the first software to be tested to obtain a software test result corresponding to the first software to be tested, the method further includes:
The electronic equipment converts a software test result corresponding to the first software to be tested into a truth table;
the electronic device displays the truth table through the display screen.
In this example, the electronic device converts the software test result corresponding to the first software to be tested into a truth table, and displays the truth table through the display screen, and displays the software test result of the first software to be tested in the form of the truth table, so that the consultability of the software test result of the software to be tested is improved.
Referring to fig. 3, fig. 3 is a schematic flow chart of another software testing method according to the embodiment of the present application, which is consistent with the embodiment shown in fig. 2, and the software testing method includes steps 301 to 311, specifically as follows:
301: when a software test request is detected, the electronic equipment acquires a first software version number and a second software version number which are included in the software test request, wherein the first software version number is the version number of software to be tested after version update, and the second software version number is the version number of the software to be tested before version update.
302: and the electronic equipment respectively determines a first storage position corresponding to the first software version number and a second storage position corresponding to the second software version number according to the mapping relation between the pre-stored software version number and the storage position of the software to be tested.
303: the electronic equipment respectively selects first software to be tested corresponding to the first storage position and second software to be tested corresponding to the second storage position from a plurality of software to be tested included in the software library to be tested.
304: the electronic equipment respectively acquires a first program code set corresponding to the first software to be tested and a second program code set corresponding to the second software to be tested.
305: the electronic device determines N target program code segments of the first set of program code that are different from the second set of program code.
306: the electronic equipment acquires N target program annotations corresponding to the N target program code segments, wherein the N target program annotations are in one-to-one correspondence with the N target program code segments.
307: the electronic equipment determines N first requirement types corresponding to the first software to be tested according to a mapping relation between pre-stored program comments and requirement types, wherein the N first requirement types are in one-to-one correspondence with the N target program comments.
308: the electronic equipment acquires N second requirement types corresponding to the first software to be tested, wherein the N second requirement types are input by a tester aiming at the N target program code sections.
309: if the N second requirement types are the same as the N first requirement types, the electronic equipment determines the N first requirement types as N target requirement types corresponding to the first software to be tested.
310: the electronic equipment inputs the N target demand types into a test strategy model for processing, and outputs N target test strategies, wherein the N target test strategies are in one-to-one correspondence with the N target demand types.
311: and the electronic equipment adopts the N target test strategies to test the first software to be tested to obtain a software test result corresponding to the first software to be tested.
It should be noted that, the specific implementation of each step of the method shown in fig. 3 may refer to the specific implementation of the foregoing method, which is not described herein.
The foregoing embodiments mainly describe the solutions of the embodiments of the present application from the point of view of the method-side execution procedure. It will be appreciated that the electronic device, in order to achieve the above-described functions, includes corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will readily appreciate that the elements and algorithm steps of the examples described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
According to the embodiment of the application, the electronic device may be divided into the functional units according to the method example, for example, each functional unit may be divided corresponding to each function, or two or more functions may be integrated into one processing unit. The integrated units may be implemented in hardware or in software functional units. It should be noted that, in the embodiment of the present application, the division of the units is schematic, which is merely a logic function division, and other division manners may be implemented in actual practice.
Referring to fig. 4, fig. 4 is a functional unit block diagram of a software testing apparatus according to an embodiment of the present application, where the software testing apparatus 400 includes:
an obtaining unit 401, configured to obtain a first software to be tested and a second software to be tested, where the first software to be tested is software to be tested after version update, and the second software to be tested is software to be tested before version update;
a determining unit 402, configured to determine N target demand types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, where N is an integer greater than 1;
The processing unit 403 is configured to input the N target demand types into a test policy model for processing, and output N target test policies, where the N target test policies are in one-to-one correspondence with the N target demand types;
and the testing unit 404 is configured to test the first software to be tested by using the N target testing strategies, so as to obtain a software testing result corresponding to the first software to be tested.
It can be seen that, compared with the method of manually determining a plurality of target requirement types corresponding to the software to be tested and a plurality of target test strategies corresponding to the plurality of target requirement types, and testing the software to be tested according to the plurality of target test strategies to obtain a software test result of the software to be tested, in the embodiment of the application, the electronic device determines N target requirement types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, inputs the N target requirement types into the test strategy model for processing, outputs the N target test strategies, and tests the first software to be tested by adopting the N target test strategies to obtain the software test result corresponding to the first software to be tested, thereby being beneficial to improving the test efficiency of the software test.
In one possible example, in terms of acquiring the first software to be tested and the second software to be tested, the above-mentioned acquiring unit 401 is specifically configured to:
when a software testing request is detected, a first software version number and a second software version number which are included in the software testing request are obtained, wherein the first software version number is the version number of software to be tested after version updating, and the second software version number is the version number of the software to be tested before version updating;
respectively determining a first storage position corresponding to the first software version number and a second storage position corresponding to the second software version number according to a mapping relation between a pre-stored software version number and a storage position of software to be tested;
and respectively selecting the first software to be tested corresponding to the first storage position and the second software to be tested corresponding to the second storage position from a plurality of software to be tested included in the software library to be tested.
In one possible example, in determining N target requirement types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, the determining unit 402 is specifically configured to:
respectively acquiring a first program code set corresponding to the first software to be tested and a second program code set corresponding to the second software to be tested;
Determining N target program code segments of the first set of program code that are different from the second set of program code;
acquiring N target program annotations corresponding to the N target program code segments, wherein the N target program annotations are in one-to-one correspondence with the N target program code segments;
and determining N target demand types corresponding to the first software to be tested according to a mapping relation between pre-stored program comments and demand types, wherein the N target demand types and the N target program comments are in one-to-one correspondence.
In one possible example, in determining N target requirement types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, the determining unit 402 is specifically configured to:
respectively acquiring a first program code set corresponding to the first software to be tested and a second program code set corresponding to the second software to be tested;
determining N target program code segments of the first set of program code that are different from the second set of program code;
acquiring N target program annotations corresponding to the N target program code segments, wherein the N target program annotations are in one-to-one correspondence with the N target program code segments;
Determining N first demand types according to a mapping relation between pre-stored program comments and demand types, wherein the N first demand types are in one-to-one correspondence with the N target program comments;
acquiring N second requirement types corresponding to the first software to be tested, wherein the N second requirement types are input by a tester aiming at the N target program code segments;
and if the N second demand types are the same as the N first demand types, determining the N first demand types as N target demand types corresponding to the first software to be tested.
In one possible example, in determining N target requirement types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, the determining unit 402 is specifically configured to:
if the N second demand types are different from the N first demand types, a demand type request carrying the N target program code segments is sent to a demand type platform, wherein the demand type request is used for indicating the demand type platform to feed back the demand type corresponding to each target program code segment in the N target program code segments;
receiving N third requirement types sent by the requirement type platform aiming at the requirement type request;
If the N third requirement types are the same as the N first requirement types and the N third requirement types are different from the N second requirements, determining the N first requirement types as N target requirement types corresponding to the first software to be tested;
and if the N third demand types are different from the N first demand types and the N third demand types are the same as the N second demand types, determining the N second demand types as N target demand types corresponding to the first software to be tested.
In one possible example, in terms of inputting the N target requirement types into the test policy model for processing and outputting N target test policies, the processing unit 403 is specifically configured to:
inputting the N target demand types into a test strategy model, wherein the test strategy model comprises a mapping relation between the demand types and test strategy names and a mapping relation between the test strategy names and storage positions of the test strategies;
determining N target test strategy names according to the mapping relation between the demand type and the test strategy names, wherein the N target test strategy names are in one-to-one correspondence with the N target demand types;
Determining N third storage positions according to the mapping relation between the test strategy names and the storage positions of the test strategies, wherein the N third storage positions are in one-to-one correspondence with the N target test strategy names;
and selecting N target test strategies corresponding to the N third storage positions from a plurality of test strategies included in the test strategy library, wherein the N target test strategies are in one-to-one correspondence with the N third storage positions.
In one possible example, in testing the first software to be tested by using the N target test policies to obtain a software test result corresponding to the first software to be tested, the test unit 404 is specifically configured to:
testing the first software to be tested by adopting an ith target test strategy to obtain an ith software part test result corresponding to the ith target test strategy;
after the test result of the ith software part is obtained, testing the first software to be tested by adopting an (i+1) th target test strategy to obtain the test result of the (i+1) th software part corresponding to the (i+1) th target test strategy;
stopping testing the first software to be tested until i=N to obtain N software part test results, wherein i is an increasing integer with an initial value of 1 and 1 as an interval;
And determining the N software part test results as software test results corresponding to the first software to be tested.
Referring to fig. 5, fig. 5 is a schematic structural diagram of an electronic device according to an embodiment of the present application, where the electronic device 500 includes a processor, a memory, a communication interface, and one or more programs, and the one or more programs are stored in the memory and configured to be executed by the processor, and the programs include instructions for executing the following steps:
acquiring first software to be tested and second software to be tested, wherein the first software to be tested is software to be tested after version updating, and the second software to be tested is software to be tested before version updating;
determining N target demand types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, wherein N is an integer greater than 1;
inputting the N target demand types into a test strategy model for processing, and outputting N target test strategies, wherein the N target test strategies are in one-to-one correspondence with the N target demand types;
and testing the first software to be tested by adopting the N target test strategies to obtain a software test result corresponding to the first software to be tested.
It can be seen that, compared with the method of manually determining a plurality of target requirement types corresponding to the software to be tested and a plurality of target test strategies corresponding to the plurality of target requirement types, and testing the software to be tested according to the plurality of target test strategies to obtain a software test result of the software to be tested, in the embodiment of the application, the electronic device determines N target requirement types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, inputs the N target requirement types into the test strategy model for processing, outputs the N target test strategies, and tests the first software to be tested by adopting the N target test strategies to obtain the software test result corresponding to the first software to be tested, thereby being beneficial to improving the test efficiency of the software test.
In one possible example, in acquiring the first software to be tested and the second software to be tested, the above-mentioned program comprises instructions specifically for performing the following steps:
when a software testing request is detected, a first software version number and a second software version number which are included in the software testing request are obtained, wherein the first software version number is the version number of software to be tested after version updating, and the second software version number is the version number of the software to be tested before version updating;
Respectively determining a first storage position corresponding to the first software version number and a second storage position corresponding to the second software version number according to a mapping relation between a pre-stored software version number and a storage position of software to be tested;
and respectively selecting the first software to be tested corresponding to the first storage position and the second software to be tested corresponding to the second storage position from a plurality of software to be tested included in the software library to be tested.
In one possible example, in determining N target requirement types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, the above program includes instructions specifically for executing the following steps:
respectively acquiring a first program code set corresponding to the first software to be tested and a second program code set corresponding to the second software to be tested;
determining N target program code segments of the first set of program code that are different from the second set of program code;
acquiring N target program annotations corresponding to the N target program code segments, wherein the N target program annotations are in one-to-one correspondence with the N target program code segments;
and determining N target demand types corresponding to the first software to be tested according to a mapping relation between pre-stored program comments and demand types, wherein the N target demand types and the N target program comments are in one-to-one correspondence.
In one possible example, in determining N target requirement types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, the above program includes instructions specifically for executing the following steps:
respectively acquiring a first program code set corresponding to the first software to be tested and a second program code set corresponding to the second software to be tested;
determining N target program code segments of the first set of program code that are different from the second set of program code;
acquiring N target program annotations corresponding to the N target program code segments, wherein the N target program annotations are in one-to-one correspondence with the N target program code segments;
determining N first demand types according to a mapping relation between pre-stored program comments and demand types, wherein the N first demand types are in one-to-one correspondence with the N target program comments;
acquiring N second requirement types corresponding to the first software to be tested, wherein the N second requirement types are input by a tester aiming at the N target program code segments;
and if the N second demand types are the same as the N first demand types, determining the N first demand types as N target demand types corresponding to the first software to be tested.
In one possible example, in determining N target requirement types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, the above program includes instructions specifically for executing the following steps:
if the N second demand types are different from the N first demand types, a demand type request carrying the N target program code segments is sent to a demand type platform, wherein the demand type request is used for indicating the demand type platform to feed back the demand type corresponding to each target program code segment in the N target program code segments;
receiving N third requirement types sent by the requirement type platform aiming at the requirement type request;
if the N third requirement types are the same as the N first requirement types and the N third requirement types are different from the N second requirements, determining the N first requirement types as N target requirement types corresponding to the first software to be tested;
if the N third demand types are different from the N first demand types and the N third demand types are the same as the N second demand types, determining the N second demand types as the N first demand types
N target demand types corresponding to the first software to be tested.
In one possible example, in inputting the N target demand types into a test policy model for processing, outputting N target test policies, the program includes instructions specifically for performing the steps of:
inputting the N target demand types into a test strategy model, wherein the test strategy model comprises a mapping relation between the demand types and test strategy names and a mapping relation between the test strategy names and storage positions of the test strategies;
determining N target test strategy names according to the mapping relation between the demand type and the test strategy names, wherein the N target test strategy names are in one-to-one correspondence with the N target demand types;
determining N third storage positions according to the mapping relation between the test strategy names and the storage positions of the test strategies, wherein the N third storage positions are in one-to-one correspondence with the N target test strategy names;
and selecting N target test strategies corresponding to the N third storage positions from a plurality of test strategies included in the test strategy library, wherein the N target test strategies are in one-to-one correspondence with the N third storage positions.
In one possible example, in testing the first software to be tested by using the N target test policies to obtain a software test result corresponding to the first software to be tested, the program includes instructions specifically configured to perform the following steps:
Testing the first software to be tested by adopting an ith target test strategy to obtain an ith software part test result corresponding to the ith target test strategy;
after the test result of the ith software part is obtained, testing the first software to be tested by adopting an (i+1) th target test strategy to obtain the test result of the (i+1) th software part corresponding to the (i+1) th target test strategy;
stopping testing the first software to be tested until i=N to obtain N software part test results, wherein i is an increasing integer with an initial value of 1 and 1 as an interval;
and determining the N software part test results as software test results corresponding to the first software to be tested.
The embodiment of the application further provides a computer storage medium, where the computer storage medium is used to store a computer program, where the computer program is executed by a processor to implement part or all of the steps of any one of the methods described in the embodiments of the method, where the computer includes an electronic device.
Embodiments of the present application also provide a computer program product comprising a non-transitory computer-readable storage medium storing a computer program operable to cause a computer to perform some or all of the steps of any one of the methods described in the method embodiments above. The computer program product may be a software installation package, said computer comprising an electronic device.
It should be noted that, for simplicity of description, the foregoing method embodiments are all expressed as a series of action combinations, but it should be understood by those skilled in the art that the present application is not limited by the order of actions described, as some steps may be performed in other order or simultaneously in accordance with the present application. Further, those skilled in the art will also appreciate that the embodiments described in the specification are all preferred embodiments, and that the acts and modules referred to are not necessarily required in the present application.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and for parts of one embodiment that are not described in detail, reference may be made to related descriptions of other embodiments.
In the several embodiments provided in this application, it should be understood that the disclosed apparatus may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, such as the above-described division of units, merely a division of logic functions, and there may be additional manners of dividing in actual implementation, such as multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, or may be in electrical or other forms.
The units described above as separate components may or may not be physically separate, and components shown as units may or may not be physical units, may be located in one place, or may be distributed over a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units described above, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable memory. Based on such understanding, the technical solution of the present application may be embodied in essence or a part contributing to the prior art or all or part of the technical solution in the form of a software product stored in a memory, including several instructions for causing a computer device (which may be a personal computer, a server or a network device, etc.) to perform all or part of the steps of the above-mentioned method of the various embodiments of the present application. And the aforementioned memory includes: a U-disk, a Read-Only Memory (ROM), a random access Memory (RAM, random Access Memory), a removable hard disk, a magnetic disk, or an optical disk, or other various media capable of storing program codes.
Those of ordinary skill in the art will appreciate that all or a portion of the steps in the various methods of the above embodiments may be implemented by a program that instructs associated hardware, and the program may be stored in a computer readable memory, which may include: flash disk, read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.
The foregoing has outlined rather broadly the more detailed description of embodiments of the present application, wherein specific examples are provided herein to illustrate the principles and embodiments of the present application, the above examples being provided solely to assist in the understanding of the methods of the present application and the core ideas thereof; meanwhile, as those skilled in the art will have varying points in specific implementation and application scope in light of the ideas of the present application, the above description should not be construed as limiting the present application.
Claims (7)
1. A method of software testing, the method comprising:
acquiring first software to be tested and second software to be tested, wherein the first software to be tested is software to be tested after version updating, and the second software to be tested is software to be tested before version updating;
Determining N target demand types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, wherein N is an integer greater than 1; comprising the following steps: respectively acquiring a first program code set corresponding to the first software to be tested and a second program code set corresponding to the second software to be tested; determining N target program code segments of the first set of program code that are different from the second set of program code; acquiring N target program annotations corresponding to the N target program code segments, wherein the N target program annotations are in one-to-one correspondence with the N target program code segments; determining N first demand types according to a mapping relation between pre-stored program comments and demand types, wherein the N first demand types are in one-to-one correspondence with the N target program comments; acquiring N second requirement types corresponding to the first software to be tested, wherein the N second requirement types are input by a tester aiming at the N target program code segments; if the N second demand types are the same as the N first demand types, determining the N first demand types as N target demand types corresponding to the first software to be tested; if the N second demand types are different from the N first demand types, a demand type request carrying the N target program code segments is sent to a demand type platform, wherein the demand type request is used for indicating the demand type platform to feed back the demand type corresponding to each target program code segment in the N target program code segments; receiving N third requirement types sent by the requirement type platform aiming at the requirement type request; if the N third requirement types are the same as the N first requirement types and the N third requirement types are different from the N second requirements, determining the N first requirement types as N target requirement types corresponding to the first software to be tested; if the N third demand types are different from the N first demand types and the N third demand types are the same as the N second demand types, determining the N second demand types as N target demand types corresponding to the first software to be tested;
Inputting the N target demand types into a test strategy model for processing, and outputting N target test strategies, wherein the N target test strategies are in one-to-one correspondence with the N target demand types; comprising the following steps: inputting the N target demand types into a test strategy model, wherein the test strategy model comprises a mapping relation between the demand types and test strategy names and a mapping relation between the test strategy names and storage positions of the test strategies; determining N target test strategy names according to the mapping relation between the demand type and the test strategy names, wherein the N target test strategy names are in one-to-one correspondence with the N target demand types; determining N third storage positions according to the mapping relation between the test strategy names and the storage positions of the test strategies, wherein the N third storage positions are in one-to-one correspondence with the N target test strategy names; selecting N target test strategies corresponding to the N third storage positions from a plurality of test strategies included in a test strategy library, wherein the N target test strategies are in one-to-one correspondence with the N third storage positions;
and testing the first software to be tested by adopting the N target test strategies to obtain a software test result corresponding to the first software to be tested.
2. The method of claim 1, wherein the acquiring the first software under test and the second software under test comprises:
when a software testing request is detected, a first software version number and a second software version number which are included in the software testing request are obtained, wherein the first software version number is the version number of software to be tested after version updating, and the second software version number is the version number of the software to be tested before version updating;
respectively determining a first storage position corresponding to the first software version number and a second storage position corresponding to the second software version number according to a mapping relation between a pre-stored software version number and a storage position of software to be tested;
and respectively selecting the first software to be tested corresponding to the first storage position and the second software to be tested corresponding to the second storage position from a plurality of software to be tested included in the software library to be tested.
3. The method according to claim 2, wherein determining N target demand types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested includes:
respectively acquiring a first program code set corresponding to the first software to be tested and a second program code set corresponding to the second software to be tested;
Determining N target program code segments of the first set of program code that are different from the second set of program code;
n target program comments corresponding to the N target program code sections are obtained, and the N target programs are obtained
Sequence notes are in one-to-one correspondence with the N target program code segments;
and determining N target demand types corresponding to the first software to be tested according to a mapping relation between pre-stored program comments and demand types, wherein the N target demand types and the N target program comments are in one-to-one correspondence.
4. The method of claim 1, wherein the testing the first software to be tested using the N target test policies to obtain a software test result corresponding to the first software to be tested comprises:
testing the first software to be tested by adopting an ith target test strategy to obtain an ith software part test result corresponding to the ith target test strategy;
after the test result of the ith software part is obtained, testing the first software to be tested by adopting an (i+1) th target test strategy to obtain the test result of the (i+1) th software part corresponding to the (i+1) th target test strategy;
Stopping testing the first software to be tested until i=N to obtain N software part test results, wherein i is an increasing integer with an initial value of 1 and 1 as an interval;
and determining the N software part test results as software test results corresponding to the first software to be tested.
5. A software testing apparatus, the apparatus comprising:
the system comprises an acquisition unit, a storage unit and a control unit, wherein the acquisition unit is used for acquiring first software to be tested and second software to be tested, the first software to be tested is software to be tested after version updating, and the second software to be tested is software to be tested before version updating;
the determining unit is used for determining N target demand types corresponding to the first software to be tested according to the first software to be tested and the second software to be tested, wherein N is an integer greater than 1; comprising the following steps: respectively acquiring a first program code set corresponding to the first software to be tested and a second program code set corresponding to the second software to be tested; determining N target program code segments of the first set of program code that are different from the second set of program code; acquiring N target program annotations corresponding to the N target program code segments, wherein the N target program annotations are in one-to-one correspondence with the N target program code segments; determining N first demand types according to a mapping relation between pre-stored program comments and demand types, wherein the N first demand types are in one-to-one correspondence with the N target program comments; acquiring N second requirement types corresponding to the first software to be tested, wherein the N second requirement types are input by a tester aiming at the N target program code segments; if the N second demand types are the same as the N first demand types, determining the N first demand types as N target demand types corresponding to the first software to be tested; if the N second demand types are different from the N first demand types, a demand type request carrying the N target program code segments is sent to a demand type platform, wherein the demand type request is used for indicating the demand type platform to feed back the demand type corresponding to each target program code segment in the N target program code segments; receiving N third requirement types sent by the requirement type platform aiming at the requirement type request; if the N third requirement types are the same as the N first requirement types and the N third requirement types are different from the N second requirements, determining the N first requirement types as N target requirement types corresponding to the first software to be tested; if the N third demand types are different from the N first demand types and the N third demand types are the same as the N second demand types, determining the N second demand types as N target demand types corresponding to the first software to be tested;
The processing unit is used for inputting the N target demand types into the test strategy model for processing, outputting N target test strategies, and the N target test strategies are in one-to-one correspondence with the N target demand types; comprising the following steps: inputting the N target demand types into a test strategy model, wherein the test strategy model comprises a mapping relation between the demand types and test strategy names and a mapping relation between the test strategy names and storage positions of the test strategies; determining N target test strategy names according to the mapping relation between the demand type and the test strategy names, wherein the N target test strategy names are in one-to-one correspondence with the N target demand types; determining N third storage positions according to the mapping relation between the test strategy names and the storage positions of the test strategies, wherein the N third storage positions are in one-to-one correspondence with the N target test strategy names; selecting N target test strategies corresponding to the N third storage positions from a plurality of test strategies included in a test strategy library, wherein the N target test strategies are in one-to-one correspondence with the N third storage positions;
and the testing unit is used for testing the first software to be tested by adopting the N target testing strategies to obtain a software testing result corresponding to the first software to be tested.
6. An electronic device comprising a processor, a memory, a communication interface, and one or more programs stored in the memory and configured to be executed by the processor, the programs comprising instructions for performing part or all of the steps of the method of any of claims 1-4.
7. A computer readable storage medium for storing a computer program for execution by a processor to implement the method of any one of claims 1-4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910880742.0A CN110750447B (en) | 2019-09-18 | 2019-09-18 | Software testing method and related equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910880742.0A CN110750447B (en) | 2019-09-18 | 2019-09-18 | Software testing method and related equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110750447A CN110750447A (en) | 2020-02-04 |
| CN110750447B true CN110750447B (en) | 2023-07-25 |
Family
ID=69276647
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910880742.0A Active CN110750447B (en) | 2019-09-18 | 2019-09-18 | Software testing method and related equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110750447B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111538647A (en) * | 2020-04-15 | 2020-08-14 | 杭州迪普科技股份有限公司 | Equipment health state detection method and device and client |
| CN111930634B (en) * | 2020-09-09 | 2021-01-15 | 北京瑞莱智慧科技有限公司 | Model processing method, device, medium and computing equipment |
| CN113190433A (en) * | 2021-04-01 | 2021-07-30 | 联想凌拓科技有限公司 | Program testing method and device |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104461877A (en) * | 2014-11-27 | 2015-03-25 | 百度在线网络技术（北京）有限公司 | Software testing method and device |
| CN109101420A (en) * | 2018-07-20 | 2018-12-28 | 中国邮政储蓄银行股份有限公司 | Determine the method, apparatus and system, terminal of Test Strategy |
| CN109240929A (en) * | 2018-09-18 | 2019-01-18 | 百度在线网络技术（北京）有限公司 | Software quality prediction method, apparatus, terminal and computer readable storage medium |
| CN110096438A (en) * | 2019-04-12 | 2019-08-06 | 平安普惠企业管理有限公司 | Method for testing software and relevant apparatus |
| CN110134594A (en) * | 2019-04-19 | 2019-08-16 | 平安科技（深圳）有限公司 | Function test method, device and the computer equipment of application including account name |
| CN110134595A (en) * | 2019-04-19 | 2019-08-16 | 平安科技（深圳）有限公司 | Analysis method, device, computer equipment before SVN resource library test |
-
2019
- 2019-09-18 CN CN201910880742.0A patent/CN110750447B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104461877A (en) * | 2014-11-27 | 2015-03-25 | 百度在线网络技术（北京）有限公司 | Software testing method and device |
| CN109101420A (en) * | 2018-07-20 | 2018-12-28 | 中国邮政储蓄银行股份有限公司 | Determine the method, apparatus and system, terminal of Test Strategy |
| CN109240929A (en) * | 2018-09-18 | 2019-01-18 | 百度在线网络技术（北京）有限公司 | Software quality prediction method, apparatus, terminal and computer readable storage medium |
| CN110096438A (en) * | 2019-04-12 | 2019-08-06 | 平安普惠企业管理有限公司 | Method for testing software and relevant apparatus |
| CN110134594A (en) * | 2019-04-19 | 2019-08-16 | 平安科技（深圳）有限公司 | Function test method, device and the computer equipment of application including account name |
| CN110134595A (en) * | 2019-04-19 | 2019-08-16 | 平安科技（深圳）有限公司 | Analysis method, device, computer equipment before SVN resource library test |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110750447A (en) | 2020-02-04 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110750447B (en) | Software testing method and related equipment | |
| US10268820B2 (en) | Malware determination device, malware determination system, malware determination method, and program | |
| JP5669630B2 (en) | Test case generation method, program and system | |
| CN106716398B (en) | Visually distinguishing character strings for testing | |
| CN111399873A (en) | Model updating method and device | |
| CN109669853A (en) | Test report generation method and device, storage medium, electric terminal | |
| CN108154197A (en) | Realize the method and device that image labeling is verified in virtual scene | |
| CN104820676B (en) | A kind of method and device for judging version number's size | |
| CN109324956B (en) | System testing method, apparatus and computer readable storage medium | |
| CN106598637A (en) | Selective loading of components within a node to accelerate maintenance actions | |
| CN108664593A (en) | Data consistency verification method, device, storage medium and electronic equipment | |
| CN113672389A (en) | Server compatibility method, system, equipment and computer readable storage medium | |
| RU2018134303A (en) | DEVICE, SYSTEM AND METHOD FOR VERIFICATION OF INFORMATION RELATED TO A MEDICAL IMAGE | |
| CN110716869B (en) | Test case generation method and device, electronic equipment and computer readable storage medium | |
| CN109240928A (en) | A kind of test method, device, equipment and storage medium | |
| CN108874425A (en) | Configuration file update method, device, baseboard management controller and storage medium | |
| US9880813B2 (en) | RTE code generating method and apparatus performing the same | |
| KR101111244B1 (en) | Simulation system for verifying performance of gearing analytical equipment for naval vessel method thereof | |
| CN105656858B (en) | A kind of data-updating method and device | |
| CN112102837B (en) | Household electrical appliance and pickup detection method and device thereof | |
| JP6249803B2 (en) | Inverter test system | |
| CN113778902A (en) | Method and device for detecting coverage of test case | |
| CN106979794B (en) | Sensor testing method and device | |
| CN108345471B (en) | The method and detection device of detection device processing asynchronous event | |
| KR20160025881A (en) | Apparatus and method for detecting malicious shared library file |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |