CN110928784A - Software testing environment monitoring method and device - Google Patents
Software testing environment monitoring method and device Download PDFInfo
- Publication number
- CN110928784A CN110928784A CN201911148365.8A CN201911148365A CN110928784A CN 110928784 A CN110928784 A CN 110928784A CN 201911148365 A CN201911148365 A CN 201911148365A CN 110928784 A CN110928784 A CN 110928784A
- Authority
- CN
- China
- Prior art keywords
- software
- software system
- target
- monitoring
- testing environment
- 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.)
- Granted
Links
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/3664—Environments for testing or debugging software
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/302—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a software system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3051—Monitoring arrangements for monitoring the configuration of the computing system or of the computing system component, e.g. monitoring the presence of processing resources, peripherals, I/O links, software programs
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The application provides a method and a device for monitoring a software testing environment, wherein the method comprises the following steps: acquiring a monitoring test case applied to a target software test environment; and running the monitoring test case, and monitoring the core function of each software system and/or the interaction function among different software systems in the target software test environment. In the application, the software testing environment can be monitored in the above mode, and the monitoring effect is improved.
Description
Technical Field
The present disclosure relates to software testing technologies, and in particular, to a method and an apparatus for monitoring a software testing environment.
Background
Before the software is put into use, a software testing environment (which may be understood as a software system environment for testing purposes, including a plurality of software systems in a testing state) is generally set up and tested.
Whether the software testing environment is stable or controllable affects the testing effect of the software, so that the software testing environment needs to be monitored, but how to monitor the software testing environment becomes a problem.
Disclosure of Invention
In order to solve the above technical problems, embodiments of the present application provide a method and an apparatus for monitoring a software testing environment, so as to achieve the purpose of monitoring the software testing environment and improving a monitoring effect, and the technical scheme is as follows:
a software testing environment monitoring method comprises the following steps:
acquiring a monitoring test case applied to a target software test environment;
and running the monitoring test case to monitor the core function of each software system and/or the interaction function among different software systems in the target software testing environment.
Preferably, the running the monitoring test case includes:
and periodically running the monitoring test case by using the continuous integrated software to monitor the core function of each software system and/or the interaction function among different software systems in the target software testing environment.
Preferably, after the monitoring the core function of each software system and/or the interaction function between different software systems in the target software testing environment to obtain the monitoring result, the method further includes:
and recording the availability data of each software system.
Preferably, the method further comprises:
and analyzing the dependency relationship between different software systems in the target software testing environment once every preset time to obtain a dependency relationship analysis result.
Preferably, the analyzing the dependency relationship between different software systems in the target software testing environment once every preset time to obtain a dependency relationship analysis result includes:
acquiring log data within a set time range every other preset time;
searching a transaction identifier of a target software system in the target software testing environment;
searching a log record related to the transaction identifier in the log data to serve as a target log record;
sequencing the target log records according to transaction time, a transaction initiating software system and a transaction receiving software system to obtain an ordered list of triples as a dependency edge set, wherein the triples comprise the transaction time, the transaction initiating software system and the transaction receiving software system;
acquiring the software system corresponding to the transaction identifier from the log data, deleting the repeated software system in the software system corresponding to the transaction identifier, and taking the obtained software system set as a dependency node set;
and constructing a software system dependency relationship graph as a dependency relationship analysis result according to the dependency relationship edge set and the dependency relationship node set.
Preferably, the method further comprises:
and marking the availability of the nodes in the dependency graph of the software system by using the availability data of each software system.
A software testing environment monitoring device, comprising:
the acquisition module is used for acquiring a monitoring test case applied to a target software test environment;
and the operation module is used for operating the monitoring test case and monitoring the core function of each software system and/or the interaction function among different software systems in the target software testing environment.
Preferably, the operation module is specifically configured to:
and periodically running the monitoring test case by using the continuous integrated software to monitor the core function of each software system and/or the interaction function among different software systems in the target software testing environment.
Preferably, the operation module is further configured to:
and running the monitoring test case, monitoring the core function of each software system and/or the interaction function among different software systems in the target software testing environment, and recording the availability data of each software system.
Preferably, the apparatus further comprises:
and the analysis module is used for analyzing the dependency relationship between different software systems in the target software testing environment once every preset time to obtain a dependency relationship analysis result.
Preferably, the analysis module is specifically configured to:
acquiring log data within a set time range every other preset time;
searching a transaction identifier of a target software system in the target software testing environment;
searching a log record related to the transaction identifier in the log data to serve as a target log record;
sequencing the target log records according to transaction time, a transaction initiating software system and a transaction receiving software system to obtain an ordered list of triples as a dependency edge set, wherein the triples comprise the transaction time, the transaction initiating software system and the transaction receiving software system;
acquiring the software system corresponding to the transaction identifier from the log data, deleting the repeated software system in the software system corresponding to the transaction identifier, and taking the obtained software system set as a dependency node set;
and constructing a software system dependency relationship graph as a dependency relationship analysis result according to the dependency relationship edge set and the dependency relationship node set.
Preferably, the apparatus further comprises:
and the marking module is used for marking the availability of the nodes in the dependency graph of the software system by using the availability data of each software system.
Compared with the prior art, the beneficial effect of this application is:
in the application, since the software testing environment is composed of a plurality of software systems, monitoring the software testing environment can be equivalent to monitoring the software systems in the software testing environment, specifically, a monitoring test case can be run, and the core function of each software system and/or the interaction function between different software systems in the target software testing environment can be monitored. In the testing link, the functional test of the software system and the interactive function test among different software systems are emphasized, so that the core function monitoring and/or the interactive function monitoring among different software systems are performed in a targeted manner, and the monitoring effect is improved.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without inventive labor.
FIG. 1 is a flow chart of a software testing environment monitoring method provided by the present application;
FIG. 2 is a flow chart of another software testing environment monitoring method provided by the present application;
FIG. 3 is a flow chart of yet another software testing environment monitoring method provided herein;
FIG. 4 is a flow chart of yet another software testing environment monitoring method provided herein;
FIG. 5 is a flow chart of yet another software testing environment monitoring method provided herein;
FIG. 6 is a schematic diagram of a software system dependency graph provided herein;
FIG. 7 is a flow chart of yet another software testing environment monitoring method provided herein;
fig. 8 is a schematic logic structure diagram of a software testing environment monitoring apparatus provided in the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
The embodiment of the application discloses a software testing environment monitoring method, which comprises the following steps: acquiring a monitoring test case applied to a target software test environment; and running the monitoring test case to monitor the core function of each software system and/or the interaction function among different software systems in the target software testing environment. In the application, the monitoring of the software testing environment is realized, and the monitoring effect is improved.
As shown in fig. 1, a flowchart of an embodiment 1 of a software testing environment monitoring method provided by the present application includes the following steps:
and step S11, acquiring a monitoring test case applied to the target software test environment.
Monitoring test cases can be understood as: and the test case is used for monitoring the availability of the test environment of the target software.
The design of the monitoring test case is related to the monitoring target of the software testing environment. For example, the software development period test focuses on the correctness of software functions, the robustness of exception handling and the coverage of branches, and the monitoring test case mainly comprises an automatic unit test and an integrated test; the software acceptance period focuses on the non-functional characteristics of the correctness of software functions, the correct processing capability of the software to exceptions, the conformity of the software functions to user requirements, the safety and the performance of the software and the like, and the monitoring test cases comprise automatic function tests, automatic safety tests, automatic performance tests and manual exploration type tests.
The development process of monitoring the test case in this embodiment may be:
the method comprises the steps of establishing one or more software development projects, selecting an automatic test framework, developing different automatic monitoring test cases aiming at different software test environments based on the automatic test framework, organizing related monitoring test cases into a set to serve as a test suite set, and placing the test suite set in the software development projects for management.
The software development engineering is managed and monitored by a source code management system.
In this embodiment, the monitoring test case applied to the target software test environment may be obtained from the source code management system.
And step S12, running the monitoring test case, and monitoring the core function of each software system and/or the interaction function among different software systems in the target software testing environment.
Monitoring the core functions of the software systems and/or the interaction functions between different software systems in the target software testing environment may be understood as: the availability of each software system in the target software test environment is monitored.
As another alternative embodiment of the present application, referring to fig. 2, a schematic flow chart of an embodiment 2 of a software testing environment monitoring method provided by the present application is provided, where this embodiment mainly relates to a refinement scheme of the software testing environment monitoring method described in the foregoing embodiment 1, as shown in fig. 2, the method may include, but is not limited to, the following steps:
and step S21, acquiring a monitoring test case applied to the target software test environment.
The detailed process of step S21 can be referred to the related description of step S11 in embodiment 1, and is not repeated here.
And step S22, periodically running the monitoring test case by using the continuous integrated software, and monitoring the core function of each software system and/or the interactive function among different software systems in the target software testing environment.
And periodically running the monitoring test case by using the continuous integrated software, and monitoring the core function of each software system and/or the interaction function among different software systems in the target software test environment so as to realize the continuous monitoring of the target software test environment and improve the monitoring reliability.
As another alternative embodiment of the present application, referring to fig. 3, a schematic flow chart of an embodiment 3 of a software testing environment monitoring method provided by the present application is provided, where this embodiment is mainly an extension of the software testing environment monitoring method described in the above embodiment 1, and as shown in fig. 3, the method may include, but is not limited to, the following steps:
and step S31, acquiring a monitoring test case applied to the target software test environment.
And step S32, running the monitoring test case, monitoring the core function of each software system and/or the interaction function among different software systems in the target software testing environment, and recording the availability data of each software system.
For the process of monitoring the core function of each software system and/or the interaction function between different software systems in the target software testing environment, reference may be made to related descriptions in embodiment 1 for monitoring the core function of each software system and/or the interaction function between different software systems in the target software testing environment, and details are not described here again.
And when monitoring the core function of each software system and/or the interaction function among different software systems in the target software testing environment by the monitoring test case, generating the availability data of each software system in the target software testing environment and recording the availability data.
The availability data of a software system can be understood as: data for characterizing the availability of the software system.
The availability data of each software system recorded by the monitoring test case can be used as guidance data for developing the monitoring test case and maintaining the test environment of the target software.
After the monitoring test case records the availability data of each software system, the recorded availability data of each software system can be pushed to related operation and maintenance personnel or related platforms; of course, the monitoring test case may also provide an inquiry interface for externally inquiring the availability data of each software system.
As another alternative embodiment of the present application, referring to fig. 4, a schematic flow chart of an embodiment 4 of a software testing environment monitoring method provided by the present application is provided, where this embodiment is mainly an extension of the software testing environment monitoring method described in the above embodiment 3, as shown in fig. 4, the method may include, but is not limited to, the following steps:
and step S41, acquiring a monitoring test case applied to the target software test environment.
And step S42, running the monitoring test case, monitoring the core function of each software system and/or the interaction function among different software systems in the target software testing environment, and recording the availability data of each software system.
The detailed procedures of steps S41-S42 can be referred to the related descriptions of steps S31-S33 in embodiment 3, and are not described herein again.
And step S43, analyzing the dependency relationship between different software systems in the target software testing environment once every preset time to obtain a dependency relationship analysis result.
It should be noted that there are calling and called dependencies between various software systems in the target software test environment. Software dependencies are determined at the software design stage, but such static relationships lose accuracy as software functions change. Therefore, the dependency relationship between the dynamic analysis software is needed to ensure the accuracy.
Analyzing the dependency relationship between different software systems in the target software testing environment once every preset time to obtain a dependency relationship analysis result, wherein the dependency relationship analysis result can be used as a function of monitoring the testing case.
Of course, a dependency relationship analysis program may also be separately set, the dependency relationship analysis program is run, and the dependency relationship between different software systems in the target software test environment is analyzed once every preset time to obtain a dependency relationship analysis result.
In this embodiment, the dependency analysis result may guide the development of the monitoring test case.
As another alternative embodiment of the present application, referring to fig. 5, a schematic flow chart of an embodiment 5 of a software testing environment monitoring method provided by the present application is provided, where this embodiment mainly relates to a refinement scheme of the software testing environment monitoring method described in the above embodiment 4, as shown in fig. 5, the method may include, but is not limited to, the following steps:
and step S51, acquiring a monitoring test case applied to the target software test environment.
And step S52, running the monitoring test case, monitoring the core function of each software system and/or the interaction function among different software systems in the target software testing environment, and recording the availability data of each software system.
The detailed procedures of steps S51-S52 can be referred to the related descriptions of steps S41-S43 in embodiment 4, and are not described herein again.
And step S53, acquiring the log data within the set time range every preset time.
The setting time range may be set as needed, and is not limited herein.
And step S54, searching the transaction identification of the target software system in the target software testing environment.
When a transaction occurs in the target software system, the transaction identifier of the target software system is transmitted between the software systems along with the transaction data and is recorded in the log data.
Therefore, when the dependency relationship between the target software system and other software systems needs to be analyzed, the transaction identifier of the target software system needs to be searched.
And step S55, searching the log record related to the transaction identification in the log data as a target log record.
Step S56, the target log records are sequenced according to the transaction time, the transaction initiating software system and the transaction receiving software system to obtain an ordered list of triples as a dependency edge set, wherein the triples comprise the transaction time, the transaction initiating software system and the transaction receiving software system.
And sequencing the target log records according to the transaction time, the transaction initiating software system and the transaction receiving software system to obtain a plurality of sequencing results, wherein each sequencing result can be understood as ordered information of the triples.
Accordingly, an ordered list of triples may be understood as: a list of ordered information comprising a plurality of triples.
And step S57, acquiring the software system corresponding to the transaction identifier from the log data, deleting the repeated software system in the software system corresponding to the transaction identifier, and taking the obtained software system set as a dependency node set.
And acquiring the software system corresponding to the transaction identifier from the log data, and deleting the repeated software system in the software system corresponding to the transaction identifier, so that the reliability of the dependency node set can be ensured.
And step S58, constructing a software system dependency relationship graph as a dependency relationship analysis result according to the dependency relationship edge set and the dependency relationship node set.
And constructing a software system dependency relationship graph according to the dependency relationship edge set and the dependency relationship node set, so that the dependency relationship among software systems can be displayed more intuitively.
In this embodiment, an aviation service software system is taken as an example to illustrate a software system dependency graph, for example, the software system dependency graph may be referred to in fig. 6. As shown in fig. 6, the 2-1 internet unified access system has a dependency relationship with the 1-1 airline website system and the 1-2 airline mobile APP background service system.
Steps S53-S58 are a specific implementation of step S43 in example 4.
In this embodiment, the software system dependency graph can also be visually displayed.
As another alternative embodiment of the present application, referring to fig. 7, a schematic flow chart of an embodiment 6 of a software testing environment monitoring method provided by the present application is provided, where this embodiment is mainly an extension of the software testing environment monitoring method described in the above embodiment 5, as shown in fig. 7, the method may include, but is not limited to, the following steps:
and step S61, acquiring a monitoring test case applied to the target software test environment.
And step S62, running the monitoring test case, monitoring the core function of each software system and/or the interaction function among different software systems in the target software testing environment, and recording the availability data of each software system.
And step S63, acquiring the log data within the set time range every preset time.
And step S64, searching the transaction identification of the target software system in the target software testing environment.
And step S65, searching the log record related to the transaction identification in the log data as a target log record.
Step S66, the target log records are sequenced according to the transaction time, the transaction initiating software system and the transaction receiving software system to obtain an ordered list of triples as a dependency edge set, wherein the triples comprise the transaction time, the transaction initiating software system and the transaction receiving software system.
And step S67, acquiring the software system corresponding to the transaction identifier from the log data, deleting the repeated software system in the software system corresponding to the transaction identifier, and taking the obtained software system set as a dependency node set.
And step S68, constructing a software system dependency relationship graph as a dependency relationship analysis result according to the dependency relationship edge set and the dependency relationship node set.
The detailed procedures of steps S61-S68 can be found in the related descriptions of steps S51-S58 in embodiment 5, and are not repeated herein.
And step S69, marking the availability of the nodes in the dependency graph of the software system by using the availability data of each software system.
The nodes in the dependency graph of the software system can be understood as follows: the target software tests the software system in the environment.
The availability of the nodes in the software system dependency graph is marked by using the availability data of each software system, so that the dependency among the software systems and the availability of each software system can be visually displayed in the software system dependency graph.
In this embodiment, the availability of the nodes in the dependency graph of the software system may be marked by using, but not limited to, a color marking method. For example, nodes in FIG. 6 that are available (e.g., 1-1 airline website system and 1-2 airline mobile APP background service system) may be marked in blue, nodes that are unavailable (e.g., 2-1 Internet Uniform Access System marked in red), and nodes with unknown availability (e.g., 3-1 available flight enquiry system, etc.) may be marked in white.
Next, the software testing environment monitoring apparatus provided in the present application is introduced, and the software testing environment monitoring apparatus described below and the software testing environment monitoring method described above may be referred to correspondingly.
Referring to fig. 8, the software testing environment monitoring apparatus includes: an acquisition module 11 and an execution module 12.
The acquisition module 11 is used for acquiring a monitoring test case applied to a target software test environment;
and the running module 12 is configured to run the monitoring test case, and monitor a core function of each software system and/or an interaction function between different software systems in the target software testing environment.
In this embodiment, the operation module 12 may be specifically configured to:
and periodically running the monitoring test case by using the continuous integrated software to monitor the core function of each software system and/or the interaction function among different software systems in the target software testing environment.
In this embodiment, the running module 12 may be further configured to:
and running the monitoring test case, monitoring the core function of each software system and/or the interaction function among different software systems in the target software testing environment, and recording the availability data of each software system.
In this embodiment, the software testing environment monitoring apparatus may further include:
and the analysis module is used for analyzing the dependency relationship between different software systems in the target software testing environment once every preset time to obtain a dependency relationship analysis result.
In this embodiment, the analysis module may be specifically configured to:
acquiring log data within a set time range every other preset time;
searching a transaction identifier of a target software system in the target software testing environment;
searching a log record related to the transaction identifier in the log data to serve as a target log record;
sequencing the target log records according to transaction time, a transaction initiating software system and a transaction receiving software system to obtain an ordered list of triples as a dependency edge set, wherein the triples comprise the transaction time, the transaction initiating software system and the transaction receiving software system;
acquiring the software system corresponding to the transaction identifier from the log data, deleting the repeated software system in the software system corresponding to the transaction identifier, and taking the obtained software system set as a dependency node set;
and constructing a software system dependency relationship graph as a dependency relationship analysis result according to the dependency relationship edge set and the dependency relationship node set.
In this embodiment, the software testing environment monitoring apparatus may further include:
and the marking module is used for marking the availability of the nodes in the dependency graph of the software system by using the availability data of each software system.
It should be noted that, in the present specification, the embodiments are all described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments may be referred to each other. For the device-like embodiment, since it is basically similar to the method embodiment, the description is simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be 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. Also, 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 a process, method, article, or apparatus that comprises the element.
For convenience of description, the above devices are described as being divided into various units by function, and are described separately. Of course, the functionality of the units may be implemented in one or more software and/or hardware when implementing the present application.
From the above description of the embodiments, it is clear to those skilled in the art that the present application can be implemented by software plus necessary general hardware platform. Based on such understanding, the technical solutions of the present application may be essentially or partially implemented in the form of a software product, which may be stored in a storage medium, such as a ROM/RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which may be a personal computer, a server, or a network device, etc.) to execute the method according to the embodiments or some parts of the embodiments of the present application.
The software testing environment monitoring method and device provided by the application are introduced in detail, specific examples are applied in the method to explain the principle and the implementation mode of the application, and the description of the embodiments is only used for helping to understand the method and the core idea of the application; meanwhile, for a person skilled in the art, according to the idea of the present application, there may be variations in the specific embodiments and the application scope, and in summary, the content of the present specification should not be construed as a limitation to the present application.
Claims (12)
1. A software testing environment monitoring method is characterized by comprising the following steps:
acquiring a monitoring test case applied to a target software test environment;
and running the monitoring test case to monitor the core function of each software system and/or the interaction function among different software systems in the target software testing environment.
2. The method of claim 1, wherein the running the monitoring test case comprises:
and periodically running the monitoring test case by using the continuous integrated software to monitor the core function of each software system and/or the interaction function among different software systems in the target software testing environment.
3. The method according to claim 1, wherein the monitoring the core functions of the software systems and/or the interaction functions between different software systems in the target software testing environment, and after obtaining the monitoring result, further comprises:
and recording the availability data of each software system.
4. The method of claim 3, further comprising:
and analyzing the dependency relationship between different software systems in the target software testing environment once every preset time to obtain a dependency relationship analysis result.
5. The method according to claim 4, wherein analyzing the dependency relationship between different software systems in the target software testing environment once every preset time to obtain a dependency relationship analysis result comprises:
acquiring log data within a set time range every other preset time;
searching a transaction identifier of a target software system in the target software testing environment;
searching a log record related to the transaction identifier in the log data to serve as a target log record;
sequencing the target log records according to transaction time, a transaction initiating software system and a transaction receiving software system to obtain an ordered list of triples as a dependency edge set, wherein the triples comprise the transaction time, the transaction initiating software system and the transaction receiving software system;
acquiring the software system corresponding to the transaction identifier from the log data, deleting the repeated software system in the software system corresponding to the transaction identifier, and taking the obtained software system set as a dependency node set;
and constructing a software system dependency relationship graph as a dependency relationship analysis result according to the dependency relationship edge set and the dependency relationship node set.
6. The method of claim 5, further comprising:
and marking the availability of the nodes in the dependency graph of the software system by using the availability data of each software system.
7. A software testing environment monitoring device, comprising:
the acquisition module is used for acquiring a monitoring test case applied to a target software test environment;
and the operation module is used for operating the monitoring test case and monitoring the core function of each software system and/or the interaction function among different software systems in the target software testing environment.
8. The apparatus of claim 7, wherein the operation module is specifically configured to:
and periodically running the monitoring test case by using the continuous integrated software to monitor the core function of each software system and/or the interaction function among different software systems in the target software testing environment.
9. The apparatus of claim 7, wherein the operation module is further configured to:
and running the monitoring test case, monitoring the core function of each software system and/or the interaction function among different software systems in the target software testing environment, and recording the availability data of each software system.
10. The apparatus of claim 9, further comprising:
and the analysis module is used for analyzing the dependency relationship between different software systems in the target software testing environment once every preset time to obtain a dependency relationship analysis result.
11. The apparatus of claim 10, wherein the analysis module is specifically configured to:
acquiring log data within a set time range every other preset time;
searching a transaction identifier of a target software system in the target software testing environment;
searching a log record related to the transaction identifier in the log data to serve as a target log record;
sequencing the target log records according to transaction time, a transaction initiating software system and a transaction receiving software system to obtain an ordered list of triples as a dependency edge set, wherein the triples comprise the transaction time, the transaction initiating software system and the transaction receiving software system;
acquiring the software system corresponding to the transaction identifier from the log data, deleting the repeated software system in the software system corresponding to the transaction identifier, and taking the obtained software system set as a dependency node set;
and constructing a software system dependency relationship graph as a dependency relationship analysis result according to the dependency relationship edge set and the dependency relationship node set.
12. The apparatus of claim 11, further comprising:
and the marking module is used for marking the availability of the nodes in the dependency graph of the software system by using the availability data of each software system.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911148365.8A CN110928784B (en) | 2019-11-21 | 2019-11-21 | Software testing environment monitoring method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911148365.8A CN110928784B (en) | 2019-11-21 | 2019-11-21 | Software testing environment monitoring method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110928784A true CN110928784A (en) | 2020-03-27 |
| CN110928784B CN110928784B (en) | 2023-09-05 |
Family
ID=69850537
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911148365.8A Active CN110928784B (en) | 2019-11-21 | 2019-11-21 | Software testing environment monitoring method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110928784B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112799962A (en) * | 2021-02-26 | 2021-05-14 | 平安消费金融有限公司 | Software testing method, device, equipment and medium |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1851665A (en) * | 2005-11-07 | 2006-10-25 | 华为技术有限公司 | Method for completing product automation test utilizing test kit |
| KR20090104275A (en) * | 2008-03-31 | 2009-10-06 | 한국항공우주산업 주식회사 | Pairwise test case generation method based on module dependency and computer readable medium for recording program thereof |
| US20160147646A1 (en) * | 2014-11-21 | 2016-05-26 | Wipro Limited | Method and system for executing automated tests in an integrated test environment |
| US20160171141A1 (en) * | 2014-12-16 | 2016-06-16 | International Business Machines Corporation | Verification environments utilzing hardware description languages |
| CN108073488A (en) * | 2016-11-14 | 2018-05-25 | 北京京东尚科信息技术有限公司 | Service monitoring method and device |
| CN108628918A (en) * | 2017-09-29 | 2018-10-09 | 南京途牛科技有限公司 | System deployment and dependence automatic Plotting System and method |
| CN108710577A (en) * | 2018-06-01 | 2018-10-26 | 平安普惠企业管理有限公司 | Operation system test method, device, computer equipment and storage medium |
| CN108845937A (en) * | 2018-06-01 | 2018-11-20 | 平安普惠企业管理有限公司 | Test environment control method, device, computer equipment and storage medium |
| CN109144874A (en) * | 2018-08-22 | 2019-01-04 | 北京奇虎科技有限公司 | A kind of monitoring method and device for testing environment |
-
2019
- 2019-11-21 CN CN201911148365.8A patent/CN110928784B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1851665A (en) * | 2005-11-07 | 2006-10-25 | 华为技术有限公司 | Method for completing product automation test utilizing test kit |
| KR20090104275A (en) * | 2008-03-31 | 2009-10-06 | 한국항공우주산업 주식회사 | Pairwise test case generation method based on module dependency and computer readable medium for recording program thereof |
| US20160147646A1 (en) * | 2014-11-21 | 2016-05-26 | Wipro Limited | Method and system for executing automated tests in an integrated test environment |
| US20160171141A1 (en) * | 2014-12-16 | 2016-06-16 | International Business Machines Corporation | Verification environments utilzing hardware description languages |
| CN108073488A (en) * | 2016-11-14 | 2018-05-25 | 北京京东尚科信息技术有限公司 | Service monitoring method and device |
| CN108628918A (en) * | 2017-09-29 | 2018-10-09 | 南京途牛科技有限公司 | System deployment and dependence automatic Plotting System and method |
| CN108710577A (en) * | 2018-06-01 | 2018-10-26 | 平安普惠企业管理有限公司 | Operation system test method, device, computer equipment and storage medium |
| CN108845937A (en) * | 2018-06-01 | 2018-11-20 | 平安普惠企业管理有限公司 | Test environment control method, device, computer equipment and storage medium |
| CN109144874A (en) * | 2018-08-22 | 2019-01-04 | 北京奇虎科技有限公司 | A kind of monitoring method and device for testing environment |
Non-Patent Citations (4)
| Title |
|---|
| JACKEI: "软件测试实践之测试环境的规划与管理", pages 1 - 5, Retrieved from the Internet <URL:https://www.cnblogs.com/jackei/archive/2005/10/02/248141.html> * |
| 何柳柳 等: "面向持续集成测试优化的强化学习奖励机制", 《软件学报》, vol. 30, no. 5, pages 1438 - 1449 * |
| 施彬彬: "面向自动化测试的虚拟机监控系统的设计与实现", 《中国优秀硕士学位论文全文数据库》, no. 2016, pages 137 - 5 * |
| 阮镰 等: "软件可靠性测试及其测试环境", 《测控技术》, no. 2, pages 9 - 16 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112799962A (en) * | 2021-02-26 | 2021-05-14 | 平安消费金融有限公司 | Software testing method, device, equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110928784B (en) | 2023-09-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110309071B (en) | Test code generation method and module, and test method and system | |
| US9753826B2 (en) | Providing fault injection to cloud-provisioned machines | |
| US9038030B2 (en) | Methods for predicting one or more defects in a computer program and devices thereof | |
| US9116779B2 (en) | Test management domain asset discovery and analysis | |
| CN109522228B (en) | Interface automation test data construction method, device, platform and storage medium | |
| US10509719B2 (en) | Automatic regression identification | |
| US11436133B2 (en) | Comparable user interface object identifications | |
| US9569782B1 (en) | Automated customer business impact assessment upon problem submission | |
| KR100460536B1 (en) | Apparatus and method for recommending associated components based on performance measurement of components | |
| EP2113874A1 (en) | Method and system for monitoring computer-implemented processes | |
| US10185559B2 (en) | Documentation notification | |
| CN106407054B (en) | BMC automatic test system and method | |
| CN110162441A (en) | Centralized monitoring method and device, electronic equipment, the storage medium of application system | |
| CN111654495B (en) | Method, apparatus, device and storage medium for determining traffic generation source | |
| CN112650688A (en) | Automated regression testing method, associated device and computer program product | |
| US10949333B1 (en) | Application maturity console | |
| CN114490375A (en) | Method, device and equipment for testing performance of application program and storage medium | |
| CN110795332A (en) | Automatic testing method and device | |
| CN110928784B (en) | Software testing environment monitoring method and device | |
| CN116662197A (en) | Automatic interface testing method, system, computer and readable storage medium | |
| CN110674024A (en) | Electronic equipment integration test system and method thereof | |
| US11894976B1 (en) | Automated predictive change analytics | |
| CN115190008B (en) | Fault processing method, fault processing device, electronic equipment and storage medium | |
| CN114064510A (en) | Function testing method and device, electronic equipment and storage medium | |
| Sundbaum | Automated Verification of Load Test Results in a Continuous Delivery Deployment Pipeline |
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 |