CN111190824B - Monitoring method, device, terminal equipment and storage medium - Google Patents
Monitoring method, device, terminal equipment and storage medium Download PDFInfo
- Publication number
- CN111190824B CN111190824B CN201911384597.3A CN201911384597A CN111190824B CN 111190824 B CN111190824 B CN 111190824B CN 201911384597 A CN201911384597 A CN 201911384597A CN 111190824 B CN111190824 B CN 111190824B
- Authority
- CN
- China
- Prior art keywords
- information
- test
- type
- preset reminding
- software
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 59
- 238000012544 monitoring process Methods 0.000 title claims abstract description 42
- 238000012360 testing method Methods 0.000 claims abstract description 199
- 238000004891 communication Methods 0.000 claims abstract description 57
- 230000007547 defect Effects 0.000 claims abstract description 55
- 238000010219 correlation analysis Methods 0.000 claims description 29
- 238000004590 computer program Methods 0.000 claims description 20
- 238000012806 monitoring device Methods 0.000 claims description 4
- 230000008859 change Effects 0.000 abstract description 4
- 230000008569 process Effects 0.000 description 10
- 238000010586 diagram Methods 0.000 description 9
- 238000012545 processing Methods 0.000 description 4
- 230000004044 response Effects 0.000 description 4
- 230000000153 supplemental effect Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 238000001514 detection method Methods 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 238000011161 development Methods 0.000 description 2
- 230000007849 functional defect Effects 0.000 description 2
- 241000700605 Viruses Species 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 230000002155 anti-virotic effect Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000003754 machining Methods 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000001537 neural effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000005236 sound signal Effects 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000001360 synchronised effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The application is applicable to the technical field of computers, and provides a monitoring method, a device, terminal equipment and a storage medium, wherein the method comprises the following steps: when the version management system is monitored to have an update record, annotation information and developer information in the update record are acquired, wherein the annotation information comprises ID information; determining an ID type of the ID information, wherein the ID type comprises a software characteristic ID type or a software defect ID type; acquiring testing progress and user information corresponding to the ID information, wherein the user information comprises tester information; and determining preset reminding information according to the ID type and/or the testing progress, and sending the testing progress and the preset reminding information to the first communication equipment corresponding to the developer information or the second communication equipment corresponding to the tester information. By combining the update record and the test progress, the intelligent reminding of developers or testers is realized, the problem caused by the change of the software code is prevented from flowing into the actual application, and the optimal experience of the client is ensured.
Description
Technical Field
The application belongs to the technical field of computers, and particularly relates to a monitoring method, a monitoring device, terminal equipment and a storage medium.
Background
Version management is an important content of software development, and code submission monitoring tools such as CommitMonitor, svnMonitorSVN can guarantee that codes are the latest versions in real time. In the software project development process, after the software code is changed, the code needs to be tested and analyzed for correlation. However, the current monitoring tool is not intelligent enough, and does not have the capability of reminding a developer of carrying out correlation analysis on the code or a tester of testing the code, so that problems existing in the software code which is not tested and subjected to correlation analysis are finally caused to flow into an actual application environment, and the satisfaction degree of a client on the software is reduced.
Disclosure of Invention
The embodiment of the application provides a monitoring method, a device, terminal equipment and a storage medium, which can solve the problem that the existing monitoring tool is not intelligent enough.
In a first aspect, an embodiment of the present application provides a monitoring method based on a version management system, including:
When the version management system is monitored to have an update record, annotation information and developer information in the update record are acquired, wherein the annotation information comprises ID information;
Determining an ID type of the ID information, wherein the ID type comprises a software characteristic ID type or a software defect ID type;
Acquiring the testing progress and user information corresponding to the ID information, wherein the user information comprises tester information;
And determining preset reminding information according to the ID type and/or the testing progress, and sending the testing progress and the preset reminding information to first communication equipment corresponding to the developer information or second communication equipment corresponding to the tester information.
According to the embodiment of the application, the software code can be timely monitored to be changed by monitoring the update record of the version management system; the method comprises the steps of obtaining annotation information in an update record, and obtaining ID information corresponding to a software characteristic test or a software defect test according to the annotation information so as to obtain the test type of software, so that a corresponding user is conveniently reminded to carry out related operations; and acquiring a test progress according to the ID information, and timely notifying a developer or a tester corresponding to the test node when the test progress reaches a preset test node, so that the developer or the tester can timely analyze or test the correlation of the code, the intelligent reminding of the developer or the tester is realized, the problem caused by the change of the software code is prevented from flowing into the actual application, and the optimal experience of a customer is ensured.
In a second aspect, an embodiment of the present application provides a monitoring apparatus based on a version management system, including:
The first acquisition module is used for acquiring annotation information in the update record when the version management system is monitored to have the update record, wherein the annotation information comprises ID information;
A determining module, configured to determine an ID type of the ID information, where the ID type includes a software characteristic ID type or a software defect ID type;
the second acquisition module is used for acquiring the testing progress and the user information corresponding to the ID information, wherein the user information comprises developer information and tester information;
the reminding module is used for determining preset reminding information according to the ID type and/or the testing progress, and sending the testing progress and the preset reminding information to first communication equipment corresponding to the developer information or second communication equipment corresponding to the tester information.
In a third aspect, an embodiment of the present application provides a terminal device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the monitoring method according to any one of the first aspects when executing the computer program.
In a fourth aspect, embodiments of the present application provide a computer readable storage medium having a computer program which, when executed by a processor, implements the monitoring method of any of the first aspects described above.
In a fifth aspect, an embodiment of the present application provides a computer program product, which, when run on a terminal device, causes the terminal device to perform the monitoring method according to any of the first aspects above.
It will be appreciated that the advantages of the second to fifth aspects may be found in the relevant description of the first aspect, and are not described here again.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
Fig. 1 is a schematic view of an application scenario provided in an embodiment of the present application;
FIG. 2 is a schematic diagram of a system according to an embodiment of the present application;
FIG. 3 is a schematic diagram of an SVN server adapted for use in a monitoring method according to an embodiment of the present application;
FIG. 4 is a flow chart of a monitoring method according to an embodiment of the application;
FIG. 5 is a flow chart of a monitoring method according to another embodiment of the present application;
FIG. 6 is a flow chart of a monitoring method according to another embodiment of the present application;
FIG. 7 is a flow chart of a monitoring method according to another embodiment of the present application;
FIG. 8 is a schematic structural diagram of a monitoring device according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of a terminal device according to an embodiment of the present application.
Detailed Description
In the following description, for purposes of explanation and not limitation, specific details are set forth such as the particular system architecture, techniques, etc., in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.
It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
It should also be understood that the term "and/or" as used in the present specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.
As used in the present description and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".
Furthermore, the terms "first," "second," "third," and the like in the description of the present specification and in the appended claims, are used for distinguishing between descriptions and not necessarily for indicating or implying a relative importance.
Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.
As described in the related art, in the process of developing and maintaining a software project, a software code (version data) is often modified to update a software version, and in order to ensure that no new problem occurs in modifying the software code, software defect test, software characteristic test or correlation analysis is required to be performed on the software code. However, developers or testers do not take care of the test progress or update records due to heavy work tasks, so that software defect tests, software characteristic tests or correlation analysis are not performed on the software codes in time, the current monitoring tools are not intelligent enough, and only can remind users of the current update records, so that the users only know the update records, but do not know which operation needs to be performed next, reminding information is easily ignored by the users, the reminding information is invalid in many cases, and poor experience is brought to the clients in the process of causing problems to flow to actual application.
Therefore, a monitoring method based on a version management system is needed to realize the process of monitoring the update record of the version management system, acquiring the test progress, combining the update record with the test progress and reminding the corresponding user of performing related operations.
Among them, software defects (also called BUG) are some functional defects that damage the normal running capability, errors or conceal in computer software or programs, and the presence of defects may cause the software product to fail to meet the needs of users to some extent. Software defect testing includes, but is not limited to, functional defect testing, system defect testing, machining defect testing, data defect testing, code defect testing.
The software characteristic test is a software performance test, and is used for verifying whether the software performance can meet the performance index or not after repeated use under normal environment and system conditions, and finding out the performance bottleneck of the software, so as to optimize the software performance. Software characterization tests include, but are not limited to, load tests and software stress tests.
Wherein, the correlation analysis is a process of analyzing each modified variable and other related variables after the software code is modified. As shown in the application scenario schematic diagram of fig. 1, there are two "business unit codes" in the diagram, in the default state, the "business unit code" in the "custom header" should be the same as the "business unit code" in the other place, when the software code modifies any place of "business unit code" into other names, the "business unit code" in the other place should be correspondingly modified, and the correlation analysis is to verify whether the other code related to the modified code in the software code is also correspondingly modified, so as to ensure the consistency of the associated code.
Fig. 2 shows a schematic diagram of a system provided by an embodiment of the present application, where the system includes an SVN (version management) server 201, a test system 202, a first communication device 203, and a second communication device 204, where the SVN server 201 communicates with the test system 202, the first communication device 203, and the second communication device 204 through a wired and/or wireless network.
The monitoring method based on the version management system provided by the embodiment of the application is applicable to the SVN server 201. The SVN server 201 is a machine operated by a version management system, and the SVN server may be operated by a stand-alone server or by means of an apache. The SVN server may monitor the submission of the software code and store version data corresponding to the software code, where the version data may be stored in BDB (transaction security table type) or FSFS (storage system that does not require a database).
The test system 202 is a system for performing a software defect test or a software property test on a software version, and records a test progress, tester information, and a name of a part property or a software defect corresponding to a test type including, but not limited to, a software version.
The first communication device 203 and the second communication device 204 may be communication devices of a developer and a tester, respectively, and may be communication devices such as a mobile phone, a tablet computer, a wearable device, a vehicle-mounted device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a Personal Digital Assistant (PDA), and the like, and the specific types of the first communication device 203 and the second communication device 204 are not limited in the embodiment of the present application.
Fig. 3 shows an example of an SVN server 201 that may include a processor 301, a memory 302, a communication module 303, a power management module 304, and the like.
The processor 301 may include one or more of a central processor, an application processor (application processor, AP), and the like. Processor 301 may be a neural and command center of a wireless router. The processor 302 may generate operation control signals according to the instruction operation code and the timing signals to complete the control of fetching instructions and executing instructions. Memory 302 may be used to store computer-executable program code that includes instructions. The processor 301 executes instructions stored in the memory 302 to thereby perform various functional applications and data processing of the SVN server 201. The memory 302 may include a storage program area and a storage data area, such as storing data of a sound signal played with, etc. For example, the memory may be a double rate synchronous dynamic random access memory DDR or Flash, etc.
The communication module 303 may be a solution of communication including wireless local area network (wireless localarea networks, WLAN), bluetooth, zigbee, mobile communication network, global navigation satellite system (global navigation SATELLITE SYSTEM, GNSS), frequency modulation (frequency modulation, FM), near field communication (NEAR FIELD communication, NFC), infrared (IR), etc. applied to the SVN server 201. The communication module 303 may include an antenna, which may have only one array element, or may be an antenna array including a plurality of array elements. The communication module 303 may receive electromagnetic waves through an antenna, frequency modulate and filter the electromagnetic wave signals, and transmit the processed signals to a processor. The communication module 303 may also receive a signal to be transmitted from the processor, frequency modulate and amplify the signal, and convert the signal to electromagnetic waves through the antenna to radiate.
The power management module 304 may receive input from a battery and/or charger to power the processor 301, memory 302, and communication module 303, among other things.
It should be noted that, the foregoing fig. 3 does not limit the structure of the SVN server 201, and may include more or fewer components than those shown in the drawings, or may combine some components, or different components, for example, the SVN server may further include a display screen, an indicator light, a control (e.g., a button), and so on.
Fig. 4 shows a schematic flow chart of a version management system-based monitoring method provided by the present application, which can be applied to the above-mentioned SVN server 201, by way of example and not limitation, and the version management system is built on the SVN server.
S401, when the version management system is monitored to have an update record, annotation information and developer information in the update record are acquired, wherein the annotation information comprises ID information.
The update record may include, but is not limited to, developer information for updating the software version, update time information (time of submission of the software code), annotation information, and path information for modifying the file. The comment information includes ID information, association between the ID information and the test system, and the like. The developer information includes a developer name, a person number, a communication address of the communication device, and the like.
S402, determining an ID type of the ID information, wherein the ID type comprises a software characteristic ID type or a software defect ID type.
ID information in the annotation information is analyzed, and the ID type of the ID information is determined according to the ID information and a preset determination rule. The software characteristic ID type is an identifier for marking one software version in one software characteristic test, and the software defect ID type is an identifier for marking one software version in one software defect test.
It should be noted that, when the ID type is the software defect ID type, the software is described as having completed the software defect test, since only the software defect test is completed, it is known to be the software defect. When the ID type is a software property ID type, the software does not necessarily start or complete the software property test.
S403, testing progress and user information corresponding to the ID information are obtained, and the user information comprises developer information and tester information.
Optionally, according to the association relation between the ID information and the test system, sending the ID information as a request for acquiring the test progress and the user information to the test system as an entry, so as to acquire the test progress and the user information corresponding to the ID information from the test system.
Optionally, the tester information includes a tester name, a person number, a communication address of the communication device, and the like.
S404, determining preset reminding information according to the ID type and/or the test progress, and sending the test progress and the preset reminding information to first communication equipment corresponding to the developer information or second communication equipment corresponding to the tester information.
The above-mentioned test schedule includes a test schedule of a software characteristic test or a test schedule of a software defect test, wherein the test schedule of the software characteristic test includes, but is not limited to, a started characteristic test, a not started characteristic test, a completed correlation analysis, a not started replenishment test, and a started replenishment test, and the test schedule of the software defect test includes, but is not limited to, a completed defect test and a completed correlation analysis. When the ID type is the software characteristic ID type, the software characteristic test is possibly completed, possibly in progress, possibly not started and the like, further determining a flow node reached by the test progress, and determining corresponding preset reminding information according to the flow node reached by the test progress; when the ID type is the software defect ID type, the software defect test is finished, and the preset reminding information for reminding the developer of carrying out correlation analysis can be determined.
The preset reminding information comprises, but is not limited to, reminding information for reminding a developer of carrying out correlation analysis, reminding information for reminding a tester of carrying out characteristic test, and reminding information for reminding the tester of carrying out supplementary test.
Optionally, the sending mode of the preset reminding information includes, but is not limited to, mail sending, short message sending, real-time chat tool (such as QQ or WeChat) sending, computer IP popup window, etc.
In one possible implementation manner, a computer IP address of a developer is obtained, a piece of data carrying the preset reminding information is sent to the computer IP address, after receiving a receiving request of the data, the computer verifies information such as a data source of the data, and after the verification is passed, the data is formally received, and after the received data is analyzed, the preset reminding information is displayed in a popup frame mode to remind the developer to perform correlation analysis on version data. The method comprises the steps of verifying information such as data sources and the like to prevent the data from being data carrying malicious viruses and being intercepted by computer antivirus software, wherein the data is sent by unknown sources. Furthermore, after the data is encrypted in a preset encryption mode, the data can be decrypted by the computer in a corresponding preset decryption mode, so that the safety of the data is improved.
According to the embodiment, the change condition of the software code can be monitored in time by monitoring the update record of the version management system; the method comprises the steps of obtaining annotation information in an update record, and obtaining ID information corresponding to a software characteristic test or a software defect test according to the annotation information so as to obtain the test type of software, so that a corresponding user is conveniently reminded to carry out related operations; acquiring a test progress according to the ID information to combine the update record and the test progress, and sending direct and effective reminding information to a user; specifically, when the test progress reaches a preset test node, a developer or a tester corresponding to the test node is timely notified, so that the developer or the tester can timely analyze or test the correlation of the code, the intelligent reminding of the developer or the tester is realized, the problem caused by the change of the software code is prevented from flowing into the actual application, and the optimal experience of a customer is ensured.
On the basis of the embodiment shown in fig. 4, the application also proposes an embodiment of another monitoring method. The step S401 described above specifically includes S4011 and S4012. It should be noted that the same steps as those in the embodiment of fig. 4 are not repeated here, please refer to the foregoing.
S4011, monitoring version data in a version library of the version management system;
S4012, when new version data is added to the version library, judging that the version management system has an update record, and acquiring annotation information and developer information in the update record.
In this embodiment, the SVN log of the SVN server may be monitored, where the SVN log records the dynamics of the version data of the version library. When new data exists in the SVN log and the new version data is recorded in the data and added into the version library, the developer is stated to send an update record containing information such as version data, annotation information, developer information and the like to the version management system, so that the annotation information and the developer information in the update record are acquired.
By monitoring whether new version data are added in the version library, whether the software version is changed or not can be timely and accurately obtained, and further, a user is timely reminded of relevant operations.
On the basis of the embodiment shown in fig. 4, the application also proposes an embodiment of another monitoring method. The step S402 described above specifically includes S4021 to S4023. It should be noted that the same steps as those in the embodiment of fig. 4 are not repeated here, please refer to the foregoing.
S4021, acquiring a keyword field of the ID information, and determining an ID type corresponding to the keyword field.
In this embodiment, the ID information includes software characteristic ID information or software defect ID information, and the software characteristic ID information or the software defect ID information may include a software name ID, a test type (software characteristic test type or software defect test type), and a corresponding number of code tests.
Specifically, if the keyword field is a first preset field, determining that the ID type of the ID information is a software characteristic ID type; and if the keyword field is a second preset field, determining that the ID type of the ID information is a software defect ID type. For example, the software defect ID information is RJ-QX0001, RJ represents a software name ID, QX represents a test type being a software defect test type, and QX0001 represents a first software defect test; the software characteristic ID information is RJ-TX0001, RJ represents the software name ID, TX represents the test type is the software characteristic test type, and TX0001 represents the first software characteristic test. Therefore, the above-mentioned analysis of the ID information in the comment information may be to analyze whether the ID information in the comment information includes a keyword field indicating a test type, and determine whether the keyword field indicating a software characteristic test or a software defect test is the keyword field indicating a software characteristic test or the software defect test, thereby determining whether the ID information is the software characteristic ID information or the software defect ID information.
It should be understood that the above-mentioned key fields of the software defect ID information and the software property ID information are only used for illustration, and are not used as specific means for limiting the embodiments of the present application, and in other embodiments, combinations of characters in other forms may be also used, which will not be repeated herein.
Fig. 5 also presents an embodiment of another monitoring method on the basis of the embodiment shown in fig. 4. As shown in fig. 5, the step S404 includes S501 and S502. It should be noted that the same steps as those in the embodiment of fig. 4 are not repeated here, please refer to the foregoing.
S501, when the ID type is a software characteristic ID type and the test progress reaches a test node which starts to be tested, determining that the preset reminding information is first preset reminding information, and sending the test progress and the first preset reminding information to first communication equipment corresponding to developer information, wherein the first preset reminding information is used for reminding a developer to carry out correlation analysis on version data.
The above-mentioned started test is specifically a started characteristic test. When the software characteristic test is started, the test is quickly finished, a developer is reminded to conduct correlation analysis on version data in order to accelerate the progress of a software development project, and when the developer starts equipment to conduct correlation analysis, the software characteristic test is basically finished, and then the correlation analysis can be conducted directly.
S502, when the ID type is a software characteristic ID type and the test progress reaches a test node which does not start testing, determining that the preset reminding information is second preset reminding information, and sending the test progress and the second preset reminding information to second communication equipment corresponding to the tester information, wherein the second preset reminding information is used for reminding a tester to test the software characteristic of the version data.
The non-start test is a non-start characteristic test. When the software characteristic test is not started, the developer is stated that the software characteristic test is planned to be carried out by the testers, the software version to be tested, the characteristic name and the like are recorded into the test system, and the software characteristic test is carried out on the version data by the testers. The method and the device can provide accurate and effective reminding information for developers or testers in combination with the test progress, and effectively improve the development efficiency of software development projects.
Fig. 6 also presents an embodiment of another monitoring method on the basis of the embodiment shown in fig. 4. As shown in fig. 6, the ID type is a software defect ID type, and the step S404 specifically includes S601. It should be noted that the same steps as those in the embodiment of fig. 4 are not repeated here, please refer to the foregoing.
S601, when the ID type is a software defect ID type, determining that the preset reminding information is first preset reminding information, and sending the test progress and the first preset reminding information to first communication equipment corresponding to the developer information, wherein the first preset reminding information is used for reminding the developer to carry out correlation analysis on version data.
In this embodiment, when the ID type is a software defect ID type, since the software defect can only be found after the test, the software defect test is finished at this time, and the developer needs to be reminded to perform correlation analysis on the version data after the software defect test. Therefore, the problem of software version is guaranteed not to flow into the actual application, and the optimal experience of the client is guaranteed.
On the basis of the embodiment shown in fig. 5 or 6, the application also proposes another embodiment of the monitoring method. The same steps as in the embodiment of fig. 5 or 6 are not shown in fig. 7, and the steps S501 or S601 described above further include S701. It should be noted that the same steps as those in the embodiment of fig. 5 or fig. 6 are not repeated here, please refer to the foregoing.
And S701, when the test progress reaches a test node where the developer has completed the correlation analysis of the version data, determining that the preset reminding information is third preset reminding information, and sending the third preset reminding information to first communication equipment corresponding to the tester information, wherein the third preset reminding information is used for reminding the tester to carry out the supplemental test on the version data after the correlation analysis.
In the present embodiment, the supplemental test includes a software characteristic supplemental test or a software defect supplemental test. After the developer performs correlation analysis on the version data, if the version data is found to have problems, the corresponding version data needs to be modified, or the version data has problems due to other reasons, so that the developer needs to be reminded to perform supplementary test on the version data subjected to the correlation analysis, and the version data released to the actual application environment is ensured not to have problems.
Optionally, after the preset reminding information is sent to the developer or the tester, the corresponding test progress is monitored regularly, and when the test progress is still the same as the test progress when the preset reminding information is sent to the developer or the tester, the preset reminding information is sent to the developer or the tester again. Therefore, the situation that the developer or the tester ignores the previous preset reminding information for some reasons and does not perform related operations in time is avoided.
On the basis of the embodiment shown in fig. 4, the application also proposes an embodiment of another monitoring method. The method further includes S405 and S406. It should be noted that the same steps as those in the embodiment of fig. 4 are not repeated here, please refer to the foregoing.
S405, monitoring a submission specification of the annotation information submitted to the version management system;
And S406, when the submission specification of the annotation information does not accord with the preset submission specification, sending a prompt for submitting the annotation information according to the preset submission specification.
In the present embodiment, the above-described submission specifications include, but are not limited to, whether ID information exists in the comment information, whether the ID information fills out the specifications, whether the ID information is associated with the test system, and the like. When a developer submits version data to the version management system, annotation information is required to be submitted along with the version data, and in order to ensure that the test progress can be obtained from the test system according to the ID information, the ID information is required to be associated with the test system, namely, the ID information is the same as the ID information stored in the test system; when the submission specification of the annotation information does not accord with the preset submission specification, the reminding information is popped up to inform a developer that the annotation information needs to be submitted according to the preset submission specification.
It should be understood that the sequence number of each step in the foregoing embodiment does not mean that the execution sequence of each process should be determined by the function and the internal logic, and should not limit the implementation process of the embodiment of the present application.
Corresponding to the monitoring method described in the above embodiments, fig. 8 shows a block diagram of a monitoring device 800 based on a version management system according to an embodiment of the present application, and for convenience of explanation, only a portion related to the embodiment of the present application is shown.
Referring to fig. 8, the apparatus includes:
A first obtaining module 801, configured to obtain annotation information and developer information in an update record when it is monitored that the version management system has the update record, where the annotation information includes ID information;
A determining module 802, configured to determine an ID type of the ID information, where the ID type includes a software characteristic ID type or a software defect ID type;
a second obtaining module 803, configured to obtain a test progress and user information corresponding to the ID information, where the user information includes tester information;
the reminding module is used for determining preset reminding information according to the ID type and/or the testing progress, and sending the testing progress and the preset reminding information to first communication equipment corresponding to the developer information or second communication equipment corresponding to the tester information.
It should be noted that, because the content of information interaction and execution process between the above devices/units is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, the specific names of the functional units and modules are only for distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.
Fig. 9 is a schematic structural diagram of a terminal device according to an embodiment of the present application. As shown in fig. 9, the terminal device 9 of this embodiment includes: at least one processor 90 (only one shown in fig. 9), a memory 91, and a computer program 92 stored in the memory 91 and executable on the at least one processor 90, the processor 90 implementing the steps in any of the various monitoring method embodiments described above when executing the computer program 92.
The terminal device 9 may be a computing device such as a desktop computer, a notebook computer, a palm computer, a cloud server, and the like, and specifically, an SVN server as described above. The terminal device may include, but is not limited to, a processor 90, a memory 91. It will be appreciated by those skilled in the art that fig. 9 is merely an example of the terminal device 9 and is not meant to be limiting as to the terminal device 9, and may include more or fewer components than shown, or may combine certain components, or different components, such as may also include input-output devices, network access devices, etc.
The Processor 90 may be a central processing unit (Central Processing Unit, CPU), the Processor 90 may also be other general purpose processors, digital signal processors (DIGITAL SIGNAL processors, DSP), application SPECIFIC INTEGRATED Circuit (ASIC), off-the-shelf Programmable gate array (Field-Programmable GATE ARRAY, FPGA) or other Programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 91 may in some embodiments be an internal storage unit of the terminal device 9, such as a hard disk or a memory of the terminal device 9. The memory 91 may in other embodiments also be an external storage device of the terminal device 9, such as a plug-in hard disk provided on the terminal device 9, a smart memory card (SMART MEDIA CARD, SMC), a Secure Digital (SD) card, a flash memory card (FLASH CARD) or the like. Further, the memory 91 may also include both an internal storage unit and an external storage device of the terminal device 9. The memory 91 is used for storing an operating system, application programs, boot loader (BootLoader), data, other programs, etc., such as program codes of the computer program. The memory 91 may also be used for temporarily storing data that has been output or is to be output.
Embodiments of the present application also provide a computer readable storage medium storing a computer program which, when executed by a processor, implements steps for implementing the various method embodiments described above.
Embodiments of the present application provide a computer program product which, when run on a mobile terminal, causes the mobile terminal to perform steps that enable the implementation of the method embodiments described above.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application may implement all or part of the flow of the method of the above embodiments, and may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, and when the computer program is executed by a processor, the computer program may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing device/terminal apparatus, recording medium, computer Memory, read-Only Memory (ROM), random access Memory (RAM, random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.
In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.
Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
In the embodiments provided in the present application, it should be understood that the disclosed apparatus/network device and method may be implemented in other manners. For example, the apparatus/network device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.
The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
The above embodiments are only for illustrating the technical solution of the present application, and not for limiting the same; although the application has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.
Claims (7)
1. A version management system-based monitoring method, comprising:
When the version management system is monitored to have an update record, annotation information and developer information in the update record are acquired, wherein the annotation information comprises ID information;
Determining an ID type of the ID information, wherein the ID type comprises a software characteristic ID type or a software defect ID type, the software characteristic ID type is an identifier for marking a software version in a software characteristic test, and the software defect ID type is an identifier for marking a software version in a software defect test;
Acquiring the test progress and the user information corresponding to the ID information, wherein the user information comprises tester information, and sending the ID information as a request for acquiring the test progress and the user information to the test system according to the association relation between the ID information and the test system so as to acquire the test progress and the user information corresponding to the ID information from the test system;
determining preset reminding information according to the ID type and/or the test progress, and sending the test progress and the preset reminding information to first communication equipment corresponding to the developer information or second communication equipment corresponding to the tester information;
The step of determining preset reminding information according to the ID type and/or the test progress, and sending the test progress and the preset reminding information to the first communication device corresponding to the developer information or the second communication device corresponding to the tester information, includes:
When the ID type is a software characteristic ID type and the test progress reaches a test node which starts to be tested, determining the preset reminding information as first preset reminding information, and sending the test progress and the first preset reminding information to first communication equipment corresponding to the developer information, wherein the first preset reminding information is used for reminding the developer to carry out correlation analysis on version data;
when the ID type is a software characteristic ID type and the test progress reaches a test node which does not start the test, determining the preset reminding information as second preset reminding information, and sending the test progress and the second preset reminding information to second communication equipment corresponding to the tester information, wherein the second preset reminding information is used for reminding a tester to test the software characteristic of the version data;
The step of determining preset reminding information according to the ID type and/or the test progress, and sending the test progress and the preset reminding information to the first communication device corresponding to the developer information or the second communication device corresponding to the tester information, includes:
When the ID type is a software defect ID type, determining that the preset reminding information is first preset reminding information, and sending the test progress and the first preset reminding information to first communication equipment corresponding to the developer information, wherein the first preset reminding information is used for reminding the developer of carrying out correlation analysis on version data;
After the test progress and the first preset reminding information are sent to the first communication device corresponding to the developer information, the method further comprises the following steps:
When the test progress reaches a test node which has completed the correlation analysis of the version data, determining that the preset reminding information is third preset reminding information, and sending the third preset reminding information to first communication equipment corresponding to the tester information, wherein the third preset reminding information is used for reminding the tester to carry out the supplementary test on the version data after the correlation analysis;
After the preset reminding information is sent to the developer or the tester, the corresponding testing progress is monitored regularly, and when the testing progress is still in the testing progress when the preset reminding information is sent to the developer or the tester, the preset reminding information is sent to the developer or the tester again.
2. The version management system-based monitoring method according to claim 1, wherein when it is monitored that the version management system has an update record, acquiring annotation information and developer information in the update record comprises:
monitoring version data in a version library of the version management system;
When new version data is added into the version library, the version management system is judged to have an update record, and annotation information and developer information in the update record are acquired.
3. The version management system-based monitoring method of claim 1, wherein the determining the ID type of the ID information comprises:
And acquiring a keyword field of the ID information, and determining an ID type corresponding to the keyword field.
4. The version management system-based monitoring method of claim 1, further comprising:
monitoring a submission specification of the annotation information submitted to the version management system;
And when the submission specification of the annotation information does not accord with the preset submission specification, sending a prompt for submitting the annotation information according to the preset submission specification.
5. A version management system-based monitoring device, comprising:
The first acquisition module is used for acquiring annotation information and developer information in the update record when the version management system is monitored to have the update record, wherein the annotation information comprises ID information;
The determining module is used for determining the ID type of the ID information, wherein the ID type comprises a software characteristic ID type or a software defect ID type, the software characteristic ID type is an identifier for marking a software version in one software characteristic test, and the software defect ID type is an identifier for marking a software version in one software defect test;
The second acquisition module is used for acquiring the test progress and the user information corresponding to the ID information, wherein the user information comprises tester information, and the ID information is used as a request for acquiring the test progress and the user information to the test system according to the association relation between the ID information and the test system so as to acquire the test progress and the user information corresponding to the ID information from the test system;
The reminding module is used for determining preset reminding information according to the ID type and/or the testing progress, and sending the testing progress and the preset reminding information to first communication equipment corresponding to the developer information or second communication equipment corresponding to the tester information;
The reminding module is specifically configured to determine that the preset reminding information is first preset reminding information when the ID type is a software characteristic ID type and the test progress reaches a test node that has started to be tested, and send the test progress and the first preset reminding information to a first communication device corresponding to the developer information, where the first preset reminding information is used to remind the developer to perform correlation analysis on version data;
when the ID type is a software characteristic ID type and the test progress reaches a test node which does not start the test, determining the preset reminding information as second preset reminding information, and sending the test progress and the second preset reminding information to second communication equipment corresponding to the tester information, wherein the second preset reminding information is used for reminding a tester to test the software characteristic of the version data;
When the ID type is a software defect ID type, determining that the preset reminding information is first preset reminding information, and sending the test progress and the first preset reminding information to first communication equipment corresponding to the developer information, wherein the first preset reminding information is used for reminding the developer of carrying out correlation analysis on version data;
After the test progress and the first preset reminding information are sent to the first communication device corresponding to the developer information, the method further comprises the following steps:
When the test progress reaches a test node which has completed the correlation analysis of the version data, determining that the preset reminding information is third preset reminding information, and sending the third preset reminding information to first communication equipment corresponding to the tester information, wherein the third preset reminding information is used for reminding the tester to carry out the supplementary test on the version data after the correlation analysis;
After the preset reminding information is sent to the developer or the tester, the corresponding testing progress is monitored regularly, and when the testing progress is still in the testing progress when the preset reminding information is sent to the developer or the tester, the preset reminding information is sent to the developer or the tester again.
6. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 4 when executing the computer program.
7. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the method according to any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911384597.3A CN111190824B (en) | 2019-12-28 | 2019-12-28 | Monitoring method, device, terminal equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911384597.3A CN111190824B (en) | 2019-12-28 | 2019-12-28 | Monitoring method, device, terminal equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111190824A CN111190824A (en) | 2020-05-22 |
| CN111190824B true CN111190824B (en) | 2024-04-26 |
Family
ID=70705914
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911384597.3A Active CN111190824B (en) | 2019-12-28 | 2019-12-28 | Monitoring method, device, terminal equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111190824B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112950138B (en) * | 2020-09-11 | 2024-03-12 | 深圳市明源云科技有限公司 | Collaborative development state management method, device and server |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105893050A (en) * | 2016-04-05 | 2016-08-24 | 延锋伟世通电子科技（南京）有限公司 | Method for carrying out overall lifecycle management on software project based on project lifecycle management (PLMS), subversion (SVN) and Jenkins |
| CN106201857A (en) * | 2015-05-05 | 2016-12-07 | 阿里巴巴集团控股有限公司 | The choosing method of test case and device |
| CN106354638A (en) * | 2016-08-29 | 2017-01-25 | 广州唯品会信息科技有限公司 | Automatic testing method and device based on lexical analysis |
| CN107463501A (en) * | 2017-08-11 | 2017-12-12 | 四川长虹电器股份有限公司 | A kind of defect management system for prompting and based reminding method |
| CN108304327A (en) * | 2018-02-02 | 2018-07-20 | 平安证券股份有限公司 | Static code scanning result treating method and apparatus |
| CN108932192A (en) * | 2017-05-22 | 2018-12-04 | 南京大学 | A kind of Python Program Type defect inspection method based on abstract syntax tree |
| CN109359028A (en) * | 2018-08-22 | 2019-02-19 | 平安科技（深圳）有限公司 | Code quality monitoring method, device, computer equipment and storage medium |
| CN109783128A (en) * | 2018-12-13 | 2019-05-21 | 平安普惠企业管理有限公司 | Code change notification method, equipment, storage medium and device |
| CN110399162A (en) * | 2019-07-09 | 2019-11-01 | 北京航空航天大学 | A kind of source code annotation automatic generation method |
-
2019
- 2019-12-28 CN CN201911384597.3A patent/CN111190824B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106201857A (en) * | 2015-05-05 | 2016-12-07 | 阿里巴巴集团控股有限公司 | The choosing method of test case and device |
| CN105893050A (en) * | 2016-04-05 | 2016-08-24 | 延锋伟世通电子科技（南京）有限公司 | Method for carrying out overall lifecycle management on software project based on project lifecycle management (PLMS), subversion (SVN) and Jenkins |
| CN106354638A (en) * | 2016-08-29 | 2017-01-25 | 广州唯品会信息科技有限公司 | Automatic testing method and device based on lexical analysis |
| CN108932192A (en) * | 2017-05-22 | 2018-12-04 | 南京大学 | A kind of Python Program Type defect inspection method based on abstract syntax tree |
| CN107463501A (en) * | 2017-08-11 | 2017-12-12 | 四川长虹电器股份有限公司 | A kind of defect management system for prompting and based reminding method |
| CN108304327A (en) * | 2018-02-02 | 2018-07-20 | 平安证券股份有限公司 | Static code scanning result treating method and apparatus |
| CN109359028A (en) * | 2018-08-22 | 2019-02-19 | 平安科技（深圳）有限公司 | Code quality monitoring method, device, computer equipment and storage medium |
| CN109783128A (en) * | 2018-12-13 | 2019-05-21 | 平安普惠企业管理有限公司 | Code change notification method, equipment, storage medium and device |
| CN110399162A (en) * | 2019-07-09 | 2019-11-01 | 北京航空航天大学 | A kind of source code annotation automatic generation method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111190824A (en) | 2020-05-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US12032554B2 (en) | Utilizing independently stored validation keys to enable auditing of instrument measurement data maintained in a blockchain | |
| CN111045756B (en) | Method, apparatus, computing device and medium for generating interface service | |
| US20180089436A1 (en) | Methods And Apparatus To Facilitate Blockchain-based Boot Tracking | |
| US10120783B2 (en) | Determining test case efficiency | |
| WO2018172838A1 (en) | Cognitive regulatory compliance automation of blockchain transactions | |
| US9280665B2 (en) | Fast and accurate identification of message-based API calls in application binaries | |
| WO2019071891A1 (en) | Code coverage analysis method and application server | |
| CN111211929A (en) | Fault positioning method, fault positioning device, control equipment and intelligent equipment | |
| CN110659206A (en) | Simulation architecture establishing method, device, medium and electronic equipment based on microservice | |
| CN111563257A (en) | Data detection method and device, computer readable medium and terminal equipment | |
| CN114491555A (en) | Equipment safety detection method and device, computer equipment and storage medium | |
| CN110059064B (en) | Log file processing method and device and computer readable storage medium | |
| CN111190824B (en) | Monitoring method, device, terminal equipment and storage medium | |
| CN112084114B (en) | Method and apparatus for testing interfaces | |
| CN111598544B (en) | Method and device for processing information | |
| CN111597093B (en) | Exception handling method, device and equipment thereof | |
| CN112015715A (en) | Industrial Internet data management service testing method and system | |
| US11423160B2 (en) | System for analysis and authorization for use of executable environment data in a computing system using hash outputs | |
| CN114371866A (en) | Version reconfiguration test method, device and equipment of service system | |
| CN113849331B (en) | Anomaly tracking method, system, device, equipment and medium of hybrid technology stack | |
| CN116488811B (en) | Method for dividing cipher boundary | |
| US11425123B2 (en) | System for network isolation of affected computing systems using environment hash outputs | |
| CN112417328B (en) | Webpage monitoring method and device | |
| US20240323209A1 (en) | System and method for data retention based on commonalities between data processing systems | |
| Malathi et al. | UVM Components for the Secure Hash 512 Algorithm |
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 |