CN111190824A - Monitoring method, monitoring device, terminal equipment and storage medium - Google Patents
Monitoring method, monitoring device, terminal equipment and storage medium Download PDFInfo
- Publication number
- CN111190824A CN111190824A CN201911384597.3A CN201911384597A CN111190824A CN 111190824 A CN111190824 A CN 111190824A CN 201911384597 A CN201911384597 A CN 201911384597A CN 111190824 A CN111190824 A CN 111190824A
- Authority
- CN
- China
- Prior art keywords
- information
- type
- test
- software
- preset reminding
- 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
- 238000000034 method Methods 0.000 title claims abstract description 62
- 238000012544 monitoring process Methods 0.000 title claims abstract description 44
- 238000012806 monitoring device Methods 0.000 title claims abstract description 8
- 238000012360 testing method Methods 0.000 claims abstract description 158
- 238000004891 communication Methods 0.000 claims abstract description 51
- 230000007547 defect Effects 0.000 claims abstract description 48
- 238000010219 correlation analysis Methods 0.000 claims description 26
- 238000004590 computer program Methods 0.000 claims description 20
- 230000008859 change Effects 0.000 abstract description 4
- 238000007726 management method Methods 0.000 description 25
- 230000008569 process Effects 0.000 description 14
- 238000010586 diagram Methods 0.000 description 8
- 238000012545 processing Methods 0.000 description 5
- 230000006870 function Effects 0.000 description 4
- 230000004044 response 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
- 238000011161 development Methods 0.000 description 3
- 238000004458 analytical method Methods 0.000 description 2
- 230000007849 functional defect Effects 0.000 description 2
- 230000000153 supplemental effect Effects 0.000 description 2
- 241000700605 Viruses Species 0.000 description 1
- 230000003321 amplification Effects 0.000 description 1
- 230000002155 anti-virotic effect Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000013500 data storage Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000001914 filtration Methods 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000012423 maintenance 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
- 238000003199 nucleic acid amplification method Methods 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
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3668—Software testing
- G06F11/3672—Test management
- G06F11/368—Test management for test version control, e.g. updating test cases to a new software version
Abstract
The application is applicable to the technical field of computers, and provides a monitoring method, a monitoring device, terminal equipment and a storage medium, wherein the monitoring method comprises the following steps: when the version management system is monitored to have an update record, acquiring annotation information and developer information in the update record, 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 test 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 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. By combining the updating record and the testing progress, developers or testers are intelligently reminded, the problem caused by software code change is prevented from flowing to practical application, and the best experience of customers is guaranteed.
Description
Technical Field
The present application belongs to the field of computer technologies, and in particular, to a monitoring method, an apparatus, a terminal device, and a storage medium.
Background
Version management is an important content of software development, and a code submission monitoring tool such as Commitmonitor, svnNitor SVN and the like can be used for guaranteeing that a code is the latest version in real time. In the development process of a software project, after software codes are changed, the codes need to be tested and subjected to correlation analysis. However, the current monitoring tool is not intelligent enough, and does not have the capability of prompting developers to perform correlation analysis on codes or testing the codes by testers, so that problems existing in software codes which are not tested and subjected to correlation analysis are caused to flow into an actual application environment, and the satisfaction degree of customers on the software is reduced.
Disclosure of Invention
The embodiment of the application provides a monitoring method, a monitoring device, terminal equipment and a storage medium, and 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, acquiring annotation information and developer information in the update record, 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 test 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 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.
According to the embodiment of the application, the software code can be monitored to be changed in time by monitoring the update record of the version management system; acquiring annotation information in the update record, and acquiring ID information corresponding to software characteristic test or software defect test according to the annotation information so as to obtain the test type of the software and conveniently remind a corresponding user to perform related operation; and obtaining the test progress according to the ID information, and when the test progress reaches a preset test node, timely notifying developers or testers corresponding to the test node so that the developers or the testers can perform correlation analysis or test on the codes in time, intelligently reminding the developers or the testers, avoiding the problem caused by the change of the software codes from flowing to practical application, and ensuring the optimal experience of customers.
In a second aspect, an embodiment of the present application provides a monitoring device based on a version management system, including:
the version management system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring annotation information in an update record when the version management system is monitored to have the update record, and 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 second acquisition module is used for acquiring the test progress and the user information corresponding to the ID information, wherein the user information comprises developer information and tester information;
and the reminding module is used for 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 equipment corresponding to the developer information or the second communication equipment corresponding to the tester information.
In a third aspect, an embodiment of the present application provides a terminal device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, where the processor implements the monitoring method described in any one of the above first aspects when executing the computer program.
In a fourth aspect, the present application provides a computer-readable storage medium having a computer program, where the computer program is executed by a processor to implement the monitoring method in any one of the above first aspects.
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 execute the monitoring method described in any one of the above first aspects.
It is understood that the beneficial effects of the second aspect to the fifth aspect can be referred to the related description of the first aspect, and are not described herein again.
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 embodiments or the prior art descriptions will be briefly described 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 exercise.
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 provided by an embodiment of the present application;
fig. 3 is a schematic diagram of an SVN server to which the monitoring method provided in an embodiment of the present application is applied;
FIG. 4 is a schematic flow chart of a monitoring method according to an embodiment of the present application;
FIG. 5 is a schematic flow chart of a monitoring method according to another embodiment of the present application;
FIG. 6 is a schematic flow chart of a monitoring method according to another embodiment of the present application;
FIG. 7 is a schematic 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 provided in 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 particular system structures, 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 will 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 this specification and the appended claims refers to and includes any and all possible combinations of one or more of the associated listed items.
As used in this specification and the appended claims, the term "if" may be interpreted contextually as "when", "upon" or "in response to" determining "or" in response to detecting ". Similarly, the phrase "if it is determined" or "if a [ described condition or event ] is detected" may be interpreted contextually to mean "upon determining" or "in response to determining" or "upon detecting [ described condition or event ]" or "in response to detecting [ described condition or event ]".
Furthermore, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used for distinguishing between descriptions and not necessarily for describing or implying relative importance.
Reference throughout this 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 present application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," or the like, in various places throughout this specification are not necessarily all referring to the same embodiment, but rather "one or more but not all embodiments" unless specifically stated 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 development and maintenance process of a software project, software code (version data) is often modified to update a software version, and in order to ensure that no new problem occurs when the software code is modified, software defect testing, software characteristic testing or correlation analysis needs to be performed on the software code. However, developers or testers are busy in working tasks and do not take test progress or update records into consideration, so that software defect testing, software characteristic testing or correlation analysis are not performed on software codes in time, and the current monitoring tool is not intelligent enough and can only remind a user of the current update record, so that the user only knows the update record and does not know which operation needs to be performed next, and thus the reminding information is easily ignored by the user, so that the reminding information is invalid under many conditions, problems flow to the actual application process, and poor experience is brought to the user.
Therefore, a monitoring method based on a version management system is needed, which realizes the processes of monitoring the update record of the version management system, obtaining the test progress, combining the update record with the test progress, and reminding the corresponding user to perform related operations.
Among them, a software Defect (Defect, also called BUG) is a problem, error or hidden functional Defect existing in computer software or program that destroys normal operation capability, and the existence of the Defect may cause a software product to be unable to meet the user's requirement to some extent. Software defect testing includes, but is not limited to, functional defect testing, system defect testing, process 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 performance indexes under normal environment and system conditions in a repeated use mode, and finding out performance bottlenecks of software, so that the software performance is optimized. 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 diagram of fig. 1, there are two places of "business unit codes," in the default state, the "business unit code" in the "custom header" should be the same as the "business unit code" in another place, after the software code modifies any place of the "business unit code" into another name, the "business unit code" in another place should also be modified correspondingly, and the correlation analysis is to verify whether other codes related to the modified codes in the software code are also modified correspondingly, so as to ensure the consistency of the associated codes.
Fig. 2 shows a schematic diagram of a system provided in an embodiment of the present application, where the system includes an SVN (version management) server 201, a testing system 202, a first communication device 203, and a second communication device 204, and the SVN server 201 communicates with the testing 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 can be applied to the SVN server 201. The SVN server 201 is a machine operated by a version management system, and the operation mode of the SVN server can be independent server operation or operation by means of apache. The SVN server can monitor the submission condition of the software code and store the version data corresponding to the software code, and the storage mode of the version data can be BDB (transaction security table type) or FSFS (storage system without database).
The test system 202 is a system for testing software defects or software characteristics of a software version, and records test progress, tester information, and names of piece characteristics or software defects corresponding to test types including but not limited to the software version.
The first communication device 203 and the second communication device 204 are 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, an in-vehicle device, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, and a Personal Digital Assistant (PDA), and the embodiment of the present application does not limit the specific types of the first communication device 203 and the second communication device 204.
Fig. 3 shows an example of an SVN server 201 that may include a processor 301, a memory 302, a communication module 303, and a power management module 304, among others.
The processor 301 may include one or more of a central processing unit (cpu), an Application Processor (AP), and the like. The processor 301 may be a neural hub and a command center of a wireless router. The processor 302 may generate operation control signals according to the instruction operation code and the timing signal, and perform control of instruction fetching and instruction execution. The memory 302 may be used to store computer-executable program code, which includes instructions. Processor 301 executes various functional applications and data processing of SVN server 201 by executing instructions stored in memory 302. The memory 302 may include a program storage area and a data storage area, such as data with a played sound signal. For example, the memory may be a double data rate synchronous dynamic random access memory DDR or a Flash memory Flash, etc.
The communication module 303 may be a solution including Wireless Local Area Networks (WLANs), bluetooth, Zigbee, a mobile communication network, Global Navigation Satellite System (GNSS), Frequency Modulation (FM), Near Field Communication (NFC), Infrared (IR), and other communications, which is 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, perform frequency modulation and filtering processing on 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, perform frequency modulation and amplification on the signal, and convert the signal into electromagnetic waves through the antenna to radiate the electromagnetic waves.
The power management module 304 may receive input from a battery and/or charger to power the processor 301, the memory 302, the communication module 303, and the like.
It should be noted that fig. 3 does not limit the structure of the SVN server 201, and may include more or less components than those shown, or 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 the like.
Fig. 4 shows a schematic flow chart of the monitoring method based on the version management system provided in the present application, and the method can be applied to the SVN server 201 described above by way of example and not limitation, and the version management system is built on the SVN server.
S401, when it is monitored that the version management system has an update record, obtaining annotation information and developer information in the update record, 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 submitting software code), comment information, and path information for modifying the file. The comment information includes ID information, an association relationship 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 the ID type of the ID information, wherein the ID type comprises a software characteristic ID type or a software defect ID type.
And analyzing the ID information in the annotation information, and determining the ID type of the ID information according to the ID information and a preset determination rule. The software property ID type is an identifier for marking a software version in one software property test, and the software defect ID type is an identifier for marking a software version in one software defect test.
It should be noted that, when the ID type is the software defect ID type, it indicates that the software has completed the software defect test, because it is only known that the software defect is a software defect if the software defect test is completed. When the ID type is a software property ID type, the software does not necessarily start or complete a software property test.
And S403, acquiring the test progress and the user information corresponding to the ID information, wherein the user information comprises developer information and tester information.
Optionally, according to the association relationship between the ID information and the test system, the ID information is used as an entry parameter to send a request for obtaining the test progress and the user information to the test system, so as to obtain 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 personnel 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 test schedule includes a test schedule for a software feature test including, but not limited to, started feature tests, not started feature tests, completed correlation analyses, not started supplemental tests, and started supplemental tests, or a test schedule for a software bug test including, but not limited to, completed bug tests and completed correlation analyses. 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, the process node reached by the test progress is further determined, and corresponding preset reminding information is determined according to the process node reached by the test progress; when the ID type is the software defect ID type, it indicates that the software defect test is completed, and may be determined as preset reminding information for reminding a developer to perform correlation analysis.
The preset reminding information includes, but is not limited to, reminding information for reminding developers to perform correlation analysis, reminding information for reminding testers to perform characteristic test, and reminding information for reminding testers to perform supplementary test.
Optionally, the sending mode of the preset reminding information includes, but is not limited to, sending an email, sending a short message, sending a real-time chat tool (such as a QQ or a WeChat), and computer IP popup.
In a possible implementation manner, a computer IP address of a developer is acquired, a piece of data carrying the preset reminding information is sent to the computer IP address, after the computer receives a receiving request of the data, information such as a data source of the data is verified, the data is formally received after the verification is passed, the received data is analyzed, and the preset reminding information is displayed in a pop-up frame manner to remind the developer to perform correlation analysis on the version data. The information such as the data source is verified so as to avoid the data carrying malicious viruses sent by the data as an unknown source and avoid being intercepted by computer antivirus software. Furthermore, the data can be encrypted in a preset encryption mode and then decrypted by the computer in a corresponding preset decryption mode, so that the safety of the data is improved.
In the embodiment, the change condition of the software code can be monitored in time by monitoring the update record of the version management system; acquiring annotation information in the update record, and acquiring ID information corresponding to software characteristic test or software defect test according to the annotation information so as to obtain the test type of the software and conveniently remind a corresponding user to perform related operation; acquiring the testing progress according to the ID information so as to send direct and effective reminding information to the user by combining the updating record and the testing progress; specifically, when the test progress reaches the preset test node, developers or testers corresponding to the test node are notified in time, so that the developers or the testers can perform correlation analysis or test on the code in time, the developers or the testers are intelligently reminded, the problem caused by software code change is prevented from flowing into practical application, and the best experience of customers is guaranteed.
On the basis of the embodiment shown in fig. 4, the present application also proposes another embodiment of the monitoring method. The step S401 specifically includes S4011 and S4012. It should be noted that the steps that are the same as those in the embodiment of fig. 4 are not repeated herein, please refer to the foregoing description.
S4011, monitoring version data in a version library of the version management system;
s4012, when new version data is added into 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, and the version data of the version library is recorded in the SVN log. When new data exists in the SVN log and new version data is recorded in the SVN log and added into the version library, the situation shows that a developer sends an update record containing the version data, annotation information, developer information and other information to the version management system, so that the annotation information and the developer information in the update record are obtained.
Whether new version data are added into the version library is monitored, so that whether the software version is changed or not can be timely and accurately known, and a user is timely reminded of relevant operations.
On the basis of the embodiment shown in fig. 4, the present application also proposes another embodiment of the monitoring method. Step S402 specifically includes S4021 to S4023. It should be noted that the steps that are the same as those in the embodiment of fig. 4 are not repeated herein, please refer to the foregoing description.
S4021, acquiring the key word field of the ID information, and determining the ID type corresponding to the key word field.
In this embodiment, the ID information includes software feature ID information or software defect ID information, and the software feature ID information or software defect ID information may include a software name ID, a test type (software feature 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 that the test type is 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 that the test type is the software characteristic test type, and TX0001 represents the first software characteristic test. Therefore, the ID information in the analyzed comment information may be determined by analyzing whether the ID information in the comment information includes a key field indicating a test type and determining whether the key field of the test type indicates a software characteristic test or a software defect test, so as to determine whether the ID information is software characteristic ID information or software defect ID information.
It should be understood that the keyword 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, other forms of character combinations may also be used, and are not described herein again.
On the basis of the embodiment shown in fig. 4, fig. 5 also proposes another embodiment of the monitoring method. As shown in fig. 5, the step S404 specifically includes S501 and S502. It should be noted that the steps that are the same as those in the embodiment of fig. 4 are not repeated herein, please refer to the foregoing description.
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 developers to perform correlation analysis on version data.
The started test is specifically a started characteristic test. When the software characteristic test is started, the test is indicated to be completed soon, in order to accelerate the progress of the software development project, developers are reminded to carry out correlation analysis on the version data, and when the developers start equipment to prepare for the correlation analysis, the software characteristic test is basically finished, and the correlation analysis can be directly carried out.
S502, when the ID type is the software characteristic ID type and the test progress reaches a test node which does not start to be tested, 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 carry out software characteristic test on the version data.
The above-described non-start test is a non-start characteristic test. When the software characteristic test is not started, the software characteristic test is performed by the developer, and the software characteristic test is performed by the software version to be tested and the characteristic name of the software to be tested are recorded in the test system. Accurate and effective reminding information is provided for developers or testers in combination with the test progress, and the development efficiency of the software development project is effectively improved.
On the basis of the embodiment shown in fig. 4, fig. 6 also proposes another embodiment of the monitoring method. 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 steps that are the same as those in the embodiment of fig. 4 are not repeated herein, please refer to the foregoing description.
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 developer information, wherein the first preset reminding information is used for reminding developers to perform correlation analysis on version data.
In this embodiment, when the ID type is a software defect ID type, since a software defect can be found only after the test is completed, the software defect test is completed, and at this time, a developer needs to be reminded to perform correlation analysis on version data after the software defect test. Therefore, the problem of the software version is prevented from flowing into practical application, and the optimal experience of a client is guaranteed.
On the basis of the embodiments shown in fig. 5 or fig. 6, the present application also proposes another embodiment of the monitoring method. The same steps as those in the embodiment of fig. 5 or 6 are not shown in fig. 7, and S701 is further specifically included after the above step S501 or S601. It should be noted that the steps that are the same as those in the embodiment of fig. 5 or fig. 6 are not repeated herein, please refer to the foregoing.
S701, when it is monitored that the test progress reaches a test node where the developer completes 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 perform supplementary test on the version data after the correlation analysis.
In the present embodiment, the supplementary test includes a software characteristic supplementary test or a software defect supplementary test. Since the developer finds that the version data has a problem after performing correlation analysis on the version data, the developer needs to modify the corresponding version data, or the developer has a problem with the version data due to other reasons, the developer needs to remind the tester to perform a supplementary test on the version data after performing the correlation analysis, so that the version data issued to the actual application environment is guaranteed not to have a problem.
Optionally, after the preset reminding information is sent to the developer or the tester, the corresponding test progress is monitored at regular time, 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 and does not perform related operations in time due to some reasons is avoided.
On the basis of the embodiment shown in fig. 4, the present application also proposes another embodiment of the monitoring method. The method further includes S405 and S406. It should be noted that the steps that are the same as those in the embodiment of fig. 4 are not repeated herein, please refer to the foregoing description.
S405, monitoring a submission specification of the annotation information submitted to the version management system;
s406, when the submission specification of the annotation information does not conform to the preset submission specification, sending a prompt for submitting the annotation information according to the preset submission specification.
In this embodiment, the submission specification includes, but is not limited to, whether ID information exists in the comment information, whether ID information fills in the specification, whether ID information is associated with a test system, and the like. When a developer submits version data to a version management system, annotation information needs to be submitted together with the version data, and in order to ensure that a test progress can be obtained from a test system according to ID information, the ID information needs to be associated with the test system, namely the ID information is the same as the ID information stored in the test system; and when the submission specification of the annotation information does not accord with the preset submission specification, popping up reminding information to inform developers of the need of submitting the annotation information according to the preset submission specification.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
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, which corresponds to the monitoring method described in the foregoing embodiment.
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 information of a tester;
and the reminding module is used for 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 equipment corresponding to the developer information or the second communication equipment corresponding to the tester information.
It should be noted that, for the information interaction, execution process, and other contents between the above-mentioned devices/units, the specific functions and technical effects thereof are based on the same concept as those of the embodiment of the method of the present application, and specific reference may be made to the part of the embodiment of the method, which is not described herein again.
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions. Each functional unit and module in the embodiments may be integrated in one processing unit, or each unit may exist alone physically, or two or more units are integrated in one unit, and the integrated unit may be implemented in a form of hardware, or in a form of software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working processes of the units and modules in the system may refer to the corresponding processes in the foregoing method embodiments, and are 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, a palm computer, and a cloud server, and specifically, the SVN server is described above. The terminal device may include, but is not limited to, a processor 90, a memory 91. Those skilled in the art will appreciate that fig. 9 is only an example of the terminal device 9, and does not constitute a limitation to the terminal device 9, and may include more or less components than those shown, or combine some components, or different components, for example, and may further include an input/output device, a network access device, and the like.
The Processor 90 may be a Central Processing Unit (CPU), and the Processor 90 may be other general purpose Processor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), an off-the-shelf Programmable Gate Array (FPGA) or other Programmable logic device, discrete Gate or transistor logic, discrete hardware components, etc. 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 also be an external storage device of the terminal device 9 in other embodiments, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), and the like provided on the terminal device 9. 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, an application program, a BootLoader (BootLoader), data, and other programs, such as program codes of the computer program. The memory 91 may also be used to temporarily store data that has been output or is to be output.
The embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored, and when the computer program is executed by a processor, the computer program implements the steps in the above-mentioned method embodiments.
The embodiments of the present application provide a computer program product, which when running on a mobile terminal, enables the mobile terminal to implement the steps in the above method embodiments when executed.
The integrated unit, if implemented in the form of a software functional unit and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, all or part of the processes in the methods of the embodiments described above can be implemented by a computer program, which can be stored in a computer-readable storage medium and can implement the steps of the embodiments of the methods described above when the computer program is executed by a processor. Wherein the computer program comprises computer program code, which may be in the form of source code, object code, an 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 apparatus/terminal apparatus, a recording medium, computer Memory, Read-Only Memory (ROM), random-access Memory (RAM), an electrical carrier signal, a telecommunications signal, and a software distribution medium. Such as a usb-disk, a removable hard disk, a magnetic or optical disk, etc. In certain jurisdictions, computer-readable media may not be an electrical carrier signal or a telecommunications signal in accordance with legislative and patent practice.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and reference may be made to the related descriptions of other embodiments for parts that are not described or illustrated in a certain embodiment.
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 implementation. 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 ways. For example, the above-described apparatus/network device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and there may be other divisions when actually implementing, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not implemented. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed 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 can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present application, and not for limiting the same; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present application and are intended to be included within the scope of the present application.
Claims (10)
1. A monitoring method based on a version management system is characterized by comprising the following steps:
when the version management system is monitored to have an update record, acquiring annotation information and developer information in the update record, 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 test 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 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.
2. The version management system-based monitoring method according to claim 1, wherein when it is monitored that there is an update record in the version management system, acquiring annotation information and developer information in the update record includes:
monitoring version data in a version library of the version management system;
and when new version data is added into the version library, judging that the version management system has an update record, and acquiring annotation information and developer information in the update record.
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 key word field of the ID information, and determining an ID type corresponding to the key word field.
4. The monitoring method based on the version management system as claimed in claim 1, wherein the determining a preset reminding message according to the ID type and/or the test progress, and sending the test progress and the preset reminding message to a first communication device corresponding to the developer information or a second communication device corresponding to the tester information comprises:
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 the developer information, wherein the first preset reminding information is used for reminding the developer to perform correlation analysis on the version data;
and 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 perform software characteristic testing on the version data.
5. The monitoring method based on the version management system as claimed in claim 1, wherein the determining a preset reminding message according to the ID type and/or the test progress, and sending the test progress and the preset reminding message to a first communication device corresponding to the developer information or a second communication device corresponding to the tester information comprises:
and 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 perform correlation analysis on the version data.
6. The monitoring method based on the version management system as claimed in claim 4 or 5, wherein after the sending the test progress and the first preset reminding information to the first communication device corresponding to the developer information, the method further comprises:
when it is monitored that the test progress reaches a test node where correlation analysis of the version data is completed, 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 perform supplementary test on the version data after the correlation analysis.
7. 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 conform to the preset submission specification, sending a prompt for submitting the annotation information according to the preset submission specification.
8. A monitoring device based on version management system, characterized by comprising:
the version management system comprises a first acquisition module, a second acquisition module and a third acquisition module, wherein the first acquisition module is used for acquiring annotation information and developer information in an update record when the version management system is monitored to have the update record, and 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 second acquisition module is used for acquiring the test progress and the user information corresponding to the ID information, and the user information comprises tester information;
and the reminding module is used for 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 equipment corresponding to the developer information or the second communication equipment corresponding to the tester information.
9. 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 7 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored which, when being executed by a processor, carries out the method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911384597.3A CN111190824B (en) | 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 | Monitoring method, device, terminal equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111190824A true CN111190824A (en) | 2020-05-22 |
| CN111190824B CN111190824B (en) | 2024-04-26 |
Family
ID=
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112950138A (en) * | 2020-09-11 | 2021-06-11 | 深圳市明源云科技有限公司 | Collaborative development state management method and 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 |
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 |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112950138A (en) * | 2020-09-11 | 2021-06-11 | 深圳市明源云科技有限公司 | Collaborative development state management method and device and server |
| CN112950138B (en) * | 2020-09-11 | 2024-03-12 | 深圳市明源云科技有限公司 | Collaborative development state management method, device and server |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11321305B2 (en) | Utilizing independently stored validation keys to enable auditing of instrument measurement data maintained in a blockchain | |
| EP3382554B1 (en) | Metrics collection and aggregation for distributed software services | |
| WO2018172838A1 (en) | Cognitive regulatory compliance automation of blockchain transactions | |
| CN109558746B (en) | Data desensitization method and device, electronic equipment and storage medium | |
| CN113268336B (en) | Service acquisition method, device, equipment and readable medium | |
| CN109726108B (en) | Front-end code testing method, device, system and medium based on analog data | |
| CN109376534B (en) | Method and apparatus for detecting applications | |
| CN112163412B (en) | Data verification method and device, electronic equipment and storage medium | |
| CN110659206A (en) | Simulation architecture establishing method, device, medium and electronic equipment based on microservice | |
| CN110688428B (en) | Method and device for issuing intelligent contracts | |
| CN110764996A (en) | Contract testing method, system, storage medium and terminal equipment | |
| CN110059064B (en) | Log file processing method and device and computer readable storage medium | |
| CN112948224A (en) | Data processing method, device, terminal and storage medium | |
| CN111563257A (en) | Data detection method and device, computer readable medium and terminal equipment | |
| CN114239026A (en) | Information desensitization conversion processing method, device, computer equipment and storage medium | |
| CN111190824B (en) | Monitoring method, device, terminal equipment and storage medium | |
| CN111190824A (en) | Monitoring method, monitoring device, terminal equipment and storage medium | |
| CN113053531B (en) | Medical data processing method, medical data processing device, computer readable storage medium and equipment | |
| CN112882948A (en) | Stability testing method, device and system for application and storage medium | |
| CN114491555A (en) | Equipment safety detection method and device, computer equipment and storage medium | |
| CN114116480A (en) | Method, device, medium and equipment for determining application program test coverage rate | |
| CN114968696A (en) | Index monitoring method, electronic equipment and chip system | |
| CN114371866A (en) | Version reconfiguration test method, device and equipment of service system | |
| CN108288135B (en) | System compatibility method and device, computer readable storage medium and electronic equipment | |
| CN112379967A (en) | Simulator detection method, device, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant |