Software testing method and device
A software testing method and software testing technology, applied in the computer field, can solve problems such as low efficiency of failure recovery testing, and achieve the effect of improving efficiency
- Summary
- Abstract
- Description
- Claims
- Application Information
AI Technical Summary
Problems solved by technology
Method used
Image
Examples
Embodiment 1
[0023] figure 1 A schematic flow chart of a software testing method provided in Embodiment 1 of the present invention, as figure 1 shown, including:
[0024] Step 101, execute the target program.
[0025] When writing the target program code, test points have been preset in the target program. The content of the test point includes the test point identification, such as the test point name, and the test point may also include macros and custom codes, wherein the macro is used to indicate the execution sequence of the custom codes and calling the test program. Since the test program is usually described in a fixed format such as execution mode, event content and event type, in order to improve the flexibility of the test, the user can pre-write a section of self-test in the test point when writing the target program code. Define the code.
[0026] Further, before executing the target program, each test point in the target program can be set to be closed, and then the target...
Embodiment 2
[0034] figure 2 It is a schematic flow diagram of a software testing method provided by Embodiment 2 of the present invention. In order to clearly illustrate the execution flow when the client modifies the test program on the server side, this embodiment provides the following figure 2 The specific schematic diagram of the process is shown.
[0035] The method provided in this embodiment is executed by a server end and a client end, wherein the server end is used to run the target program, and a container (Map) storing the test program is set on the server end. The client can request to update the test program in the Map through RCP.
[0036] For the server side, on the one hand, test points are inserted at required test positions in the target program, for example, to eliminate bugs (debug) points.
[0037] Specifically, the debug point can be designed using the singleton mode. In the code of the target program, the position of the debug point needs to be added, and a nam...
Embodiment 3
[0056] image 3 A schematic structural diagram of a software testing device provided in Embodiment 3 of the present invention, such as image 3 As shown, it includes: an execution module 31 and a calling module 32 .
[0057] The execution module 31 is used for executing the target program.
[0058] The calling module 32 is configured to call the test program corresponding to the test point to test the target program when the test point preset in the target program is executed.
[0059] Wherein, the test point may include: test point identification, macro and custom code.
[0060] Specifically, the calling module 32 is specifically configured to call the test program to perform a failure recovery test on the target program.
[0061] In this embodiment, by setting test points in the target program in advance, in the process of executing the target program, the test program corresponding to the test point is called to test the target program after the target program is execute...
PUM
Login to View More Abstract
Description
Claims
Application Information
Login to View More