CN116820946B - Method and device for automatically testing compatibility of target software - Google Patents
Method and device for automatically testing compatibility of target software Download PDFInfo
- Publication number
- CN116820946B CN116820946B CN202310723764.2A CN202310723764A CN116820946B CN 116820946 B CN116820946 B CN 116820946B CN 202310723764 A CN202310723764 A CN 202310723764A CN 116820946 B CN116820946 B CN 116820946B
- Authority
- CN
- China
- Prior art keywords
- target
- test
- retest
- mode
- software
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 324
- 238000000034 method Methods 0.000 title claims abstract description 144
- 238000013102 re-test Methods 0.000 claims abstract description 190
- 230000008569 process Effects 0.000 claims abstract description 102
- 238000004590 computer program Methods 0.000 claims description 6
- 238000012544 monitoring process Methods 0.000 claims description 6
- 238000012795 verification Methods 0.000 claims description 6
- 230000006978 adaptation Effects 0.000 claims description 4
- 238000013522 software testing Methods 0.000 abstract description 2
- 230000003287 optical effect Effects 0.000 description 6
- 238000012545 processing Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000009471 action Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 230000000644 propagated effect Effects 0.000 description 2
- 238000010998 test method Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005856 abnormality Effects 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 239000004065 semiconductor Substances 0.000 description 1
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/3688—Test management for test execution, e.g. scheduling of test suites
-
- 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/3664—Environments for testing or debugging software
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application relates to the technical field of software testing, in particular to a method and a device for automatically testing compatibility of target software, wherein the method comprises the steps of determining a target retest mode corresponding to the target software based on a current test process of the target software; when the generation of the test characteristics is detected, ending the current test process, and determining the test result of the current test process; determining target retest parameters according to the target retest mode and the test result; the target retest parameters are input according to the target retest mode to retest the target software, so that stability and accuracy of a test result are improved, unattended automatic test is realized, and the problems of low software and hardware compatibility test efficiency and difficulty in realizing automatic test are solved.
Description
Technical Field
The application relates to the technical field of software testing, in particular to a method and a device for automatically testing compatibility of target software.
Background
To determine whether the target software is operating properly on a particular soft, hard, and combination platform, compatibility testing of the target software on the platform is required.
In the past, manual testing is mostly adopted. The detection content of the software and hardware compatibility test comprises whether the software and hardware compatibility test can normally operate or not when combined with specific software, hardware or data in an operating environment, whether the software and hardware compatibility test is abnormal or not, and unstable factors exist in the test process, such as network state, data interaction link state and the like, which can cause the situation that a test case fails in the software and hardware compatibility test and influence the stability and accuracy of a test result.
At present, it is common practice to solve the problem by retesting the components involved in the failure case by a tester, and retesting the failure terms multiple times. Therefore, the realization of automatic retesting of failure terms is an effective means for improving test efficiency, stability and accuracy. However, since the execution state of the single test has no definite reference feature, the ending time of the single test cannot be detected, so that the next test cannot be started in time, and the automation of the software and hardware compatibility test is difficult.
Disclosure of Invention
In view of the problems described above, the present application has been made to provide a method and apparatus for automated testing of compatibility of target software that overcomes the problems described above or at least partially solves the problems described above, including:
a method of automated testing of compatibility of target software, comprising:
Determining a target retest mode corresponding to target software based on a current test process of the target software;
When the generation of the test characteristics is detected, ending the current test process, and determining the test result of the current test process;
determining target retest parameters according to the target retest mode and the test result;
and inputting the target retest parameters according to the target retest mode to retest the target software.
Preferably, the step of performing the test based on the current test process of the target software includes:
acquiring a test task input by a test user to the target software;
Performing adaptation verification on the target software and a test environment according to the test task;
if the test is matched, generating test summary information; wherein the test summary information includes at least one test component, the test component including at least one test case;
And inputting the test summary information into the current test process, and testing the target software.
Preferably, the inputting the test summary information into the current test process, and testing the target software includes:
Displaying the test summary information, retest mode options and retest times options to the test user; wherein the retest mode options comprise a full-scale retest mode, an error component retest mode and an error case retest mode;
Acquiring target test summary information, target retest mode and target retest times input by the test user;
And inputting the target test summary information, the target retest mode and the target retest times to the current test process, and testing the target software.
Preferably, when the test feature is generated, ending the current test process, and determining a test result of the current test process, including:
Monitoring output data of the current test process, and determining that the current test process is finished when the output data contains the data of the test characteristics; the data of the test feature comprises target time node data, target file data and target byte data in the target file data.
Preferably, the determining the target retest parameter according to the target retest mode and the test result includes:
when the target retest mode is a full-scale retest mode, taking the target test summary information input by the test user as the target retest parameter;
When the target retest mode is an error component retest mode, taking an error test component in a test result of the current test process as the target retest parameter;
And when the target retest mode is an error case retest mode, taking an error test case in a test result of the current test process as the target retest parameter.
Preferably, the inputting the target retest parameter according to the target retest mode retests the target software, before comprising:
determining the actual retest times corresponding to the retests, and inputting the target retest parameters according to the target retest mode to retest the target software when the actual retest times are smaller than or equal to the target retest times; otherwise, the test is ended.
Preferably, the method further comprises:
And obtaining a test result of the current test process and generating a test report.
There is also provided an apparatus for automated testing of compatibility of target software, the apparatus comprising:
The mode determining module is used for determining a target retest mode corresponding to the target software based on the current test process of the target software;
The process monitoring module is used for ending the current test process and determining the test result of the current test process when the test feature is generated;
the parameter determining module is used for determining target retest parameters according to the target retest mode and the test result;
And the retest executing module is used for retesting the target software according to the target retest mode input target retest parameters.
An apparatus comprising a processor, a memory and a computer program stored on the memory and capable of running on the processor, which when executed by the processor performs the steps of a method of automated testing of target software compatibility as described above.
A computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of a method of automated testing of compatibility of target software as described above.
The application has the following advantages:
In the embodiment of the application, the method is to carry out compatibility test on specific software, hardware or a combination platform thereof, such as product automation using Android or OpenHarmony operating systems, for target software, and the method determines a target retest mode corresponding to the target software based on the current test process of the target software; when the generation of the test characteristics is detected, ending the current test process, and determining the test result of the current test process; determining target retest parameters according to the target retest mode and the test result; and inputting the target retest parameters according to the target retest mode to retest the target software. Whether the current test process is finished or not can be monitored through preset test features, and a target retest mode corresponding to the target software and required target retest parameters are timely obtained, so that the target retest parameters are automatically input into the next test process according to the preset target retest mode after the current test process is finished, and specific test is carried out on the target software; by the method, stability and accuracy of a test result are improved, unattended automatic test is realized, and the problems that software and hardware compatibility test efficiency is low and automatic test is difficult to realize are solved.
Drawings
In order to more clearly illustrate the technical solutions of the present application, the drawings that are needed in the description of the present application will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.
FIG. 1 is a flow chart of steps of a method for automated testing of compatibility of target software according to one embodiment of the present application;
FIG. 2 is a block diagram of an apparatus for automated testing of compatibility of target software according to one embodiment of the present application;
Fig. 3 is a schematic structural diagram of a computer device according to an embodiment of the present application.
Detailed Description
In order that the manner in which the above recited objects, features and advantages of the present application are obtained will become more readily apparent, a more particular description of the application briefly described above will be rendered by reference to the appended drawings. It will be apparent that the described embodiments are some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Referring to fig. 1, a flowchart of steps in a method for automatically testing compatibility of target software according to an embodiment of the present application is shown; the method comprises the following steps:
s110, determining a target retest mode corresponding to target software based on a current test process of the target software;
S120, ending the current test process and determining a test result of the current test process when the generation of the test characteristics is detected;
S130, determining target retest parameters according to the target retest mode and the test result;
S140, retesting is carried out on the target software according to the target retesting parameter input by the target retesting mode.
In the embodiment of the application, the method is to carry out compatibility test on specific software, hardware or a combination platform thereof, such as carrying out compatibility test on product automation using an Android operating system, and the method is based on the current test process of the target software to determine the target retest mode corresponding to the target software; when the generation of the test characteristics is detected, ending the current test process, and determining the test result of the current test process; determining target retest parameters according to the target retest mode and the test result; and inputting the target retest parameters according to the target retest mode to retest the target software. Whether the current test process is finished or not can be monitored through preset test features, and a target retest mode corresponding to the target software and required target retest parameters are timely obtained, so that the target retest parameters are automatically input into the next test process according to the preset target retest mode after the current test process is finished, and specific test is carried out on the target software; by the method, stability and accuracy of a test result are improved, unattended automatic test is realized, and the problems that software and hardware compatibility test efficiency is low and automatic test is difficult to realize are solved.
In the following, a method for automatically testing compatibility of target software will be further described by the following examples.
And step S110, determining a target retest mode corresponding to the target software based on the current test process of the target software.
In one embodiment of the present application, the specific procedure before the "current test procedure based on the target software" in step S110 may be further described in conjunction with the following description.
As will be described in the following steps,
Acquiring a test task input by a test user to the target software;
Performing adaptation verification on the target software and a test environment according to the test task;
if the test is matched, generating test summary information; wherein the test summary information includes at least one test component, the test component including at least one test case;
And inputting the test summary information into the current test process, and testing the target software.
It can be understood that if the target software is not adapted to the test environment, the test is ended until the target software is adapted to the test environment, and then the test is performed.
It should be noted that, the current test process may be the first test or the retest after the last test. The current test procedure in this embodiment is the first test, and then the test environment verification needs to be performed, and the input test summary information needs to be relatively comprehensive. If the process is the retest process, the environment verification is not needed.
In this embodiment, the inputting the test summary information to the current test process, and testing the target software includes:
Displaying the test summary information, retest mode options and retest times options to the test user; wherein the retest mode options comprise a full-scale retest mode, an error component retest mode and an error case retest mode;
Acquiring target test summary information, target retest mode and target retest times input by the test user;
And inputting the target test summary information, the target retest mode and the target retest times to the current test process, and testing the target software.
It should be noted that, the full-scale retest mode is to test the target test summary information selected by the test user in the test summary information once every time of retesting; the error component retest mode is to retest the next test process for the error component tested by the current test process, and retest each case in the error component; the error case retest mode is to retest the next test process for the error case tested by the current test process.
When it is detected that the test feature is generated, the current test process is ended, and the test result of the current test process is determined, as in step S120.
In combination with the above embodiment, when it is detected that the test feature is generated, ending the current test process, and determining a test result of the current test process includes:
Monitoring output data of the current test process, and determining that the current test process is finished when the output data contains the data of the test characteristics; the data of the test feature comprises target time node data, target file data and target byte data in the target file data.
It should be noted that, in the embodiment of the present application, at least one test feature of a plurality of test features is used to monitor whether the current test process is finished. Specifically, when the target time node data is taken as test feature data, a tester can preset an end time node, the general end time node is set with 2-3 times of the duration of a normal test market, and when the current test process is carried out to the end time node and no abnormality occurs in the test process, the current test process is determined to be ended; when the target file data is used as test feature data, a tester designates a file name with an absolute path in advance, when the current test process is finished, a target file is generated according to the path, and when the target file is monitored, the current test process is determined to be finished; when the target byte data is taken as the test characteristic data, when the target file is monitored to contain the target byte data, the current test process is determined to be ended.
As described in the step S130, a target retest parameter is determined according to the target retest mode and the test result.
In an embodiment of the present application, the specific process of determining the target retest parameter according to the target retest mode and the test result in step S130 may be further described in conjunction with the following description.
When the target retest mode is a full-scale retest mode, taking target test summary information input by the test user as the target retest parameter;
When the target retest mode is an error component retest mode, taking an error test component in a test result of the current test process as the target retest parameter;
And when the target retest mode is an error case retest mode, taking an error test case in a test result of the current test process as the target retest parameter.
In step S140, retesting is performed on the target software according to the target retest parameter input in the target retest mode.
In an embodiment of the present application, the specific procedure before "input the target retest parameter according to the target retest mode to retest the target software" in step S140 may be further described in conjunction with the following description.
Determining the actual retest times corresponding to the retests, and inputting the target retest parameters according to the target retest mode to retest the target software when the actual retest times are smaller than or equal to the target retest times; otherwise, the test is ended.
It can be understood that, according to the target retest times set during the first test, if the actual retest times of the next test process are less than or equal to the target retest times, the next test process is performed.
In the embodiment of the application, the method further comprises the steps of obtaining the test result of the current test process and generating a test report. The generated test report may be exported in excel sheet and pdf document formats.
For the device embodiments, since they are substantially similar to the method embodiments, the description is relatively simple, and reference is made to the description of the method embodiments for relevant points.
Referring to fig. 2, a schematic structural diagram of an apparatus for automatically testing compatibility of target software according to an embodiment of the present application is shown, where the apparatus includes:
The mode determining module 110 is configured to determine a target retest mode corresponding to the target software based on a current test process where the target software is located;
the process monitoring module 120 is configured to end the current test process and determine a test result of the current test process when it is monitored that the test feature is generated;
A parameter determining module 130, configured to determine a target retest parameter according to the target retest mode and the test result;
and the retest executing module 140 is configured to retest the target software according to the target retest mode input the target retest parameter.
Referring to fig. 3, a schematic structural diagram of a computer device according to an embodiment of the present application may specifically include the following:
The computer device 12 described above is embodied in the form of a general purpose computing device, and the components of the computer device 12 may include, but are not limited to: one or more processors or processing units 16, a system memory 28, a bus 18 that connects the various system components, including the system memory 28 and the processing units 16.
Bus 18 represents one or more of several types of bus 18 structures, including a memory bus 18 or memory controller, a peripheral bus 18, an accelerated graphics port, a processor, or a local bus 18 using any of a variety of bus 18 architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus 18, micro channel architecture (MAC) bus 18, enhanced ISA bus 18, video Electronics Standards Association (VESA) local bus 18, and Peripheral Component Interconnect (PCI) bus 18.
Computer device 12 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by computer device 12 and includes both volatile and nonvolatile media, removable and non-removable media.
The system memory 28 may include computer system readable media in the form of volatile memory, such as Random Access Memory (RAM) 30 and/or cache memory 32. The computer device 12 may further include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only, storage system 34 may be used to read from or write to non-removable, nonvolatile magnetic media (commonly referred to as a "hard disk drive"). Although not shown in fig. 3, a magnetic disk drive for reading from and writing to a removable non-volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk such as a CD-ROM, DVD-ROM, or other optical media may be provided. In such cases, each drive may be coupled to bus 18 through one or more data medium interfaces. The memory may include at least one program product having a set (e.g., at least one) of program modules 42, the program modules 42 being configured to carry out the functions of embodiments of the application.
A program/utility 40 having a set (at least one) of program modules 42 may be stored in, for example, a memory, such program modules 42 including, but not limited to, an operating system, one or more application programs, other program modules 42, and program data, each or some combination of which may include an implementation of a network environment. Program modules 42 generally perform the functions and/or methods of the embodiments described herein.
The computer device 12 may also communicate with one or more external devices 14 (e.g., keyboard, pointing device, display 24, camera, etc.), one or more devices that enable a user to interact with the computer device 12, and/or any devices (e.g., network card, modem, etc.) that enable the computer device 12 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 22. Moreover, computer device 12 may also communicate with one or more networks such as a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network such as the Internet, through network adapter 20. As shown, network adapter 20 communicates with other modules of computer device 12 via bus 18. It should be appreciated that although not shown in fig. 3, other hardware and/or software modules may be used in connection with computer device 12, including, but not limited to: microcode, device drivers, redundant processing units 16, external disk drive arrays, RAID systems, tape drives, data backup storage systems 34, and the like.
The processing unit 16 executes various functional applications and data processing by running programs stored in the system memory 28, for example, implementing a method for automated testing of compatibility of target software provided by embodiments of the present application.
That is, the processing unit 16 realizes when executing the program: determining a target retest mode corresponding to target software based on a current test process of the target software; when the generation of the test characteristics is detected, ending the current test process, and determining the test result of the current test process; determining target retest parameters according to the target retest mode and the test result; and inputting the target retest parameters according to the target retest mode to retest the target software.
In an embodiment of the present application, the present application further provides a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements a method for automatically testing compatibility of target software as provided in all embodiments of the present application:
That is, the program is implemented when executed by a processor: determining a target retest mode corresponding to target software based on a current test process of the target software; when the generation of the test characteristics is detected, ending the current test process, and determining the test result of the current test process; determining target retest parameters according to the target retest mode and the test result; and inputting the target retest parameters according to the target retest mode to retest the target software.
Any combination of one or more computer readable media may be employed. The computer readable medium may be a computer-readable signal medium or a computer-readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Computer program code for carrying out operations of the present application may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider). In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.
While preferred embodiments of the present application have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiment and all such alterations and modifications as fall within the scope of the embodiments of the application.
Finally, it is further noted that relational terms such as first and second, and the like are used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal 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 terminal. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or terminal device that comprises the element.
The above description of the method and apparatus for automatically testing compatibility of target software provided by the present application has described specific examples, which are used to illustrate the principles and embodiments of the present application, and the above examples are only used to help understand the method and core ideas of the present application; meanwhile, as those skilled in the art will have variations in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.
Claims (8)
1. A method for automated testing of compatibility of target software, the method comprising:
Determining a target retest mode corresponding to target software based on a current test process of the target software;
When the generation of the test characteristics is detected, ending the current test process, and determining the test result of the current test process;
determining target retest parameters according to the target retest mode and the test result;
inputting the target retest parameters according to the target retest mode to retest the target software;
the current test process based on the target software comprises the following steps: acquiring a test task input by a test user to the target software; performing adaptation verification on the target software and a test environment according to the test task; if the test is matched, generating test summary information; wherein the test summary information includes at least one test component, the test component including at least one test case; inputting the test summary information into the current test process, and testing the target software;
The step of inputting the test summary information into the current test process to test the target software includes: displaying the test summary information, retest mode options and retest times options to the test user; wherein the retest mode options comprise a full-scale retest mode, an error component retest mode and an error case retest mode; acquiring target test summary information, target retest mode and target retest times input by the test user; and inputting the target test summary information, the target retest mode and the target retest times to the current test process, and testing the target software.
2. The method of claim 1, wherein when the test feature is detected to be generated, ending the current test process and determining a test result of the current test process comprises:
Monitoring output data of the current test process, and determining that the current test process is finished when the output data contains the data of the test characteristics; the data of the test feature comprises target time node data, target file data and target byte data in the target file data.
3. The method of claim 1, wherein determining the target retest parameter based on the target retest pattern and the test result comprises:
when the target retest mode is a full-scale retest mode, taking the target test summary information input by the test user as the target retest parameter;
When the target retest mode is an error component retest mode, taking an error test component in a test result of the current test process as the target retest parameter;
And when the target retest mode is an error case retest mode, taking an error test case in a test result of the current test process as the target retest parameter.
4. The method of claim 1, wherein retesting the target software according to the target retest mode input the target retest parameter comprises:
determining the actual retest times corresponding to the retests, and inputting the target retest parameters according to the target retest mode to retest the target software when the actual retest times are smaller than or equal to the target retest times; otherwise, the test is ended.
5. The method according to claim 1, wherein the method further comprises:
And obtaining a test result of the current test process and generating a test report.
6. An apparatus for automated testing of compatibility of target software, the apparatus comprising:
The mode determining module is used for determining a target retest mode corresponding to the target software based on the current test process of the target software;
The process monitoring module is used for ending the current test process and determining the test result of the current test process when the test feature is generated;
the parameter determining module is used for determining target retest parameters according to the target retest mode and the test result;
The retest execution module is used for retesting the target software according to the target retest mode input target retest parameters;
the current test process based on the target software comprises the following steps: acquiring a test task input by a test user to the target software; performing adaptation verification on the target software and a test environment according to the test task; if the test is matched, generating test summary information; wherein the test summary information includes at least one test component, the test component including at least one test case; inputting the test summary information into the current test process, and testing the target software;
The step of inputting the test summary information into the current test process to test the target software includes: displaying the test summary information, retest mode options and retest times options to the test user; wherein the retest mode options comprise a full-scale retest mode, an error component retest mode and an error case retest mode; acquiring target test summary information, target retest mode and target retest times input by the test user; and inputting the target test summary information, the target retest mode and the target retest times to the current test process, and testing the target software.
7. An apparatus comprising a processor, a memory, and a computer program stored on the memory and capable of running on the processor, which when executed by the processor, implements the method of any one of claims 1 to 5.
8. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the method according to any of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310723764.2A CN116820946B (en) | 2023-06-16 | 2023-06-16 | Method and device for automatically testing compatibility of target software |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310723764.2A CN116820946B (en) | 2023-06-16 | 2023-06-16 | Method and device for automatically testing compatibility of target software |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN116820946A CN116820946A (en) | 2023-09-29 |
| CN116820946B true CN116820946B (en) | 2024-05-14 |
Family
ID=88128612
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310723764.2A Active CN116820946B (en) | 2023-06-16 | 2023-06-16 | Method and device for automatically testing compatibility of target software |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116820946B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108459953A (en) * | 2017-02-22 | 2018-08-28 | 北京京东尚科信息技术有限公司 | test method and device |
| CN108572892A (en) * | 2017-03-14 | 2018-09-25 | 大唐移动通信设备有限公司 | A kind of off-line test method and apparatus based on PowerPC multi-core processors |
| KR20190084827A (en) * | 2018-01-09 | 2019-07-17 | 주식회사 한글과컴퓨터 | Method for automatic test of program compatibility and apparatus using the same |
| CN114968770A (en) * | 2022-05-11 | 2022-08-30 | 中国银行股份有限公司 | Automatic testing method, device, equipment and storage medium |
| CN116244186A (en) * | 2022-12-30 | 2023-06-09 | 统信软件技术有限公司 | Operating system test management method and device and computing equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20160077956A1 (en) * | 2014-09-11 | 2016-03-17 | Wipro Limited | System and method for automating testing of software |
-
2023
- 2023-06-16 CN CN202310723764.2A patent/CN116820946B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108459953A (en) * | 2017-02-22 | 2018-08-28 | 北京京东尚科信息技术有限公司 | test method and device |
| CN108572892A (en) * | 2017-03-14 | 2018-09-25 | 大唐移动通信设备有限公司 | A kind of off-line test method and apparatus based on PowerPC multi-core processors |
| KR20190084827A (en) * | 2018-01-09 | 2019-07-17 | 주식회사 한글과컴퓨터 | Method for automatic test of program compatibility and apparatus using the same |
| CN114968770A (en) * | 2022-05-11 | 2022-08-30 | 中国银行股份有限公司 | Automatic testing method, device, equipment and storage medium |
| CN116244186A (en) * | 2022-12-30 | 2023-06-09 | 统信软件技术有限公司 | Operating system test management method and device and computing equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN116820946A (en) | 2023-09-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110764945B (en) | Crash log processing method, device, equipment and storage medium | |
| CN111274154A (en) | Automatic testing method, device, equipment and storage medium | |
| WO2021244535A1 (en) | Vehicle software fault detection method, apparatus and device, and storage medium | |
| CN110990411B (en) | Data structure generation method and device, and calling method and device | |
| CN108874441B (en) | Board card configuration method, device, server and storage medium | |
| CN113572658A (en) | Vehicle control signal testing method and device, electronic equipment and storage medium | |
| CN111949545A (en) | Automatic testing method, system, server and storage medium | |
| CN109324968B (en) | System testing method and device | |
| CN111694684B (en) | Abnormal construction method and device of storage device, electronic device and storage medium | |
| CN111274130A (en) | Automatic testing method, device, equipment and storage medium | |
| CN110716843A (en) | System fault analysis processing method and device, storage medium and electronic equipment | |
| CN110888641B (en) | Script automatic generation method and device, server and storage medium | |
| CN116541270B (en) | Method and device for testing adaptation verification of operating system | |
| CN116820946B (en) | Method and device for automatically testing compatibility of target software | |
| CN111694724B (en) | Test method and device of distributed form system, electronic equipment and storage medium | |
| CN107562593A (en) | A kind of automated testing method and system for verifying internal memory ECC functions | |
| CN113238940B (en) | Interface test result comparison method, device, equipment and storage medium | |
| CN114706371A (en) | Complete vehicle network non-dormancy diagnosis method and device, electronic equipment and storage medium | |
| CN113656301A (en) | Interface testing method, device, equipment and storage medium | |
| CN113760696A (en) | Program problem positioning method and device, electronic equipment and storage medium | |
| CN113010114A (en) | Data processing method and device, computer equipment and storage medium | |
| CN114338846A (en) | Message testing method and device | |
| CN112307131B (en) | Equipment inspection method, system, electronic equipment and storage medium | |
| CN111240928B (en) | Automatic detection method, device, equipment and storage medium for equipment drive | |
| CN110020565B (en) | Probe information reading fault prompting method, device, server and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |