CN110134595B - Analysis method, analysis device and computer equipment before SVN (scalable vector network) resource library test - Google Patents
Analysis method, analysis device and computer equipment before SVN (scalable vector network) resource library test Download PDFInfo
- Publication number
- CN110134595B CN110134595B CN201910319560.6A CN201910319560A CN110134595B CN 110134595 B CN110134595 B CN 110134595B CN 201910319560 A CN201910319560 A CN 201910319560A CN 110134595 B CN110134595 B CN 110134595B
- Authority
- CN
- China
- Prior art keywords
- version
- target
- file
- change
- policy
- 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
- 238000012360 testing method Methods 0.000 title claims abstract description 103
- 238000004458 analytical method Methods 0.000 title claims abstract description 88
- 230000008859 change Effects 0.000 claims abstract description 386
- 238000000034 method Methods 0.000 claims abstract description 22
- 230000009471 action Effects 0.000 claims description 138
- 230000000875 corresponding effect Effects 0.000 claims description 133
- 230000037430 deletion Effects 0.000 claims description 77
- 238000012217 deletion Methods 0.000 claims description 77
- 230000004048 modification Effects 0.000 claims description 70
- 238000012986 modification Methods 0.000 claims description 70
- 238000004590 computer program Methods 0.000 claims description 13
- 238000001514 detection method Methods 0.000 claims description 6
- 238000000605 extraction Methods 0.000 claims description 2
- 238000007792 addition Methods 0.000 description 26
- 238000010586 diagram Methods 0.000 description 3
- 238000004891 communication Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 230000009977 dual effect Effects 0.000 description 1
- 230000003068 static effect Effects 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)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to the technical field of cloud testing, in particular to an analysis method, an analysis device and computer equipment before SVN resource library testing. The method comprises the following steps: detecting whether a version submission exists in the SVN resource library; if the SVN resource inventory is detected to be submitted in the version, acquiring a submitted target version; comparing the target version with the version to be compared to obtain a change file; judging the change type of the change file; matching corresponding strategies in a strategy library according to the change types of the change files to obtain target strategies; analyzing character string rules in the change file according to analysis before testing the change file by the target strategy to obtain target character string rules; and matching the target character string rule, and marking the matched output information in the corresponding character string to form a report file. The method solves the problems that in the existing test mode, analysis before test is not performed, the whole new version is tested, the test range is wide, and the test time is long.
Description
Technical Field
The application relates to the technical field of cloud testing, in particular to an analysis method, an analysis device and computer equipment before SVN resource library testing.
Background
At present, the update period of the version is faster and faster, and when a new version appears, test analysis needs to be performed, and in the existing test mode, the whole new version is tested, so that the problems of wide test range and long test time are caused.
Content of the application
Aiming at the defects of the prior art, the application provides an analysis method, an analysis device and computer equipment before SVN resource library test, which aim to solve the problems that in the existing test mode, the whole new version is tested without analysis before test, so that the test range is wide and the test time is long.
The technical scheme provided by the application is as follows:
A method of analysis prior to testing of an SVN resource library, the method comprising:
Detecting whether a version submission exists in the SVN resource library;
If the SVN resource inventory is detected to be submitted in the version, acquiring a submitted target version;
Comparing the target version with the version to be compared to obtain a change file;
judging the change type of the change file;
matching corresponding strategies in a strategy library according to the variation category of the variation file to obtain a target strategy;
analyzing character string rules in the change file according to the analysis before the test of the change file by the target strategy to obtain target character string rules;
Matching the target character string rule with a preset character string rule in the target strategy and an output information relation table, and marking the matched output information in the corresponding character string to form a report file, wherein the output information comprises analysis information and risk focus information.
Further, the step of comparing the target version with the version to be compared to obtain the change file includes:
Comparing the target version with the version to be compared, and judging whether a new added, modified or deleted file exists in the target version;
If the new file is added, modified or deleted, the corresponding file is acquired, and the changed file is acquired.
Further, the step of determining the change type of the change file includes:
if the change file is a newly added file, judging that the change type of the change file is the newly added type;
if the change file is a modified file, judging that the change type of the change file is a modified type;
and if the change file is a deleted file, judging that the change type of the change file is a deleted type.
Further, the step of matching the corresponding policy in the policy library according to the change category of the change file to obtain the target policy includes:
if the change category of the change file is a new addition category, matching the new addition category in the policy library to a new addition category policy to obtain a target policy;
if the change category of the change file is a modification category, matching the modification category in the policy base to a modification category policy to obtain a target policy;
and if the change category of the change file is a deletion category, matching the deletion category in the policy library to a deletion category policy to obtain a target policy.
Further, the step of analyzing the change file before the test according to the target policy includes:
when the target policy is a deletion category policy, matching the target policy in an action library to the action library of the deletion category;
Acquiring the suffix name of the change file;
Matching the suffix name of the change file in the action library of the deletion category to corresponding actions;
And executing analysis before testing on the change file according to the action matched with the corresponding action.
Further, the step of analyzing the change file before the test according to the target policy includes:
when the target strategy is a newly added type strategy, matching the target strategy in an action library to the action library of the newly added type;
Acquiring the suffix name of the change file;
Matching the suffix name of the change file in the action library of the newly added category to corresponding actions;
And executing analysis before testing on the change file according to the action matched with the corresponding action.
Further, the step of analyzing the change file before the test according to the target policy includes:
when the target policy is a modified class policy, matching the target policy in an action library to a modified class action library;
comparing the change file with the file corresponding to the version to be compared to obtain a difference part;
extracting a code format from the difference portion;
Matching the extracted code format in the action library of the modification category to corresponding actions;
and executing analysis before testing of the difference part according to the action matched with the corresponding action.
The application also provides an analysis device before SVN resource library test, which comprises:
the detection module is used for detecting whether the version submission exists in the SVN resource library;
If the SVN resource inventory is detected to be submitted in the version, acquiring a submitted target version;
the comparison module is used for comparing the target version with the version to be compared to obtain a change file;
The judging module is used for judging the change type of the change file;
the matching module is used for matching corresponding strategies in the strategy library according to the variation category of the variation file to obtain a target strategy;
The analysis module is used for analyzing the character string rule in the change file according to the analysis before the test of the change file by the target strategy to obtain a target character string rule;
the output module is used for matching the target character string rule with a preset character string rule in the target strategy and an output information relation table, marking the matched output information in a corresponding character string to form a report file, wherein the output information comprises analysis information and risk focus information.
The application also provides a computer device comprising a memory storing a computer program and a processor implementing the steps of any of the methods described above when the processor executes the computer program.
The application also provides a computer readable storage medium having stored thereon a computer program which when executed by a processor performs the steps of the method of any of the preceding claims.
According to the technical scheme, the application has the beneficial effects that: detecting that a version of the SVN resource library is submitted, acquiring a submitted target version, comparing the target version with a version to be compared, acquiring a change file according to a comparison result, matching a corresponding strategy in a strategy library according to a change category of the change file, acquiring a target strategy, analyzing character string rules in the change file according to the analysis before testing the change file by the target strategy, and acquiring target character string rules; the method comprises the steps of matching target character string rules, marking matched output information in corresponding character strings to form a report file, and further testing the whole version in a targeted mode without testing the whole version.
Drawings
FIG. 1 is a flow chart of an analysis method before SVN resource library testing, which is provided by an embodiment of the application;
FIG. 2 is a functional block diagram of an analysis device before testing an SVN resource library according to an embodiment of the present application;
Fig. 3 is a schematic block diagram of a computer device to which an embodiment of the present application is applied.
Detailed Description
The present application will be described in further detail with reference to the drawings and examples, in order to make the objects, technical solutions and advantages of the present application more apparent. It should be understood that the specific embodiments described herein are for purposes of illustration only and are not intended to limit the scope of the application.
As shown in fig. 1, an embodiment of the present application provides an analysis method before testing an SVN resource library, where the method includes the following steps:
step S101, detecting whether a version submission exists in the SVN resource library.
Configuring an account number and a password connected with an SVN resource library in a configuration file, establishing communication connection with the SVN resource library according to the account number and the password in the configuration file, and detecting whether version submission exists in the SVN resource library after establishing connection with the SVN resource library.
Step S102, if the SVN resource inventory is detected to be submitted in the version, acquiring the submitted target version.
If the SVN repository is detected to be submitted by the version, the version is marked, and after the version is submitted, the version is acquired, so that the submitted target version is acquired.
Step S103, comparing the target version with the version to be compared to obtain a change file.
After the target version is obtained, comparing the target version with the version to be compared, and obtaining the change file according to the comparison result.
In this embodiment, the version to be compared is the last version of the target version, for example, the version number of the target version is 18192, the version numbers of the existing versions are 18191 and 18190, the version number of the last version of the target version is 18191 according to the naming rule of the version numbers, for this reason, the version number of the version to be compared is 18191, or taking the uploading time as an example, the uploading time of the target version is the current uploading time of the existing version is the last wednesday and the last monday, and the version number of the last version of the target version is the version of the last monday according to the rule of the uploading time, so that the version numbers of the versions to be compared are the versions of the last monday.
In some embodiments, the version to be compared is a specified version of the user input.
In the present embodiment, before step S103, it includes:
Detecting whether a user inputs a designated version as a version to be compared;
if the appointed version input by the user is detected to be used as the version to be compared, acquiring the appointed version input by the user, and acquiring the version to be compared;
if the fact that the user does not input the appointed version as the version to be compared is detected, the last version of the target version is obtained, and the version to be compared is obtained.
After the target version is acquired, the version to be compared is required to be acquired, whether a user inputs the designated version as the version to be compared is detected, if the designated version input by the user is detected as the version to be compared, the designated version input by the user is acquired, and after the designated version input by the user is acquired, the designated version input by the user is taken as the version to be compared, so that the version to be compared is acquired. If the fact that the user does not input the appointed version as the version to be compared is detected, the last version of the target version is obtained, and the version to be compared is obtained.
In the present embodiment, in step S103, it includes:
Comparing the target version with the version to be compared, and judging whether a new added, modified or deleted file exists in the target version;
If the new file is added, modified or deleted, the corresponding file is acquired, and the changed file is acquired.
After the target version is obtained, comparing the target version with the version to be compared, and obtaining a difference part of the target version and the version to be compared according to the comparison, wherein the specific type of the difference part comprises new addition, modification and deletion, judging whether the new addition, modification or deletion files exist in the target version according to the specific type of the difference part, and obtaining the corresponding files if the new addition, modification or deletion files exist, so as to obtain the change files.
Step S104, judging the change type of the change file.
After the change file is acquired, the change type of the change file is judged, and the change type of the change file is judged to be a new type, a deleted type or a modified type.
In the present embodiment, after step S103, before step S104, it includes:
marking the change category of the change file.
When comparing the target version with the version to be compared, a difference part between the target version and the version to be compared can be obtained, the specific type of the difference part comprises new addition, modification and deletion, whether the new addition, modification or deletion files exist in the target version is judged according to the specific type of the difference part, if the new addition, modification or deletion files exist, the corresponding files are obtained, a change file is obtained, and then the change category of the change file is marked according to the specific type of the difference part corresponding to the change file.
Correspondingly, in step S104, it includes:
acquiring a mark of a change type of the change file;
And judging the change type of the change file according to the mark of the change type of the change file.
After marking the change category of the change document, the mark of the change category of the change document is acquired, and the change category of the change document is known from the mark, and therefore, the change category of the change document is judged from the mark of the change category of the change document.
In some embodiments, in step S104, comprising:
comparing the changed file with the file corresponding to the version to be compared;
and judging the change type of the change file according to the comparison.
After the change file is obtained, the change file is compared with the file corresponding to the version to be compared again, a difference part can be obtained according to the comparison, the specific types of the difference part comprise addition, modification and deletion, and the change type of the change file is judged according to the specific type of the difference part.
In the present embodiment, in step S104, it includes:
if the change file is a newly added file, judging that the change type of the change file is the newly added type;
if the change file is a modified file, judging that the change type of the change file is a modified type;
and if the change file is a deleted file, judging that the change type of the change file is a deleted type.
And judging the change type of the change file according to judging that the change file is a new added, modified or deleted file, specifically judging that the change type of the change file is a new added type if the change file is a new added file, judging that the change type of the change file is a modified type if the change file is a modified file, and judging that the change type of the change file is a deleted type if the change file is a deleted file.
Step 105, matching the corresponding strategies in the strategy library according to the variation category of the variation file to obtain the target strategy.
After the change type of the change file is judged, the corresponding strategy is matched in the strategy library according to the change type of the change file, and the target strategy is obtained.
In the present embodiment, in step S105, it includes:
if the change category of the change file is a new addition category, matching the new addition category in the policy library to a new addition category policy to obtain a target policy;
if the change category of the change file is a modification category, matching the modification category in the policy base to a modification category policy to obtain a target policy;
and if the change category of the change file is a deletion category, matching the deletion category in the policy library to a deletion category policy to obtain a target policy.
The policy library comprises a new class policy, a modified class policy and a deleted class policy, the change class of the change file is judged, if the change class of the change file is the new class, the new class is matched in the policy library, and the new class is matched to the new class policy, so that the target policy is obtained. If the change type of the change file is the modification type, matching the modification type in a strategy library, and matching the modification type to the modification type strategy to obtain the target strategy. If the change type of the change file is the deletion type, matching the deletion type in a policy base, and matching the deletion type to the deletion type policy to obtain the target policy.
And S106, analyzing the character string rule in the change file according to the analysis before the test of the change file by the target strategy to obtain a target character string rule.
Step S107, matching the target character string rule with a preset character string rule in the target strategy and an output information relation table, and marking the matched output information in a corresponding character string to form a report file, wherein the output information comprises analysis information and risk focus information.
After the target policy is obtained, the change file is analyzed before testing according to the target policy. And matching different action libraries in the action libraries by different target strategies, and analyzing the change file before testing the action corresponding to the target strategy in the action libraries. Analyzing the character string rule in the change file to obtain a target character string rule, storing the corresponding relation between the character string rule and output information in a relation table of preset character string rule and output information in a target strategy, marking the output information matched according to the target character string rule in the corresponding character string, forming a report document, sending the report document to a tester through mail, and recording analysis information and risk focus information in the report document, so that the code is changed transparently and is easy to view, and the method has the functions of leading and inspiring the tester.
In this embodiment, the step of analyzing the change file before the test according to the target policy includes:
when the target policy is a deletion category policy, matching the target policy in an action library to the action library of the deletion category;
Acquiring the suffix name of the change file;
Matching the suffix name of the change file in the action library of the deletion category to corresponding actions;
And executing analysis before testing on the change file according to the action matched with the corresponding action.
When the target policy is a deletion type policy, the target policy is matched in an action library, namely, the deletion type policy is matched in the action library, the deletion type policy corresponds to the action library of the deletion type, the action library of the deletion type is matched, the suffix name of the change file can be obtained according to the suffix name of the file after the action library of the deletion type is matched, the suffix name of the change file is matched in the action library of the deletion type, the corresponding action is matched, and therefore the action corresponding to the suffix name of the file is obtained, and analysis before testing the change file is executed according to the action matched to the corresponding action after the corresponding action is matched.
In some embodiments, the step of analyzing the change file before testing according to the target policy includes:
when the target strategy is a newly added type strategy, matching the target strategy in an action library to the action library of the newly added type;
Acquiring the suffix name of the change file;
Matching the suffix name of the change file in the action library of the newly added category to corresponding actions;
And executing analysis before testing on the change file according to the action matched with the corresponding action.
When the target policy is a new type policy, matching the target policy in an action library, that is, matching the new type policy in the action library, wherein the new type policy corresponds to the action library of the new type, for this purpose, matching the new type policy to the action library of the new type, after matching the action library of the new type, obtaining the suffix name of the change file, according to the suffix name of the file, matching the suffix name of the change file in the action library of the new type, matching the suffix name of the change file to the corresponding action, thereby obtaining an action corresponding to the suffix name of the file, and after matching the corresponding action, executing analysis before testing the change file according to the action matched to the corresponding action.
In some embodiments, the step of analyzing the change file before testing according to the target policy includes:
when the target policy is a modified class policy, matching the target policy in an action library to a modified class action library;
comparing the change file with the file corresponding to the version to be compared to obtain a difference part;
extracting a code format from the difference portion;
Matching the extracted code format in the action library of the modification category to corresponding actions;
and executing analysis before testing of the difference part according to the action matched with the corresponding action.
When the target policy is a modification type policy, the target policy is matched in an action library, namely, the modification type policy is matched in the action library, the modification type policy is corresponding to the action library of the modification type, for this purpose, the modification type policy is matched to the action library of the modification type, after the modification type policy is matched to the action library of the modification type, a change file is compared with a file corresponding to a version to be compared, according to the comparison, the difference between the change file and the file corresponding to the version to be compared is obtained, a difference part is obtained, after the difference part is obtained, a code format is extracted from the difference part, after the code format is extracted, the extracted code format is matched in the action library of the modification type to the corresponding action, so that the action corresponding to the code format is obtained, and after the corresponding action is matched, the analysis before the test of the difference part is executed according to the action matched to the corresponding action.
In summary, it is detected that the SVN resource library has a version submitted, a submitted target version is obtained, the target version is compared with the version to be compared, a change file is obtained according to the comparison result, a corresponding policy is matched in the policy library according to the change category of the change file, a target policy is obtained, analysis is performed on the change file according to the target policy before testing, and character string rules in the change file are analyzed, so as to obtain a target character string rule; the method comprises the steps of matching target character string rules, marking matched output information in corresponding character strings to form a report file, and further testing the whole version in a targeted mode without testing the whole version.
As shown in fig. 2, an embodiment of the present application provides an analysis device 1 before testing an SVN resource library, where the device 1 includes a detection module 11, an acquisition module 12, a comparison module 13, a judgment module 14, a matching module 15, an analysis module 16, and an output module 17.
And the detection module 11 is used for detecting whether the version submission exists in the SVN resource library.
Configuring an account number and a password connected with an SVN resource library in a configuration file, establishing communication connection with the SVN resource library according to the account number and the password in the configuration file, and detecting whether version submission exists in the SVN resource library after establishing connection with the SVN resource library.
And the obtaining module 12 is configured to obtain the submitted target version if the SVN resource inventory is detected to be submitted in the version.
If the SVN repository is detected to be submitted by the version, the version is marked, and after the version is submitted, the version is acquired, so that the submitted target version is acquired.
And the comparison module 13 is used for comparing the target version with the version to be compared to obtain a change file.
After the target version is obtained, comparing the target version with the version to be compared, and obtaining the change file according to the comparison result.
In this embodiment, the version to be compared is the last version of the target version, for example, the version number of the target version is 18192, the version numbers of the existing versions are 18191 and 18190, the version number of the last version of the target version is 18191 according to the naming rule of the version numbers, for this reason, the version number of the version to be compared is 18191, or taking the uploading time as an example, the uploading time of the target version is the current uploading time of the existing version is the last wednesday and the last monday, and the version number of the last version of the target version is the version of the last monday according to the rule of the uploading time, so that the version numbers of the versions to be compared are the versions of the last monday.
In some embodiments, the version to be compared is a specified version of the user input.
In this embodiment, the apparatus 1 includes:
the first detection module is used for detecting whether a user inputs a designated version as a version to be compared or not;
The first acquisition module is used for acquiring the appointed version input by the user if the appointed version input by the user is detected to be used as the version to be compared, and acquiring the version to be compared;
And the second acquisition module is used for acquiring the last version of the target version to obtain the version to be compared if the fact that the user does not input the appointed version as the version to be compared is detected.
After the target version is acquired, the version to be compared is required to be acquired, whether a user inputs the designated version as the version to be compared is detected, if the designated version input by the user is detected as the version to be compared, the designated version input by the user is acquired, and after the designated version input by the user is acquired, the designated version input by the user is taken as the version to be compared, so that the version to be compared is acquired. If the fact that the user does not input the appointed version as the version to be compared is detected, the last version of the target version is obtained, and the version to be compared is obtained.
In the present embodiment, the comparison module 13 includes:
The first sub-judging module is used for comparing the target version with the version to be compared and judging whether a new added, modified or deleted file exists in the target version;
And the first sub-acquisition module is used for acquiring the corresponding file and acquiring the changed file if the newly added, modified or deleted file exists.
After the target version is obtained, comparing the target version with the version to be compared, and obtaining a difference part of the target version and the version to be compared according to the comparison, wherein the specific type of the difference part comprises new addition, modification and deletion, judging whether the new addition, modification or deletion files exist in the target version according to the specific type of the difference part, and obtaining the corresponding files if the new addition, modification or deletion files exist, so as to obtain the change files.
The judging module 14 is configured to judge a variation category of the variation file.
After the change file is acquired, the change type of the change file is judged, and the change type of the change file is judged to be a new type, a deleted type or a modified type.
In this embodiment, the apparatus 1 includes:
and the first marking module is used for marking the change category of the change file.
When comparing the target version with the version to be compared, a difference part between the target version and the version to be compared can be obtained, the specific type of the difference part comprises new addition, modification and deletion, whether the new addition, modification or deletion files exist in the target version is judged according to the specific type of the difference part, if the new addition, modification or deletion files exist, the corresponding files are obtained, a change file is obtained, and then the change category of the change file is marked according to the specific type of the difference part corresponding to the change file.
Correspondingly, the judging module 14 includes:
The second sub-acquisition module is used for acquiring marks of the change category of the change file;
And the second sub-judging module is used for judging the change type of the change file according to the mark of the change type of the change file.
After marking the change category of the change document, the mark of the change category of the change document is acquired, and the change category of the change document is known from the mark, and therefore, the change category of the change document is judged from the mark of the change category of the change document.
In some embodiments, the determination module 14 includes:
the second sub-comparison module is used for comparing the change file with the file corresponding to the version to be compared;
And the third sub-judging module is used for judging the change type of the change file according to the comparison.
After the change file is obtained, the change file is compared with the file corresponding to the version to be compared again, a difference part can be obtained according to the comparison, the specific types of the difference part comprise addition, modification and deletion, and the change type of the change file is judged according to the specific type of the difference part.
In the present embodiment, the judging module 14 includes:
The first sub-judging module is used for judging that the change type of the change file is a new type if the change file is a new type;
The second sub-judging module is used for judging that the change type of the change file is a modification type if the change file is a modified file;
and a third sub-determination module, configured to determine that the change type of the change file is a deletion type if the change file is a deleted file.
And judging the change type of the change file according to judging that the change file is a new added, modified or deleted file, specifically judging that the change type of the change file is a new added type if the change file is a new added file, judging that the change type of the change file is a modified type if the change file is a modified file, and judging that the change type of the change file is a deleted type if the change file is a deleted file.
And the matching module 15 is used for matching the corresponding strategies in the strategy library according to the variation category of the variation file to obtain the target strategy.
After the change type of the change file is judged, the corresponding strategy is matched in the strategy library according to the change type of the change file, and the target strategy is obtained.
In the present embodiment, the matching module 15 includes:
The first sub-matching module is used for matching the new category in the policy base if the change category of the change file is the new category, and matching the new category to the new category policy to obtain a target policy;
The second sub-matching module is used for matching the modification category in the policy base if the modification category of the modification file is a modification category, and matching the modification category to a modification category policy to obtain a target policy;
and the third sub-matching module is used for matching the deletion category in the policy library if the change category of the change file is the deletion category, matching the deletion category to a deletion category policy, and obtaining a target policy.
The policy library comprises a new class policy, a modified class policy and a deleted class policy, the change class of the change file is judged, if the change class of the change file is the new class, the new class is matched in the policy library, and the new class is matched to the new class policy, so that the target policy is obtained. If the change type of the change file is the modification type, matching the modification type in a strategy library, and matching the modification type to the modification type strategy to obtain the target strategy. If the change type of the change file is the deletion type, matching the deletion type in a policy base, and matching the deletion type to the deletion type policy to obtain the target policy.
And the analysis module 16 is configured to analyze the string rule in the change file according to the analysis before testing the change file according to the target policy, so as to obtain a target string rule.
And the output module 17 is configured to match the target string rule with a preset string rule in the target policy and an output information relationship table, and mark the matched output information in a corresponding string to form a report file, where the output information includes analysis information and risk focus information.
After the target policy is obtained, the change file is analyzed before testing according to the target policy. And matching different action libraries in the action libraries by different target strategies, and analyzing the change file before testing the action corresponding to the target strategy in the action libraries. Analyzing the character string rule in the change file to obtain a target character string rule, storing the corresponding relation between the character string rule and output information in a relation table of preset character string rule and output information in a target strategy, marking the output information matched according to the target character string rule in the corresponding character string, forming a report document, sending the report document to a tester through mail, and recording analysis information and risk focus information in the report document, so that the code is changed transparently and is easy to view, and the method has the functions of leading and inspiring the tester.
In the present embodiment, the analysis module 16 includes:
A fourth sub-matching module, configured to match the target policy in an action library when the target policy is a deletion category policy, to the action library of the deletion category;
a third sub-acquisition module, configured to acquire a suffix name of the change file;
a fifth sub-matching module, configured to match the suffix name of the change file to a corresponding action in the action library of the deletion class;
And the first sub-analysis module is used for executing analysis before testing the change file according to the action matched with the corresponding action.
When the target policy is a deletion type policy, the target policy is matched in an action library, namely, the deletion type policy is matched in the action library, the deletion type policy corresponds to the action library of the deletion type, the action library of the deletion type is matched, the suffix name of the change file can be obtained according to the suffix name of the file after the action library of the deletion type is matched, the suffix name of the change file is matched in the action library of the deletion type, the corresponding action is matched, and therefore the action corresponding to the suffix name of the file is obtained, and analysis before testing the change file is executed according to the action matched to the corresponding action after the corresponding action is matched.
In some embodiments, the analysis module 16 includes:
a sixth sub-matching module, configured to match the target policy in an action library when the target policy is a newly added category policy, to the action library of the newly added category;
a fourth sub-acquisition module, configured to acquire a suffix name of the change file;
a seventh sub-matching module, configured to match the suffix name of the change file to a corresponding action in the action library of the new added category;
and the second sub-analysis module is used for executing analysis before testing the change file according to the action matched with the corresponding action.
When the target policy is a new type policy, matching the target policy in an action library, that is, matching the new type policy in the action library, wherein the new type policy corresponds to the action library of the new type, for this purpose, matching the new type policy to the action library of the new type, after matching the action library of the new type, obtaining the suffix name of the change file, according to the suffix name of the file, matching the suffix name of the change file in the action library of the new type, matching the suffix name of the change file to the corresponding action, thereby obtaining an action corresponding to the suffix name of the file, and after matching the corresponding action, executing analysis before testing the change file according to the action matched to the corresponding action.
In some embodiments, the analysis module 16 includes:
An eighth sub-matching module, configured to match the target policy in an action library to a modified class action library when the target policy is a modified class policy;
a fifth sub-acquisition module, configured to compare the change file with a file corresponding to the version to be compared, and acquire a difference portion;
a first sub-extraction module for extracting a code format from the difference portion;
a ninth sub-matching module, configured to match the extracted code format to a corresponding action in the action library of the modification class;
and the third sub-analysis module is used for executing analysis before the test on the difference part according to the action matched with the corresponding action.
When the target policy is a modification type policy, the target policy is matched in an action library, namely, the modification type policy is matched in the action library, the modification type policy is corresponding to the action library of the modification type, for this purpose, the modification type policy is matched to the action library of the modification type, after the modification type policy is matched to the action library of the modification type, a change file is compared with a file corresponding to a version to be compared, according to the comparison, the difference between the change file and the file corresponding to the version to be compared is obtained, a difference part is obtained, after the difference part is obtained, a code format is extracted from the difference part, after the code format is extracted, the extracted code format is matched in the action library of the modification type to the corresponding action, so that the action corresponding to the code format is obtained, and after the corresponding action is matched, the analysis before the test of the difference part is executed according to the action matched to the corresponding action.
In summary, it is detected that the SVN resource library has a version submitted, a submitted target version is obtained, the target version is compared with the version to be compared, a change file is obtained according to the comparison result, a corresponding policy is matched in the policy library according to the change category of the change file, a target policy is obtained, analysis is performed on the change file according to the target policy before testing, and character string rules in the change file are analyzed, so as to obtain a target character string rule; the method comprises the steps of matching target character string rules, marking matched output information in corresponding character strings to form a report file, and further testing the whole version in a targeted mode without testing the whole version.
As shown in fig. 3, in an embodiment of the present application, a computer device is further provided, where the computer device may be a server, and the internal structure of the computer device may be as shown in fig. 3. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the computer is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database of the computer equipment is used for storing data such as models of analysis methods before SVN resource library testing. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program, when executed by the processor, implements a method of analysis prior to testing of the SVN resource library.
The processor executes the steps of the analysis method before the SVN resource library test: detecting whether a version submission exists in the SVN resource library; if the SVN resource inventory is detected to be submitted in the version, acquiring a submitted target version; comparing the target version with the version to be compared to obtain a change file; judging the change type of the change file; matching corresponding strategies in a strategy library according to the variation category of the variation file to obtain a target strategy; analyzing character string rules in the change file according to the analysis before the test of the change file by the target strategy to obtain target character string rules; matching the target character string rule with a preset character string rule in the target strategy and an output information relation table, and marking the matched output information in the corresponding character string to form a report file, wherein the output information comprises analysis information and risk focus information.
In one embodiment, the step of comparing the target version with the version to be compared to obtain the change file includes:
Comparing the target version with the version to be compared, and judging whether a new added, modified or deleted file exists in the target version;
If the new file is added, modified or deleted, the corresponding file is acquired, and the changed file is acquired.
In one embodiment, the step of determining the change type of the change file includes:
if the change file is a newly added file, judging that the change type of the change file is the newly added type;
if the change file is a modified file, judging that the change type of the change file is a modified type;
and if the change file is a deleted file, judging that the change type of the change file is a deleted type.
In one embodiment, the step of matching the corresponding policy in the policy repository according to the change category of the change file to obtain the target policy includes:
if the change category of the change file is a new addition category, matching the new addition category in the policy library to a new addition category policy to obtain a target policy;
if the change category of the change file is a modification category, matching the modification category in the policy base to a modification category policy to obtain a target policy;
and if the change category of the change file is a deletion category, matching the deletion category in the policy library to a deletion category policy to obtain a target policy.
In one embodiment, the step of analyzing the change file before testing according to the target policy includes:
when the target policy is a deletion category policy, matching the target policy in an action library to the action library of the deletion category;
Acquiring the suffix name of the change file;
Matching the suffix name of the change file in the action library of the deletion category to corresponding actions;
And executing analysis before testing on the change file according to the action matched with the corresponding action.
In one embodiment, the step of analyzing the change file before testing according to the target policy includes:
when the target strategy is a newly added type strategy, matching the target strategy in an action library to the action library of the newly added type;
Acquiring the suffix name of the change file;
Matching the suffix name of the change file in the action library of the newly added category to corresponding actions;
And executing analysis before testing on the change file according to the action matched with the corresponding action.
In one embodiment, the step of analyzing the change file before testing according to the target policy includes:
when the target policy is a modified class policy, matching the target policy in an action library to a modified class action library;
comparing the change file with the file corresponding to the version to be compared to obtain a difference part;
extracting a code format from the difference portion;
Matching the extracted code format in the action library of the modification category to corresponding actions;
and executing analysis before testing of the difference part according to the action matched with the corresponding action.
It will be appreciated by those skilled in the art that the architecture shown in fig. 3 is merely a block diagram of a portion of the architecture in connection with the present inventive arrangements and is not intended to limit the computer devices to which the present inventive arrangements are applicable.
The computer equipment of the embodiment of the application detects that a version of an SVN resource library is submitted, acquires a submitted target version, compares the target version with a version to be compared, acquires a change file according to a comparison result, matches a corresponding strategy in a strategy library according to the change category of the change file, acquires a target strategy, analyzes the change file according to the target strategy before testing, analyzes character string rules in the change file, and acquires target character string rules; the method comprises the steps of matching target character string rules, marking matched output information in corresponding character strings to form a report file, and further testing the whole version in a targeted mode without testing the whole version.
An embodiment of the present application further provides a computer readable storage medium, on which a computer program is stored, where the computer program when executed by a processor implements a method for analyzing before testing an SVN resource library, specifically: detecting whether a version submission exists in the SVN resource library; if the SVN resource inventory is detected to be submitted in the version, acquiring a submitted target version; comparing the target version with the version to be compared to obtain a change file; judging the change type of the change file; matching corresponding strategies in a strategy library according to the variation category of the variation file to obtain a target strategy; analyzing character string rules in the change file according to the analysis before the test of the change file by the target strategy to obtain target character string rules; matching the target character string rule with a preset character string rule in the target strategy and an output information relation table, and marking the matched output information in the corresponding character string to form a report file, wherein the output information comprises analysis information and risk focus information.
In one embodiment, the step of comparing the target version with the version to be compared to obtain the change file includes:
Comparing the target version with the version to be compared, and judging whether a new added, modified or deleted file exists in the target version;
If the new file is added, modified or deleted, the corresponding file is acquired, and the changed file is acquired.
In one embodiment, the step of determining the change type of the change file includes:
if the change file is a newly added file, judging that the change type of the change file is the newly added type;
if the change file is a modified file, judging that the change type of the change file is a modified type;
and if the change file is a deleted file, judging that the change type of the change file is a deleted type.
In one embodiment, the step of matching the corresponding policy in the policy repository according to the change category of the change file to obtain the target policy includes:
if the change category of the change file is a new addition category, matching the new addition category in the policy library to a new addition category policy to obtain a target policy;
if the change category of the change file is a modification category, matching the modification category in the policy base to a modification category policy to obtain a target policy;
and if the change category of the change file is a deletion category, matching the deletion category in the policy library to a deletion category policy to obtain a target policy.
In one embodiment, the step of analyzing the change file before testing according to the target policy includes:
when the target policy is a deletion category policy, matching the target policy in an action library to the action library of the deletion category;
Acquiring the suffix name of the change file;
Matching the suffix name of the change file in the action library of the deletion category to corresponding actions;
And executing analysis before testing on the change file according to the action matched with the corresponding action.
In one embodiment, the step of analyzing the change file before testing according to the target policy includes:
when the target strategy is a newly added type strategy, matching the target strategy in an action library to the action library of the newly added type;
Acquiring the suffix name of the change file;
Matching the suffix name of the change file in the action library of the newly added category to corresponding actions;
And executing analysis before testing on the change file according to the action matched with the corresponding action.
In one embodiment, the step of analyzing the change file before testing according to the target policy includes:
when the target policy is a modified class policy, matching the target policy in an action library to a modified class action library;
comparing the change file with the file corresponding to the version to be compared to obtain a difference part;
extracting a code format from the difference portion;
Matching the extracted code format in the action library of the modification category to corresponding actions;
and executing analysis before testing of the difference part according to the action matched with the corresponding action.
The storage medium of the embodiment of the application detects that a version of an SVN resource library is submitted, acquires a submitted target version, compares the target version with a version to be compared, acquires a change file according to a comparison result, matches a corresponding strategy in a strategy library according to a change category of the change file, acquires a target strategy, analyzes the change file according to the target strategy before testing, analyzes character string rules in the change file, and acquires target character string rules; the method comprises the steps of matching target character string rules, marking matched output information in corresponding character strings to form a report file, and further testing the whole version in a targeted mode without testing the whole version.
Those skilled in the art will appreciate that implementing all or part of the above described methods may be accomplished by way of a computer program stored on a non-transitory computer readable storage medium, which when executed, may comprise the steps of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium provided by the present application and used in embodiments may include non-volatile and/or volatile memory. The nonvolatile memory can include Read Only Memory (ROM), programmable ROM (PROM), electrically Programmable ROM (EPROM), electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual speed data rate SDRAM (SSRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (SYNCHL INK) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), among others.
The foregoing description of the preferred embodiment of the application is not intended to be limiting, but rather is intended to cover all modifications, equivalents, and alternatives falling within the spirit and principles of the application.
Claims (7)
1. An analysis method before testing an SVN resource library, the method comprising:
Detecting whether a version submission exists in the SVN resource library;
If the SVN resource inventory is detected to be submitted in the version, acquiring a submitted target version;
Comparing the target version with the version to be compared to obtain a change file;
judging the change type of the change file;
matching corresponding strategies in a strategy library according to the variation category of the variation file to obtain a target strategy;
analyzing character string rules in the change file according to the analysis before the test of the change file by the target strategy to obtain target character string rules;
Matching the target character string rule with a preset character string rule in the target strategy and an output information relation table, and marking the matched output information in a corresponding character string to form a report file, wherein the output information comprises analysis information and risk focus information;
the version to be compared is a designated version input by a user; the step of comparing the target version with the version to be compared to obtain the change file comprises the following steps:
Detecting whether a user inputs a designated version as a version to be compared;
if the appointed version input by the user is detected to be used as the version to be compared, acquiring the appointed version input by the user, and acquiring the version to be compared;
if the fact that the user does not input the appointed version as the version to be compared is detected, the last version of the target version is obtained, and the version to be compared is obtained;
the step of analyzing the change file before testing according to the target strategy comprises the following steps:
when the target policy is a deletion category policy, matching the target policy in an action library to the action library of the deletion category;
Acquiring the suffix name of the change file;
Matching the suffix name of the change file in the action library of the deletion category to corresponding actions;
Performing pre-test analysis on the change file according to the matched corresponding action;
the step of analyzing the change file before testing according to the target strategy comprises the following steps:
when the target strategy is a newly added type strategy, matching the target strategy in an action library to the action library of the newly added type;
Acquiring the suffix name of the change file;
Matching the suffix name of the change file in the action library of the newly added category to corresponding actions;
Performing pre-test analysis on the change file according to the matched corresponding action;
the step of analyzing the change file before testing according to the target strategy comprises the following steps:
when the target policy is a modified class policy, matching the target policy in an action library to a modified class action library;
comparing the change file with the file corresponding to the version to be compared to obtain a difference part;
extracting a code format from the difference portion;
Matching the extracted code format in the action library of the modification category to corresponding actions;
and executing analysis before testing of the difference part according to the action matched with the corresponding action.
2. The method for analyzing a SVN repository before testing according to claim 1, wherein the step of comparing the target version with the version to be compared to obtain the change file includes:
Comparing the target version with the version to be compared, and judging whether a new added, modified or deleted file exists in the target version;
If the new file is added, modified or deleted, the corresponding file is acquired, and the changed file is acquired.
3. The method of claim 1, wherein the step of determining the change type of the change file comprises:
if the change file is a newly added file, judging that the change type of the change file is the newly added type;
if the change file is a modified file, judging that the change type of the change file is a modified type;
and if the change file is a deleted file, judging that the change type of the change file is a deleted type.
4. The method for analyzing SVN resource library before testing according to claim 3, wherein said step of matching corresponding policies in a policy library according to a change category of said change file to obtain a target policy comprises:
if the change category of the change file is a new addition category, matching the new addition category in the policy library to a new addition category policy to obtain a target policy;
if the change category of the change file is a modification category, matching the modification category in the policy base to a modification category policy to obtain a target policy;
and if the change category of the change file is a deletion category, matching the deletion category in the policy library to a deletion category policy to obtain a target policy.
5. An apparatus for analyzing a SVN resource library prior to testing, the apparatus comprising:
the detection module is used for detecting whether the version submission exists in the SVN resource library;
The acquisition module is used for acquiring a submitted target version if the SVN resource inventory is detected to be submitted in the version;
the comparison module is used for comparing the target version with the version to be compared to obtain a change file;
The judging module is used for judging the change type of the change file;
the matching module is used for matching corresponding strategies in the strategy library according to the variation category of the variation file to obtain a target strategy;
The analysis module is used for analyzing the character string rule in the change file according to the analysis before the test of the change file by the target strategy to obtain a target character string rule;
The output module is used for matching the target character string rule with a preset character string rule in the target strategy and an output information relation table, marking the matched output information in a corresponding character string to form a report file, wherein the output information comprises analysis information and risk focus information;
the version to be compared is a designated version input by a user; the device comprises:
the first detection module is used for detecting whether a user inputs a designated version as a version to be compared or not;
The first acquisition module is used for acquiring the appointed version input by the user if the appointed version input by the user is detected to be used as the version to be compared, and acquiring the version to be compared;
the second acquisition module is used for acquiring a previous version of the target version to obtain a version to be compared if the fact that the user does not input the designated version as the version to be compared is detected;
the analysis module comprises:
A fourth sub-matching module, configured to match the target policy in an action library when the target policy is a deletion category policy, to the action library of the deletion category;
a third sub-acquisition module, configured to acquire a suffix name of the change file;
a fifth sub-matching module, configured to match the suffix name of the change file to a corresponding action in the action library of the deletion class;
The first sub-analysis module is used for executing analysis before testing the change file according to the action matched with the corresponding action;
The analysis module further includes:
a sixth sub-matching module, configured to match the target policy in an action library when the target policy is a newly added category policy, to the action library of the newly added category;
a fourth sub-acquisition module, configured to acquire a suffix name of the change file;
a seventh sub-matching module, configured to match the suffix name of the change file to a corresponding action in the action library of the new added category;
The second sub-analysis module is used for executing analysis before testing the change file according to the action matched with the corresponding action;
The analysis module further includes:
An eighth sub-matching module, configured to match the target policy in an action library to a modified class action library when the target policy is a modified class policy;
a fifth sub-acquisition module, configured to compare the change file with a file corresponding to the version to be compared, and acquire a difference portion;
a first sub-extraction module for extracting a code format from the difference portion;
a ninth sub-matching module, configured to match the extracted code format to a corresponding action in the action library of the modification class;
and the third sub-analysis module is used for executing analysis before the test on the difference part according to the action matched with the corresponding action.
6. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor implements the steps of the method of any of claims 1 to 4 when the computer program is executed.
7. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the steps of the method of any of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910319560.6A CN110134595B (en) | 2019-04-19 | 2019-04-19 | Analysis method, analysis device and computer equipment before SVN (scalable vector network) resource library test |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910319560.6A CN110134595B (en) | 2019-04-19 | 2019-04-19 | Analysis method, analysis device and computer equipment before SVN (scalable vector network) resource library test |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110134595A CN110134595A (en) | 2019-08-16 |
| CN110134595B true CN110134595B (en) | 2024-05-28 |
Family
ID=67570672
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910319560.6A Active CN110134595B (en) | 2019-04-19 | 2019-04-19 | Analysis method, analysis device and computer equipment before SVN (scalable vector network) resource library test |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110134595B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110708210B (en) * | 2019-08-30 | 2022-05-03 | 深圳壹账通智能科技有限公司 | Cloud test configuration method and device, computer equipment and storage medium |
| CN110750447B (en) * | 2019-09-18 | 2023-07-25 | 平安科技（深圳）有限公司 | Software testing method and related equipment |
| CN115099795B (en) * | 2022-08-29 | 2022-11-11 | 江苏青山软件有限公司 | Enterprise internal digital resource management method and system |
Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103514166A (en) * | 2012-06-15 | 2014-01-15 | 阿里巴巴集团控股有限公司 | Method and device for SQL inspection |
| CN103577311A (en) * | 2012-07-26 | 2014-02-12 | 深圳市世纪光速信息技术有限公司 | Method and device for screening test cases |
| CN103699488A (en) * | 2013-12-30 | 2014-04-02 | 优视科技有限公司 | Call relation dependence graph based regression testing method and system |
| CN104424088A (en) * | 2013-08-21 | 2015-03-18 | 腾讯科技（深圳）有限公司 | Software testing method and device |
| CN106445476A (en) * | 2015-08-11 | 2017-02-22 | 腾讯科技（深圳）有限公司 | Code change information determination method and device and electronic equipment |
| CN106909510A (en) * | 2017-03-02 | 2017-06-30 | 腾讯科技（深圳）有限公司 | A kind of method and server for obtaining test case |
| CN107480050A (en) * | 2017-07-17 | 2017-12-15 | 上海爱数信息技术股份有限公司 | A kind of method of testing of automatic test renewal bag |
| CN107688541A (en) * | 2017-09-15 | 2018-02-13 | 广州酷狗计算机科技有限公司 | File reviewing method, device, server and computer-readable recording medium |
| CN108491331A (en) * | 2018-04-13 | 2018-09-04 | 平安普惠企业管理有限公司 | Method for testing software, device, equipment and computer storage media |
| CN108845843A (en) * | 2018-05-25 | 2018-11-20 | 腾讯科技（深圳）有限公司 | A kind of function processing method, device and relevant device |
| CN109542779A (en) * | 2018-11-12 | 2019-03-29 | 泰康保险集团股份有限公司 | Test method, device and storage medium |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US10191737B2 (en) * | 2016-06-29 | 2019-01-29 | Accenture Global Solutions Limited | Program code comparison and reporting |
-
2019
- 2019-04-19 CN CN201910319560.6A patent/CN110134595B/en active Active
Patent Citations (11)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103514166A (en) * | 2012-06-15 | 2014-01-15 | 阿里巴巴集团控股有限公司 | Method and device for SQL inspection |
| CN103577311A (en) * | 2012-07-26 | 2014-02-12 | 深圳市世纪光速信息技术有限公司 | Method and device for screening test cases |
| CN104424088A (en) * | 2013-08-21 | 2015-03-18 | 腾讯科技（深圳）有限公司 | Software testing method and device |
| CN103699488A (en) * | 2013-12-30 | 2014-04-02 | 优视科技有限公司 | Call relation dependence graph based regression testing method and system |
| CN106445476A (en) * | 2015-08-11 | 2017-02-22 | 腾讯科技（深圳）有限公司 | Code change information determination method and device and electronic equipment |
| CN106909510A (en) * | 2017-03-02 | 2017-06-30 | 腾讯科技（深圳）有限公司 | A kind of method and server for obtaining test case |
| CN107480050A (en) * | 2017-07-17 | 2017-12-15 | 上海爱数信息技术股份有限公司 | A kind of method of testing of automatic test renewal bag |
| CN107688541A (en) * | 2017-09-15 | 2018-02-13 | 广州酷狗计算机科技有限公司 | File reviewing method, device, server and computer-readable recording medium |
| CN108491331A (en) * | 2018-04-13 | 2018-09-04 | 平安普惠企业管理有限公司 | Method for testing software, device, equipment and computer storage media |
| CN108845843A (en) * | 2018-05-25 | 2018-11-20 | 腾讯科技（深圳）有限公司 | A kind of function processing method, device and relevant device |
| CN109542779A (en) * | 2018-11-12 | 2019-03-29 | 泰康保险集团股份有限公司 | Test method, device and storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 利用SVN对软件项目进行版本控制管理;闫晗;科技风(05);全文 * |
| 闫晗.利用SVN对软件项目进行版本控制管理.科技风.2009,(05),全文. * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110134595A (en) | 2019-08-16 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110134595B (en) | Analysis method, analysis device and computer equipment before SVN (scalable vector network) resource library test | |
| CN109710508B (en) | Test method, test device, test apparatus, and computer-readable storage medium | |
| CN110221982B (en) | Performance test method, device and equipment of business system and readable storage medium | |
| CN109446068B (en) | Interface test method, device, computer equipment and storage medium | |
| CN109800258B (en) | Data file deployment method, device, computer equipment and storage medium | |
| CN110730107B (en) | Test data generation method and device, computer equipment and storage medium | |
| CN108427613B (en) | Abnormal interface positioning method and device, computer equipment and storage medium | |
| CN108985057B (en) | Webshell detection method and related equipment | |
| CN108459954B (en) | Application program vulnerability detection method and device | |
| CN107622008B (en) | Traversal method and device for application page | |
| CN108491321B (en) | Method and device for determining test case range and storage medium | |
| WO2019019647A1 (en) | Method and system for determining application program testing range, server and storage medium | |
| CN112363937B (en) | Differential coverage rate testing method, differential coverage rate testing device, computer equipment and storage medium | |
| CN110955608B (en) | Test data processing method, device, computer equipment and storage medium | |
| CN108399125B (en) | Automatic testing method and device, computer equipment and storage medium | |
| CN109324961B (en) | System automatic test method, device, computer equipment and storage medium | |
| CN112363936A (en) | Method and device for testing differential coverage rate, computer equipment and storage medium | |
| CN106557419B (en) | Program testing method and device | |
| CN111290950A (en) | Test point obtaining method and device in program test, storage medium and equipment | |
| CN115098151A (en) | Fine-grained intranet equipment firmware version detection method | |
| CN112612706A (en) | Automated testing method, computer device and storage medium | |
| CN116225622A (en) | Docker-based PaaS application parameter template testing method | |
| CN115168217A (en) | Defect discovery method and device for source code file | |
| CN112363929B (en) | System online method and device, computer equipment and storage medium | |
| US11977477B2 (en) | System and method for identification of web elements used in automation test case |
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 |