CN112148583A - Software testing method and system - Google Patents
Software testing method and system Download PDFInfo
- Publication number
- CN112148583A CN112148583A CN201910568195.2A CN201910568195A CN112148583A CN 112148583 A CN112148583 A CN 112148583A CN 201910568195 A CN201910568195 A CN 201910568195A CN 112148583 A CN112148583 A CN 112148583A
- Authority
- CN
- China
- Prior art keywords
- test
- environment module
- target
- test environment
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 70
- 238000013522 software testing Methods 0.000 title claims abstract description 34
- 238000012360 testing method Methods 0.000 claims abstract description 730
- 230000008569 process Effects 0.000 claims abstract description 19
- 238000011161 development Methods 0.000 claims description 120
- 238000004519 manufacturing process Methods 0.000 claims description 32
- 238000004088 simulation Methods 0.000 claims description 31
- 230000001419 dependent effect Effects 0.000 claims description 6
- 230000003993 interaction Effects 0.000 claims description 3
- 230000018109 developmental process Effects 0.000 claims 52
- 230000033772 system development Effects 0.000 claims 1
- 238000010586 diagram Methods 0.000 description 10
- 238000004590 computer program Methods 0.000 description 9
- 238000012545 processing Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 238000011056 performance test Methods 0.000 description 5
- 230000008901 benefit Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000000926 separation method Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000002159 abnormal effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000010354 integration Effects 0.000 description 1
- 239000000047 product Substances 0.000 description 1
- 230000009467 reduction Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 239000013589 supplement Substances 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/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/3668—Software testing
- G06F11/3672—Test management
- G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Computer Security & Cryptography (AREA)
- Debugging And Monitoring (AREA)
Abstract
The embodiment of the disclosure discloses a software testing method and system, relates to the technical field of software development, and mainly aims to avoid code version confusion in the software development testing process. The main technical scheme of the embodiment of the disclosure comprises the following steps: respectively deploying at least one testing environment module in each system related to software development; each testing environment module is respectively stored with codes of various versions developed by the system corresponding to the testing environment module; different kinds of test environment modules execute different tests; when any target test environment module in the test environment modules deployed by any system needs to execute a test, determining a target system related to the current test in each system; and executing the test corresponding to the target test environment module depending on the same version code aiming at the current test in the test environment module corresponding to the target test environment module in each target system.
Description
Technical Field
The embodiment of the disclosure relates to the technical field of software development, in particular to a software testing method and system.
Background
With the development of computer technology, more and more business processes need to be realized through computer software, and in order to ensure the quality and stability of the business realized by the computer software, codes related to the software need to be tested during software development.
At present, when software development of a service is realized, a large number of development devices are required to participate, and a developer corresponding to each development device develops at least part of software-related codes in the development device. When the test is performed on the code, the code in the relevant development equipment needs to be combined together to complete the test. However, when testing is performed, because the development progress of each development device is different, codes in different development devices may not be in the same version, which causes code version conflict, and causes code version confusion in the software testing process.
Disclosure of Invention
In view of this, embodiments of the present disclosure provide a software testing method and system, and mainly aim to avoid code version confusion during a software development testing process. The embodiment of the disclosure mainly provides the following technical scheme:
in a first aspect, an embodiment of the present disclosure provides a software testing method, where the method is used for a software development-related system to test software, and the method includes:
respectively deploying at least one testing environment module in each system related to software development; each testing environment module is respectively stored with codes of various versions developed by the system corresponding to the testing environment module; different kinds of test environment modules execute different tests;
when any target test environment module in the test environment modules deployed by any system needs to execute a test, determining a target system related to the current test in each system;
and executing the test corresponding to the target test environment module depending on the same version code aiming at the current test in the test environment module corresponding to the target test environment module in each target system.
In a second aspect, an embodiment of the present disclosure provides a software testing system, including:
n systems related to software development; at least one testing environment module is respectively deployed in each system related to software development; each testing environment module is respectively stored with codes of various versions developed by the system corresponding to the testing environment module; different kinds of test environment modules execute different tests;
each system is respectively used for determining a target system related to the current test in each system when any target test environment module in the test environment modules deployed by the system needs to execute the test; and executing the test corresponding to the target test environment module depending on the same version code aiming at the current test in the test environment module corresponding to the target test environment module in each target system.
In a third aspect, an embodiment of the present disclosure provides a storage medium, where the storage medium includes a stored program, and when the program runs, a device on which the storage medium is located is controlled to execute the software testing method according to the first aspect.
In a fourth aspect, embodiments of the present disclosure provide a human-computer interaction device, which includes a storage medium; and one or more processors, the storage medium coupled with the processors, the processors configured to execute program instructions stored in the storage medium; the program instructions when executed perform the software testing method of the first aspect.
By means of the above technical solution, the software testing method and system provided in the embodiments of the present disclosure deploy corresponding testing environment modules in each system related to software development, and store codes of each version developed by the system corresponding to each testing environment module. When any target test environment module in any system needs to execute the test, the target system related to the current test is determined in each system. And executing the test corresponding to the target test environment module depending on the code of the same version aiming at the current test in the test environment module corresponding to the target test environment module in each target system. Therefore, the embodiment of the disclosure realizes effective management of codes of each version on the basis of realizing separation of various test environments by using various test environment modules, and reduces conflicts of codes of each version when software is developed and tested, thereby improving the efficiency of software development and testing.
The foregoing description is only an overview of the embodiments of the present disclosure, and in order to make the technical means of the embodiments of the present disclosure more clearly understood, the embodiments of the present disclosure may be implemented in accordance with the content of the description, and in order to make the foregoing and other objects, features, and advantages of the embodiments of the present disclosure more clearly understood, the following detailed description of the embodiments of the present disclosure is given.
Drawings
Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are only for purposes of illustrating the preferred embodiments and are not to be construed as limiting the embodiments of the present disclosure. Also, like reference numerals are used to refer to like parts throughout the drawings. In the drawings:
FIG. 1 shows a flow chart of a software testing method provided by an embodiment of the present disclosure;
FIG. 2 shows a flow chart of another software testing method provided by embodiments of the present disclosure;
FIG. 3 shows a schematic diagram of a software testing process provided by an embodiment of the present disclosure;
fig. 4 shows a block diagram of a software testing system provided by an embodiment of the present disclosure.
Detailed Description
Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.
In a first aspect, an embodiment of the present disclosure provides a software testing method, where the method is used for a system related to software development to test software, and as shown in fig. 1, the method mainly includes:
101. respectively deploying at least one testing environment module in each system related to software development; each testing environment module is respectively stored with codes of various versions developed by the system corresponding to the testing environment module; different kinds of test environment modules execute different tests;
specifically, the systems described herein are systems related to software development, that is, there exist codes involved in the software development process, and the codes need to participate in the test of the software development process in order to ensure the quality of the software development. It should be noted that the system described herein may include, but is not limited to, a local system and an extraterritorial system. Local systems refer to development machines (e.g., desktop or laptop computers for personal development) and/or servers within an enterprise that are used by software developers. The local systems can communicate with each other based on intranets, Private lines, Virtual Private Networks (VPNs), and other intranets. The extraterritorial system refers to a system outside an intranet of an enterprise, and can be a business platform for providing codes related to software development for a local system or a platform for providing an external formal release service facing the internet for software.
Specifically, each system is deployed with at least one test environment module, and different systems may deploy the same type of test environment module or different types of test environment modules, which is not specifically limited herein. It should be noted that, in order to ensure that each testing environment module can smoothly execute the test and ensure the test is correct, when two or more testing environment modules are deployed in one system, a specific testing execution sequence exists among the testing environment modules. That is, for the same version of code, the test environment module located at the previous bit in the test execution sequence performs the corresponding test on the code, and when the test passes, the test environment module located at the next bit can perform the corresponding test on the code.
Specifically, during testing, in order to ensure the stability of the code required for testing, the code stored in each test environment module is required to be the code that the test environment module executes its corresponding test and is stored when the test passes.
Specifically, the at least one testing environment module may include, but is not limited to, at least one of a development environment module, a testing environment module, a multi-terminal testing environment module, a simulation environment module, a performance testing environment module, a pre-development environment module, and a production environment module. The development environment module, the test environment module, the multi-terminal test environment module and the simulation environment module are all test environment modules related to software independent development. The performance testing environment module, the pre-sending environment module and the production environment module are all testing environment modules related to software collaborative development.
It should be noted that, in order to meet different testing requirements, different testing environment modules execute different tests. Specifically, the development environment module is used for performing integration test on the software developer by using the associated codes of other people and the codes on the local system of the software developer in the software development stage. And the test environment module is used for executing the full-function test of the software, and the stored codes are the codes which are released to the test environment after the test of the development environment module is successfully completed. The multi-terminal testing environment module is used for testing each terminal in a scene of parallel multi-terminal testing. The simulation environment module is deployed in a production environment with wired scale reduction and copying and used for providing reliable dependence on offline development and testing, the simulation environment needs to be updated synchronously when a new production environment module is online every time, and the simulation environment module is not deployed independently and needs to be deployed together with the production environment module. The performance testing environment module is deployed in a production environment which is copied in a reduced proportion under a wire, is used for performing online performance testing, considers that the performance testing is performed in an abnormal state, and can export and backup a mirror image during the period of nonuse, so that resources in the system are released. The pre-release environment is deployed with a production environment which is copied in a reduced scale in a wired mode and used for release verification before formal release of software, and if the release is successful in the pre-release environment, the release test is passed, and the software can be formally released to the production environment. And the production environment is used for providing formal production service facing the Internet and the outside.
102. And when any target test environment module in the test environment modules deployed by any system needs to execute the test, determining the target system involved in the current test in each system.
In practical application, each system may initiate a test requirement, and execute a test in a test environment module deployed therein and meeting the test requirement, where the executed test is a target test environment module.
Specifically, when any target test environment module in the test environment modules deployed by any system needs to perform a test, in order to ensure the performability and integrity of the test, a system having a dependency relationship with the system is determined in each system according to the dependency relationship among the systems, and the determined systems are all determined as target systems related to the current test.
103. And executing the test corresponding to the target test environment module depending on the same version code aiming at the current test in the test environment module corresponding to the target test environment module in each target system.
Specifically, depending on the same version code for the current test in the test environment module corresponding to the target test environment module in each target system, the process of executing the test corresponding to the target test environment module is as follows: and extracting codes of the same version meeting the test requirements from the test environment modules corresponding to the target test environment modules in each target system, and executing the test corresponding to the target test environment modules based on the extracted codes of the same version and the codes of the same version in the target test environment modules.
It should be noted that each test environment module stores the code of each version developed by its corresponding system, and the stored code is the code that the test environment module executes its corresponding test and stores when the test passes. That is, the codes stored in the test environment module are all codes in a stable version state. Therefore, even if the target system develops a new version of code, the test can be completed depending on the code in the version stable state in each target system in the process of executing the test corresponding to the target test environment, so that the probability of version confusion of the code participating in the test process is ensured to be lower.
In the software testing method provided by the embodiment of the disclosure, the corresponding testing environment modules are respectively deployed in the systems related to software development, and the codes of the versions developed by the systems corresponding to the testing environment modules are respectively stored in the testing environment modules. When any target test environment module in any system needs to execute the test, the target system related to the current test is determined in each system. And executing the test corresponding to the target test environment module depending on the code of the same version aiming at the current test in the test environment module corresponding to the target test environment module in each target system. Therefore, the embodiment of the disclosure realizes effective management of codes of each version on the basis of realizing separation of various test environments by using various test environment modules, and reduces conflicts of codes of each version when software is developed and tested, thereby improving the efficiency of software development and testing.
In a second aspect, according to the method in the first aspect, another embodiment of the present disclosure further provides a software testing method, as shown in fig. 2, the method mainly includes:
201. respectively deploying at least one testing environment module in each system related to software development; each testing environment module is respectively stored with codes of various versions developed by the system corresponding to the testing environment module; different kinds of test environment modules perform different tests.
Specifically, the system exists in two forms: first, the system is only a local system. Second, the system includes a local system and an out-of-domain system. It should be noted that the number of systems is not particularly limited. For example, a personal development machine and a development server within an enterprise may both be local systems.
Specifically, each system is deployed with at least one test environment module, and different systems may deploy the same type of test environment module or different types of test environment modules, which is not specifically limited herein. Each test environment module performs testing of different development stages of the software. It should be noted that, in order to clearly distinguish the functions of each test environment module, the local system includes an online subsystem and an offline subsystem, the test environment modules related to software independent development are all deployed in the online subsystem, and the test environment modules related to software collaborative development are all deployed in the offline subsystem.
Illustratively, as shown in fig. 3, a development environment module, a test environment module and a simulation environment module deployed in the offline subsystem, and a performance test environment module, a pre-development environment module and a production environment module deployed in the online subsystem are deployed in the local system 30. The local system 31 is provided with a development environment module, a test environment module, a multi-terminal test environment module and a simulation environment module which are deployed in the online sub-system, and a performance test environment module, a pre-launch environment module and a production environment module which are deployed in the online sub-system. The local system 32 is disposed with a simulation environment module disposed in the offline subsystem, a performance test environment module, a pre-launch environment module, and a production environment module disposed in the online subsystem. A test environment module and a production environment module are deployed in the out-of-domain system 33. A development environment module, a test environment module, a multi-terminal test environment module, a simulation environment module, a performance test environment module, a pre-launch environment module, and a production environment module are deployed in the out-of-domain system 34.
202. And when any target test environment module in the test environment modules deployed by any system needs to execute the test, determining the target system involved in the current test in each system.
Specifically, each system may initiate a test requirement and execute a test in a test environment module deployed therein, which satisfies the test requirement, so that the target test environment module has at least the following forms:
first, the target test environment module is any test environment module related to software independent development in the local system.
Secondly, the target test environment module is any test environment module related to software collaborative development in the local system.
Thirdly, the target test environment module is any test environment module related to software collaborative development in the system outside the domain.
Specifically, after the target test environment module is determined, in order to ensure the performability and integrity of the test, systems having a dependency relationship with the system where the target test environment module is located are determined in each system according to the dependency relationship among the systems, and the determined systems are all determined as target systems related to the current test.
203. And executing the test corresponding to the target test environment module depending on the same version code aiming at the current test in the test environment module corresponding to the target test environment module in each target system. When there is a problem in executing the test corresponding to the target test environment, executing step 204; step 205 is performed when a test pass corresponding to the target test environment is performed.
Specifically, depending on the target system and the target test environment module, at least the following tests are performed in the target system and depending on the target code in the test environment module corresponding to the target test environment module:
first, when the target test environment is a test environment module related to software independent development and the target systems are all local systems, executing the test corresponding to the target test environment module depending on the same version code for the current test in the test environment module corresponding to the target test environment module in each target system may include the following steps: and executing a test related to the independent development of the software corresponding to the target test environment module depending on the same version code for the current test in the test environment module corresponding to the target test environment module in each target system. In this way, each development machine can cooperate with other development machines to complete the test in the software development process, so that software developers can flexibly arrange the test based on the development progress of the software developers.
Specifically, the test environment module related to software independent development described herein includes: a development environment module, a test environment module, and a simulation environment module, and the target test environment module is any one of these modules. It should be noted that the simulated environment module stores the code that passes the test and is in the stable version state, that is, the code under the new version development and the code under the stable version state are decoupled from each other, so that the code under the stable version state stored in the simulated environment module is not affected no matter whether the software development is in the new version software development state. Therefore, when the target test environment is a development environment module, a test environment module, or a simulation test environment module, the test related to the independent development of the software corresponding to the target test environment module is executed depending on the same version code for the current test in the simulation environment module corresponding to the target test environment module in each target system.
For example, as shown in fig. 3, when the target test environment module is a module related to software independent development (any one of a development environment module, a test environment module, and a simulation environment module) in an offline subsystem in the local system 30, the determined target system is the local system 31 (the local system 31 depends on the local system 30), and then, as can be seen from the trajectory a, the test related to software independent development corresponding to the target test environment module is executed depending on the same version code for the current test in the simulation environment module corresponding to the target test environment module in the local system 31.
For example, as shown in fig. 3, when the target test environment module is a module related to software independent development (any one of a development environment module, a test environment module, a multi-terminal test module, and a simulation environment module) in an offline subsystem in the local system 31, the determined target system is the local system 32 (the local system 31 is dependent on the local system 30), and then, as can be seen from the trace B, the test related to software independent development corresponding to the target test environment module is executed depending on the same version of code for the current test in the simulation environment module corresponding to the target test environment module in the local system 32.
Second, when the target test environment is a test environment module related to software collaborative development and the target systems are all local systems, executing the test corresponding to the target test environment module depending on the same version code for the current test in the test environment module corresponding to the target test environment module in each target system may include the following steps: and executing the test related to the local collaborative development of the software corresponding to the target test environment module depending on the same version code aiming at the current test in the test environment module corresponding to the target test environment module in each target system.
Thirdly, when the target test environment is a test environment module related to software independent development and the target system includes a local system and an off-domain system, executing the test corresponding to the target test environment module depending on the same version code for the current test in the test environment module corresponding to the target test environment module in each target system may include the following steps: and executing a test related to software independent development corresponding to the target test environment module depending on the same-version code for the current test in the test environment module corresponding to the target test environment module in the local system in each target system and depending on the same-version code for the current test in the test environment module corresponding to the target test environment module in the off-domain system in each target system.
Fourth, when the target test environment is a test environment module related to software independent development and the target system includes an out-of-domain system, executing the test corresponding to the target test environment module depending on the same version code for the current test in the test environment module corresponding to the target test environment module in each target system may include the following steps: and executing a test related to independent software development corresponding to the target test environment module depending on the same-version code for the current test in the test environment module corresponding to the target test environment module in the out-of-domain system in each target system. It should be noted that, in the independent software development stage, the method can find errors in the software development process in time by testing based on the related codes provided by the system outside the domain, thereby improving the convenience and efficiency of software development.
For example, as shown in fig. 3, when the target test environment module is a module related to software independent development (any one of a development environment module, a test environment module, a multi-terminal test module, and a simulation environment module) in an offline subsystem in the local system 31, the determined target system is the out-of-domain system 33 (the local system 31 is dependent on the out-of-domain system 33), and then, as can be seen from the trajectory C, the test related to software independent development corresponding to the target test environment module is executed depending on the same version code for the current test in the test environment module corresponding to the target test environment module in the out-of-domain system 33.
For example, as shown in fig. 3, when the target test environment module is a module (any one of a performance test environment module, a pre-launch environment module, and a production environment module) related to software collaborative development in an offline subsystem in the local system 31, and the determined target system is the out-of-domain system 33 (the local system 31 is dependent on the out-of-domain system 33), it can be known from the trajectory D that a test related to software independent development corresponding to the target test environment module is executed depending on the same version of code for the current test in the production environment module corresponding to the target test environment module in the out-of-domain system 33. This situation depends on the production environment in the system outside the domain no matter what the target test environment module is related to the software co-development, so this kind of test can improve the quality and reliability of the software development.
Fifth, when the target test environment is a test environment module related to software collaborative development and the target system includes an out-of-domain system, executing the test corresponding to the target test environment module depending on the same version code for the current test in the test environment module corresponding to the target test environment module in each target system may include the following steps: and executing the test related to the software collaborative development corresponding to the target test environment module by depending on the same version code aiming at the current test in the test environment module corresponding to the target test environment in the out-of-domain system in each target system.
Sixth, when the target test environment is a test environment module related to software collaborative development in an out-of-domain system and the target system includes a local system, executing the test corresponding to the target test environment module depending on the same version code for the current test in the test environment module corresponding to the target test environment module in each target system may include the following steps: and executing a test related to the cooperative development outside the software domain corresponding to the target test environment module depending on the same-version code aiming at the current test in the test environment module corresponding to the target test environment module in a local system in each target system.
Specifically, the test environment module related to software collaborative development includes: the system comprises a performance testing environment module, a pre-sending environment module and a production environment module; the production environment module stores codes in a publishable version state. Because the production environment module completely simulates the environment of product release, the quality and reliability of codes after the production environment module executes tests are high, and the codes can be released and used. And when the target test environment is an environment test environment module related to software collaborative development in the system outside the domain, executing a test related to software collaborative development outside the domain corresponding to the target test environment module depending on the same-version code aiming at the current test in the production environment module corresponding to the target test environment module in each target system.
For example, as shown in fig. 3, when the target test environment module is a line production environment module in the out-of-domain system 34, the determined target system is the local system 31 (the local system 31 depends on the out-of-domain system 34), and then, as can be seen from the trace E, a test related to software independent development corresponding to the target test environment module "production environment module" is executed depending on the same version code for the current test in the production environment module corresponding to the target test environment module "production environment module" in the local system 31. In this case, no matter what kind of module of the target test environment is related to the software collaborative development, the target test environment module depends on the production environment in the local system, so the test can improve the quality and reliability of the software development.
In addition, no matter what system the target system is, what module the target test environment module is, when the test corresponding to the target test environment module is executed depending on the same version code for the current test in the test environment module corresponding to the target test environment in each target system, the following steps are executed in order to ensure the test sequence: judging whether the same version code aiming at the current test exists in the test environment module corresponding to the target test environment in each target system; if the codes exist, the codes which are in the same version and are in the stable state exist in all the target systems, and the codes of the same version aiming at the current test can finish the test corresponding to the target test environment, the codes of the same version aiming at the current test are extracted from the test environment modules corresponding to the target test environment in all the target systems, and the extracted codes of the same version aiming at the current test are utilized to execute the test corresponding to the target test environment. If the same version code aiming at the current test does not exist in the test environment module corresponding to the target test environment module in part of the target system, the code required by the test is incomplete, the test cannot be completed, and prompt information that the test cannot be executed is sent out, so that software developers can perform code supplement processing according to the prompt information so as to complete the test in time. The prompt information carries an identifier of the test environment module without the target code and an identifier of a target system where the test environment module without the same version code for the current test is located.
204. Generating a test report; and the test report comprises code line information with errors.
Specifically, when there is a problem in executing a test corresponding to the target test environment, it is indicated that there are errors in the same version code for the current test, and in order to ensure the quality and stability of software, it is necessary to timely eliminate these errors, and then a test report is generated. The test report comprises the information of the code lines with errors, and a software developer can timely perform debugging processing based on the information of the code lines with errors.
205. And sending a code corresponding to the current test in the target test environment module to a test environment module positioned next in the test execution sequence for the next test environment module to execute the corresponding test.
Specifically, when a test corresponding to the target test environment is executed, it indicates that there is no error in the same version code of the current test, and the quality and stability of the software are high, and in order to advance the software development process in time, the code corresponding to the current test needs to be sent to the test environment module located next in the test execution sequence, so that the next test environment module executes the corresponding test. In addition, it should be noted that, when the test environment module is pushed to the next test environment module, in order to make the software developer know the test progress in time, a test progress reminder may be sent to the software developer.
In a third aspect, according to the method shown in fig. 1 or fig. 2, another embodiment of the present disclosure further provides a software testing system, as shown in fig. 4, the system mainly includes:
n software development-related systems 40; at least one test environment module is respectively deployed in each system 40 related to software development; each of the test environment modules stores the code of each version developed by the system 40 corresponding to the test environment module; different kinds of test environment modules execute different tests; n is more than or equal to 1
Each of the systems 40 is configured to determine, in each system, a target system related to a current test when any target test environment module in the test environment modules deployed by the system itself needs to perform the test; and executing the test corresponding to the target test environment module depending on the same version code aiming at the current test in the test environment module corresponding to the target test environment module in each target system.
In the software testing system provided by the embodiment of the disclosure, the corresponding testing environment modules are respectively deployed in the systems related to software development, and the codes of the versions developed by the systems corresponding to the testing environment modules are respectively stored in the testing environment modules. When any target test environment module in any system needs to execute the test, the target system related to the current test is determined in each system. And executing the test corresponding to the target test environment module depending on the code of the same version aiming at the current test in the test environment module corresponding to the target test environment module in each target system. Therefore, the embodiment of the disclosure realizes effective management of codes of each version on the basis of realizing separation of various test environments by using various test environment modules, and reduces conflicts of codes of each version when software is developed and tested, thereby improving the efficiency of software development and testing.
In some embodiments, the system 40 comprises a local system; the local system is provided with a test environment module related to independent software development and a test environment module related to software collaborative development;
the local system is used for executing the test which is corresponding to the target test environment module and is related to the independent development of the software depending on the code of the same version aiming at the current test in the test environment module corresponding to the target test environment module in each target system;
or, the local system is configured to execute a test related to local collaborative development of software corresponding to the target test environment, depending on the same-version code for the current test in the test environment module corresponding to the target test environment module in each target system.
In some embodiments, the test environment module related to software independent development comprises: the system comprises a development environment module, a test environment module and a simulation environment module; the simulation environment module is stored with a code which passes the test and is in a stable version state;
and the local system is used for executing the test which corresponds to the target test environment module and is related to the independent development of the software depending on the code of the same version aiming at the current test in the simulation environment module which corresponds to the target test environment module in each target system.
In some embodiments, the local system comprises: a first local system, a second local system, and a third local system that is dependent on the second local system;
and the first local system and the second local system are respectively used for executing the test which is corresponding to the target test environment module and is related to the independent development of the software, depending on the same version code aiming at the current test in the simulation environment module corresponding to the target test environment module in the third local system.
Illustratively, as shown in fig. 3, the local system 32 is a third local system, and the local system 31 is a second local system. The local system 32 is dependent on the local system 31. When the target test environment module is a module (any one of a development environment module, a test environment module, a multi-terminal test module, and a simulation environment module) related to software independent development in the offline subsystem of the local system 31, if the determined target system is the local system 32 (the local system 31 depends on the local system 30), it can be known from the trajectory B that the test related to software independent development corresponding to the target test environment module is executed depending on the same version code for the current test in the simulation environment module corresponding to the target test environment module in the local system 32.
In some embodiments, the system includes a local system and an out-of-domain system; the local system is provided with a test environment module related to independent software development and a test environment module related to software collaborative development; the system outside the domain is provided with a test environment module related to software collaborative development;
the out-of-domain system is configured to execute a test related to independent software development corresponding to the target test environment module, depending on the same-version code for a current test in the test environment module corresponding to the target test environment module in a local system in each target system, and depending on the same-version code for the current test in the test environment module corresponding to the target test environment module in the first out-of-domain system in each target system.
In some embodiments, the system includes a local system and an out-of-domain system; the local system is provided with a test environment module related to independent software development and a test environment module related to software collaborative development; the system outside the domain is provided with a test environment module related to software collaborative development;
and the out-of-domain system is used for executing the test which corresponds to the target test environment module and is related to the software out-of-domain collaborative development by depending on the same version code aiming at the current test in the test environment module corresponding to the target test environment module in the local system in each target system.
In some embodiments, the local system includes an inline subsystem and an offline subsystem; a test environment module related to software independent development is deployed in the online subsystem; and a test environment module related to software collaborative development is deployed in the offline subsystem.
In some embodiments, the N systems related to software development are all systems involved in a development process of a car machine system.
In some embodiments, each of the systems is further configured to determine whether a same version code for a current test exists in a test environment module corresponding to the target test environment module in each target system; if the test environment module exists, extracting the same version code aiming at the current test from the test environment module corresponding to the target test environment in each target system, and executing the test corresponding to the target test environment module by utilizing the extracted same version code aiming at the current test; otherwise, sending out prompt information that the test is not executable; the prompt information carries an identifier of a test environment module without a code of the same version aiming at the current test and an identifier of a target system where the test environment module without the code of the same version aiming at the current test is located.
In some embodiments, each of the systems is further configured to generate a test report when there is a problem in executing the test corresponding to the target test environment module; and the test report comprises code line information with errors.
In some embodiments, each of the systems, when a test corresponding to the target test environment module passes, sends a code corresponding to a current test in the target test environment module to a test environment module next in the test execution sequence, so that the next test environment module executes a corresponding test.
The software testing system provided by the embodiment of the third aspect may be configured to execute the software testing method provided by the embodiment of the first aspect or the second aspect, and the related meanings and specific embodiments may be referred to in the description of the embodiment of the first aspect or the second aspect, and are not described in detail here.
In a fourth aspect, an embodiment of the present disclosure provides a storage medium, where the storage medium includes a stored program, and when the program runs, a device in which the storage medium is located is controlled to execute the software testing method according to the first aspect or the second aspect.
The storage medium may include volatile memory in a computer readable medium, Random Access Memory (RAM) and/or nonvolatile memory such as Read Only Memory (ROM) or flash memory (flash RAM), and the memory includes at least one memory chip.
In a fifth aspect, embodiments of the present disclosure provide a human-computer interaction device, which includes a storage medium; and one or more processors, the storage medium coupled with the processors, the processors configured to execute program instructions stored in the storage medium; the program instructions when executed perform the software testing method of the first aspect or the second aspect.
In the foregoing embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
As will be appreciated by one skilled in the art, embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the disclosure. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). The memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in the process, method, article, or apparatus that comprises the element.
As will be appreciated by one skilled in the art, embodiments of the present disclosure may be provided as a method, system, or computer program product. Accordingly, embodiments of the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, embodiments of the present disclosure may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and so forth) having computer-usable program code embodied therein.
The above are merely examples of the present application and are not intended to limit the present application. Various modifications and changes may occur to those skilled in the art. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.
Claims (23)
1. A software testing method for a software development-related system to test software, the method comprising:
respectively deploying at least one testing environment module in each system related to software development; each testing environment module is respectively stored with codes of various versions developed by the system corresponding to the testing environment module; different kinds of test environment modules execute different tests;
when any target test environment module in the test environment modules deployed by any system needs to execute a test, determining a target system related to the current test in each system;
and executing the test corresponding to the target test environment module depending on the same version code aiming at the current test in the test environment module corresponding to the target test environment module in each target system.
2. The method of claim 1, wherein at least one test environment module deployed in the system comprises a set test execution order;
the test execution sequence is as follows: and aiming at the codes of the same version, executing corresponding tests on the codes by the test environment module positioned at the previous bit in the test execution sequence, and executing corresponding tests on the codes by the test environment module positioned at the next bit when the tests are passed.
3. The method of claim 2, wherein each of the test environment modules stores code that the test environment module performs its corresponding test and stores when the test passes.
4. The method of claim 1, wherein the system comprises a local system; the local system is provided with a test environment module related to independent software development and a test environment module related to software collaborative development;
when the target testing environment module is a testing environment module related to software independent development, executing a test corresponding to the target testing environment module by relying on the same version code for a current test in the testing environment module corresponding to the target testing environment module in each target system, including:
and executing a test related to the independent software development corresponding to the target test environment module depending on the same version code for the current test in the test environment module corresponding to the target test environment module in each target system.
5. The method of claim 4, wherein the test environment module associated with software independent development comprises: the system comprises a development environment module, a test environment module and a simulation environment module; the simulation environment module is stored with a code which passes the test and is in a stable version state;
when the target testing environment module is a development environment module, a testing environment module or a simulation environment module, depending on the same version code for the current test in the testing environment module corresponding to the target testing environment module in each target system, executing a test related to the independent software development corresponding to the target testing environment module, including:
and executing the test related to the independent software development corresponding to the target test environment module depending on the same version code aiming at the current test in the simulation environment module corresponding to the target test environment module in each target system.
6. The method of claim 1, wherein the system comprises a local system; the local system is provided with a test environment module related to independent software development and a test environment module related to software collaborative development;
when the target testing environment module is a testing environment module related to software collaborative development, executing a test corresponding to the target testing environment module by relying on the same version code for a current test in the testing environment module corresponding to the target testing environment module in each target system, including:
and executing the test related to the local collaborative development of the software corresponding to the target test environment by depending on the same version code aiming at the current test in the test environment module corresponding to the target test environment module in each target system.
7. The method of claim 1, wherein the system comprises a local system and an out-of-domain system; the local system is provided with a test environment module related to independent software development and a test environment module related to software collaborative development; the system outside the domain is provided with a test environment module related to software collaborative development;
when the target testing environment module is a testing environment module related to software independent development and a target system includes a local system and an off-domain system, executing a test corresponding to the target testing environment module depending on a same version code for a current test in the testing environment module corresponding to the target testing environment module in each target system, including:
and executing a test related to software independent development corresponding to the target test environment module depending on the same-version code for the current test in the test environment module corresponding to the target test environment module in a local system in each target system and depending on the same-version code for the current test in the test environment module corresponding to the target test environment module in an off-domain system in each target system.
8. The method of claim 1, wherein the system comprises a local system and an out-of-domain system; the local system is provided with a test environment module related to independent software development and a test environment module related to software collaborative development; the system outside the domain is provided with a test environment module related to software collaborative development;
when the target testing environment module is a testing environment module related to software collaborative development in an out-of-domain system and a target system includes a local system, executing a test corresponding to the target testing environment module depending on a same version code for a current test in a testing environment module corresponding to the target testing environment module in each target system, including:
and executing a test related to the cooperative development outside the software domain corresponding to the target test environment module depending on the same-version code aiming at the current test in the test environment module corresponding to the target test environment module in a local system in each target system.
9. The method of claim 8, wherein the test environment module related to software collaborative development comprises: at least one of a performance testing environment module, a pre-launch environment module and a production environment module; the production environment module stores codes in a publishable version state;
when the target testing environment module is an environment testing environment module related to software collaborative development in an out-of-domain system, depending on a local system in each target system, a same-version code for a current test in a testing environment module corresponding to the target testing environment module, and executing a test related to software out-of-domain collaborative development corresponding to the target testing environment module, including:
and executing the test related to the cooperative development outside the software domain corresponding to the target test environment module according to the same version code aiming at the current test in the production environment module corresponding to the target test environment module in each target system.
10. The method of any one of claims 4, 6, 7 and 8, wherein the local system comprises an inline subsystem and an offline subsystem; a test environment module related to software independent development is deployed in the online subsystem; and a test environment module related to software collaborative development is deployed in the offline subsystem.
11. The method of claim 1, wherein the executing the test corresponding to the target test environment module in dependence on the same version code for the current test in the test environment module corresponding to the target test environment module in each target system comprises:
judging whether the same version codes for the current test exist in the test environment modules corresponding to the target test environment modules in each target system;
if the test environment module exists, extracting the same version code aiming at the current test from the test environment module corresponding to the target test environment in each target system, and executing the test corresponding to the target test environment module by utilizing the extracted same version code aiming at the current test;
otherwise, sending out prompt information that the test is not executable; the prompt information carries an identifier of a test environment module without a code of the same version aiming at the current test and an identifier of a target system where the test environment module without the code of the same version aiming at the current test is located.
12. The method of claim 1, wherein after executing the test corresponding to the target test environment module in dependence on the same version code for the current test in the test environment module corresponding to the target test environment module in each target system, the method further comprises:
when the test corresponding to the target test environment module is executed and has a problem, generating a test report; and the test report comprises code line information with errors.
13. The method of claim 1, wherein at least one test environment module deployed in the system has a particular test execution order; after the executing the test corresponding to the target test environment module by the same version code for the current test in the test environment module corresponding to the target test environment module in each target system, the method further includes:
and when the test corresponding to the target test environment module passes, sending a code corresponding to the current test in the target test environment module to a test environment module positioned next in the test execution sequence for the next test environment module to execute the corresponding test.
14. A software testing system, comprising: n systems related to software development; at least one testing environment module is respectively deployed in each system related to software development; each testing environment module is respectively stored with codes of various versions developed by the system corresponding to the testing environment module; different kinds of test environment modules execute different tests;
each system is respectively used for determining a target system related to the current test in each system when any target test environment module in the test environment modules deployed by the system needs to execute the test; and executing the test corresponding to the target test environment module depending on the same version code aiming at the current test in the test environment module corresponding to the target test environment module in each target system.
15. The software testing system of claim 14, wherein the system comprises a local system; the local system is provided with a test environment module related to independent software development and a test environment module related to software collaborative development;
the local system is used for executing the test which is corresponding to the target test environment module and is related to the independent development of the software depending on the code of the same version aiming at the current test in the test environment module corresponding to the target test environment module in each target system;
or, the local system is configured to execute a test related to local collaborative development of software corresponding to the target test environment, depending on the same-version code for the current test in the test environment module corresponding to the target test environment module in each target system.
16. The software testing system of claim 15, wherein the test environment module associated with software independent development comprises: the system comprises a development environment module, a test environment module and a simulation environment module; the simulation environment module is stored with a code which passes the test and is in a stable version state;
and the local system is used for executing the test which corresponds to the target test environment module and is related to the independent development of the software depending on the code of the same version aiming at the current test in the simulation environment module which corresponds to the target test environment module in each target system.
17. The software testing system of claim 16, wherein the local system comprises: a first local system, a second local system, and a third local system that is dependent on the second local system;
and the first local system and the second local system are respectively used for executing the test which is corresponding to the target test environment module and is related to the independent development of the software, depending on the same version code aiming at the current test in the simulation environment module corresponding to the target test environment module in the third local system.
18. The software testing system of claim 14, wherein the system comprises a local system and an off-domain system; the local system is provided with a test environment module related to independent software development and a test environment module related to software collaborative development; the system outside the domain is provided with a test environment module related to software collaborative development;
the out-of-domain system is configured to execute a test related to independent software development corresponding to the target test environment module, depending on the same-version code for a current test in the test environment module corresponding to the target test environment module in a local system in each target system, and depending on the same-version code for the current test in the test environment module corresponding to the target test environment module in the first out-of-domain system in each target system.
19. The software testing system of claim 14, wherein the system comprises a local system and an off-domain system; the local system is provided with a test environment module related to independent software development and a test environment module related to software collaborative development; the system outside the domain is provided with a test environment module related to software collaborative development;
and the out-of-domain system is used for executing the test which corresponds to the target test environment module and is related to the software out-of-domain collaborative development by depending on the same version code aiming at the current test in the test environment module corresponding to the target test environment module in the local system in each target system.
20. The method of any one of claims 15-19, wherein the local system includes an online subsystem and an offline subsystem; a test environment module related to software independent development is deployed in the online subsystem; and a test environment module related to software collaborative development is deployed in the offline subsystem.
21. The software testing system of any one of claims 14-19, wherein the N software development-related systems are all systems involved in a car machine system development process.
22. A storage medium comprising a stored program, wherein the apparatus on which the storage medium is located is controlled to perform the software testing method of any one of claims 1 to 13 when the program is run.
23. A human-computer interaction device, characterized in that the device comprises a storage medium; and one or more processors, the storage medium coupled with the processors, the processors configured to execute program instructions stored in the storage medium; the program instructions when executed perform the software testing method of any one of claims 1 to 13.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910568195.2A CN112148583A (en) | 2019-06-27 | 2019-06-27 | Software testing method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910568195.2A CN112148583A (en) | 2019-06-27 | 2019-06-27 | Software testing method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112148583A true CN112148583A (en) | 2020-12-29 |
Family
ID=73869593
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910568195.2A Pending CN112148583A (en) | 2019-06-27 | 2019-06-27 | Software testing method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112148583A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112860540A (en) * | 2021-01-14 | 2021-05-28 | 中国农业银行股份有限公司 | Software version upgrade test management and control system and method |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150082279A1 (en) * | 2013-09-13 | 2015-03-19 | Sap Ag | Software testing system and method |
| CN104765692A (en) * | 2015-04-29 | 2015-07-08 | 北京嘀嘀无限科技发展有限公司 | Method and equipment for automatically testing software |
| CN106407100A (en) * | 2015-07-29 | 2017-02-15 | 中兴通讯股份有限公司 | Method and apparatus for realizing continuous integration testing |
| CN106717118A (en) * | 2014-09-29 | 2017-05-24 | 飞利浦灯具控股公司 | Systems and methods for managing environmental conditions |
| CN107885658A (en) * | 2017-10-31 | 2018-04-06 | 平安科技（深圳）有限公司 | Test preposition implementation method, device, terminal device and storage medium |
| CN109240662A (en) * | 2018-08-09 | 2019-01-18 | 赛尔网络有限公司 | A kind of software development methodology based on cloud platform, cloud platform, equipment and medium |
| CN109358858A (en) * | 2018-09-19 | 2019-02-19 | 网易（杭州）网络有限公司 | Automatically dispose method, apparatus, medium and electronic equipment |
| CN109408382A (en) * | 2018-10-11 | 2019-03-01 | 网宿科技股份有限公司 | A kind of continuous integrating method and continuous integration system |
| CN109582569A (en) * | 2018-11-14 | 2019-04-05 | 深圳市佰仟金融服务有限公司 | Lending platforms test method, device, terminal device and readable storage medium storing program for executing |
-
2019
- 2019-06-27 CN CN201910568195.2A patent/CN112148583A/en active Pending
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20150082279A1 (en) * | 2013-09-13 | 2015-03-19 | Sap Ag | Software testing system and method |
| CN106717118A (en) * | 2014-09-29 | 2017-05-24 | 飞利浦灯具控股公司 | Systems and methods for managing environmental conditions |
| CN104765692A (en) * | 2015-04-29 | 2015-07-08 | 北京嘀嘀无限科技发展有限公司 | Method and equipment for automatically testing software |
| CN106407100A (en) * | 2015-07-29 | 2017-02-15 | 中兴通讯股份有限公司 | Method and apparatus for realizing continuous integration testing |
| CN107885658A (en) * | 2017-10-31 | 2018-04-06 | 平安科技（深圳）有限公司 | Test preposition implementation method, device, terminal device and storage medium |
| CN109240662A (en) * | 2018-08-09 | 2019-01-18 | 赛尔网络有限公司 | A kind of software development methodology based on cloud platform, cloud platform, equipment and medium |
| CN109358858A (en) * | 2018-09-19 | 2019-02-19 | 网易（杭州）网络有限公司 | Automatically dispose method, apparatus, medium and electronic equipment |
| CN109408382A (en) * | 2018-10-11 | 2019-03-01 | 网宿科技股份有限公司 | A kind of continuous integrating method and continuous integration system |
| CN109582569A (en) * | 2018-11-14 | 2019-04-05 | 深圳市佰仟金融服务有限公司 | Lending platforms test method, device, terminal device and readable storage medium storing program for executing |
Non-Patent Citations (4)
| Title |
|---|
| EARL T. BARR 等: "The Oracle Problem in Software Testing: A Survey", 《IEEE TRANSACTIONS ON SOFTWARE ENGINEERING 》, vol. 41, no. 5, 20 November 2014 (2014-11-20), pages 507 - 525, XP011581002, DOI: 10.1109/TSE.2014.2372785 * |
| GREENGNN: "前端环境搭建——代码开发测试部署", Retrieved from the Internet <URL:《https://www.cnblogs.com/greengnn/archive/2011/03/30/1999373.html》> * |
| 李健楠: "基于Android平台的软件自动化测试系统的设计与实现", 《中国优秀硕士学位论文全文数据库 信息科技辑》, no. 3, 15 March 2018 (2018-03-15), pages 138 - 870 * |
| 章亮 等: "嵌入式软件测试开发环境的框架设计", 《北京航空航天大学学报》, no. 3, 30 March 2005 (2005-03-30), pages 336 - 340 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112860540A (en) * | 2021-01-14 | 2021-05-28 | 中国农业银行股份有限公司 | Software version upgrade test management and control system and method |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11036491B1 (en) | Identifying and resolving firmware component dependencies | |
| US20170277624A1 (en) | Method and system for automated user interface (ui) testing through model driven techniques | |
| US9483384B2 (en) | Generation of software test code | |
| US11080179B2 (en) | Device, system, and method for automatically detecting and repairing a bug in a computer program using a genetic algorithm | |
| CN111767226B (en) | Cloud computing platform resource testing method, system and equipment | |
| US8024707B2 (en) | Facilitating self-remediation for software applications | |
| US11461472B2 (en) | Automatic correctness and performance measurement of binary transformation systems | |
| CN114692169B (en) | Page vulnerability processing method applying big data and AI analysis and page service system | |
| CN111274117B (en) | Recommended service experiment and management method, device and system thereof | |
| CN114237754B (en) | Data loading method and device, electronic equipment and storage medium | |
| CN111813379B (en) | Application deployment method and device, electronic equipment and computer readable storage medium | |
| CN106874173B (en) | Page template testing method and device | |
| CN112148583A (en) | Software testing method and system | |
| CN111240987B (en) | Method and device for detecting migration program, electronic equipment and computer readable storage medium | |
| WO2023207973A1 (en) | Compiler test method and apparatus, case generation method and apparatus, and instruction storage structure | |
| US10481969B2 (en) | Configurable system wide tests | |
| JP6878707B2 (en) | Test equipment, test methods and test programs | |
| CN110471828B (en) | Operating system testing method, device and equipment thereof | |
| US20140215440A1 (en) | Marked test script creation | |
| CN116561003A (en) | Test data generation method, device, computer equipment and storage medium | |
| US11740895B2 (en) | Generation of software program repair explanations | |
| CN114338846B (en) | Message testing method and device | |
| CN110297625B (en) | Application processing method and device | |
| CN114237687A (en) | Software version acquisition method and system, electronic equipment and storage medium | |
| WO2012104991A1 (en) | Program test method, program test system, and program |
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 |