CN103077111A - Method and system for locating continuous integration failed case - Google Patents
Method and system for locating continuous integration failed case Download PDFInfo
- Publication number
- CN103077111A CN103077111A CN2011103295218A CN201110329521A CN103077111A CN 103077111 A CN103077111 A CN 103077111A CN 2011103295218 A CN2011103295218 A CN 2011103295218A CN 201110329521 A CN201110329521 A CN 201110329521A CN 103077111 A CN103077111 A CN 103077111A
- Authority
- CN
- China
- Prior art keywords
- failed
- test script
- code
- reason
- method call
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention provides a method and system for locating a continuous integration failed case and solves the problem of low manual location efficiency at present. The method comprises the following steps: filling a journal output byte code in an engineering code when loading the engineering code; recording a method invoking journal through the journal output byte code before each method of starting a test script when operating the test scrip including the engineering code, and forming an journal file of a method invoking hierarchy according to the method invoking journal; and analyzing a test script which is failed to operate according to the method invoking hierarchy in the journal file, and locating the reason of failed operation. According to the method and system for locating the continuous integration failed case, disclosed by the invention, codes are not needed to be manually debugged so that the problem reason can be conveniently, quickly and automatically located, the problem is saved, the maintenance is convenient, a large amount of time and energy is saved and the working efficiency is improved.
Description
Technical field
The application relates to measuring technology, particularly relates to a kind of localization method that continues integrated failed use-case, and, a kind of positioning system that continues integrated failed use-case.
Background technology
Continuing integrated is a kind of practice mode of software development, utilize the mode of robotization that the newly-increased code with revising that the team develops personnel submit to is continued to make up (comprising compiling, issue, automatic test), at least once a day, find as soon as possible code issue, thereby guarantee product quality.
A typical lasting integrated cycle comprises following step:
1) continues integrating server and constantly check code status from version control server, see whether code has renewal;
2) if find that code has up-to-date submission, so just download up-to-date code from version control server;
3) after etc. code upgrades fully, call the robotization compilation script, carry out code compilation;
4) move all automatic tests;
5) carry out code analysis;
6) produce executable software, and offer the tester and test.
If wherein any one step failure just represents this structure failure, lasting integrating server can give corresponding feedback.
Projects is being continued when integrated, if the developer revises the partial code in the engineering or revises configuration file, all will cause the test script failure, thereby cause continuing integrated can not normally carrying out, have a strong impact on lasting integrated effect and quality to product development.At this moment, just must the quick positioning question reason, and deal with problems to make and continue integrated normal operation.
The more loaded down with trivial details poor efficiency of means of present orientation problem reason, mainly be artificially by Eclipse instrument (Eclipse is famous cross-platform free Sets IDE (IDE)) step by step debugging code analyze the program code problem, perhaps artificially by SVN (Subversion, a kind of Version, by source code is carried out Version Control, thereby reach the purpose that guarantees file synchronization) client utility Show log check that recent code upgrades, and the alteration that contrasts program code.
This present two schemes all is to come the analyzing and positioning problem by artificial craft, can relate to the problems such as technical experience, maintenance cost this moment, when technical experience is not enough, probably find less than the problem place, and when script is hundreds and thousands of, safeguard very difficult, need to consume a large amount of time and energy so artificially locate, affect work efficiency.
Summary of the invention
The application's purpose is, provides a kind of localization method and system that continues integrated failed use-case, to solve the inefficient problem of present manual positioning.
In order to address the above problem, the application discloses a kind of localization method that continues integrated failed use-case, comprising:
When loading the engineering code, in the engineering code, inject daily record output byte code;
When operation comprises the test script of described engineering code, call daily record by the recording method of described daily record output byte code before entering each method of test script, and form the journal file of method call level according to the method call daily record;
According to the failed test script of the operation of the method call step analysis in the described journal file, the reason of positioning trip failure.
Preferably, described according to the failed test script of the operation of the method call step analysis in the described journal file, the reason of positioning trip failure comprises: according to the method call level in the described journal file, and the current version of control methods and the last code that moves successful version; The change point that contrast is found carries out mark, and orientates the change point of mark as operation failed reason.
Preferably, unchanged if contrast is found, also comprise: the possible cause that the prompting operation is failed, described possible cause comprise database change and/or configuration change.
Preferably, when clicking the link of the failed test script of certain operation, according to the test script of this clicked operation failure of the method call step analysis in the described journal file, the reason of positioning trip failure.
Preferably, according to the failed test script of all operations of the method call step analysis in the described journal file, locate after the failed reason of all operations, also comprise: when clicking the link of the failed test script of certain operation, therefrom obtain the reason of corresponding operation failure.
The application also provides a kind of positioning system that continues integrated failed use-case, comprising:
Bytecode injects the unit, when being used for loading the engineering code, injects daily record output byte code in the engineering code;
Method call step analysis unit, be used for when operation comprises the test script of described engineering code, call daily record by the recording method of described daily record output byte code before entering each method of test script, and form the journal file of method call level according to the method call daily record;
The failure positioning unit is used for the failed test script of method call step analysis operation according to described journal file, the reason of positioning trip failure.
Preferably, described failed positioning unit comprises:
Contrast subunit is used for the method call level according to described journal file, the current version of control methods and the last code that moves successful version;
The mark subelement is used for contrasting the change point of finding and carries out mark, and orientates the change point of mark as operation failed reason.
Preferably, unchanged if contrast is found, described failed positioning unit also comprises:
The prompting subelement is used for the failed possible cause of prompting operation, and described possible cause comprises database change and/or configuration change.
Preferably, described system also comprises: the unit is checked in the first click, be used for when clicking the link of the failed test script of certain operation, triggering described failed positioning unit, described failed positioning unit is according to the test script of this clicked operation failure of the method call step analysis in the described journal file, the reason of positioning trip failure.
Preferably, described failed positioning unit is located the failed reason of all operations according to the failed test script of all operations of the method call step analysis in the described journal file; Described system also comprises: the unit is checked in the second click, is used for obtaining the reason of corresponding operation failure from described failed positioning unit when clicking the link of the failed test script of certain operation.
Compared with prior art, the application comprises following advantage:
At first, the application is in continuing integrating process, in the engineering code, inject daily record output byte code during by loading engineering code, utilize described daily record output byte code to analyze method call level in the test script, then according to the failed test script of method call step analysis operation, finally automatically orient the failed code point of operation.The method of this automatic location failure use-case need not the manual debugging code, therefore can automatically navigate to easily and quickly the problem reason, deals with problems, and maintains easily, and saves plenty of time and energy, has improved work efficiency.
Secondly, the application uses SVN Kit client library automatically to contrast current version and the last method of successfully calling version, find out wherein code change or configuration change, need not manually to compare change point, thus more convenient, automatically navigate to the problem reason more quickly.
Again, all right automatic monitoring script operation conditions of the application, if move unsuccessfully, then system can notify the related personnel to follow the tracks of in modes such as mail, instant messagings automatically.And the related personnel clicks failed script url, and system shows the situation of change of class methods according to the method change point of mark, helps its quick positioning question reason.
Certainly, arbitrary product of enforcement the application not necessarily needs to reach simultaneously above-described all advantages.
Description of drawings
Fig. 1 is the described a kind of localization method process flow diagram that continues integrated failed use-case of the embodiment of the present application;
Fig. 2 is the described a kind of positioning system structure figure that continues integrated failed use-case of the embodiment of the present application;
Fig. 3 is the described a kind of positioning system structure figure that continues integrated failed use-case of another embodiment of the application;
Fig. 4 is the described a kind of positioning system structure figure that continues integrated failed use-case of another embodiment of the application;
Fig. 5 is the described system construction drawing of another embodiment of the application;
Fig. 6 is the process flow diagram that middle ASM embodiment illustrated in fig. 5 injects daily record output byte code;
Fig. 7 is the process flow diagram of middle SVN Kit contrast code change embodiment illustrated in fig. 5.
Embodiment
For above-mentioned purpose, the feature and advantage that make the application can become apparent more, below in conjunction with the drawings and specific embodiments the application is described in further detail.
Projects is being continued when integrated, in order to navigate to fast the problem reason, the application at first automatic analysis goes out the hierarchical relationship of method call in the test script, then according to the failed test script of method call step analysis operation, finally automatically orients and moves failed code point.
Below by embodiment the application is elaborated.
With reference to Fig. 1, it is the described a kind of localization method process flow diagram that continues integrated failed use-case of the embodiment of the present application.
Bytecode (Byte-code) be a kind ofly comprise executive routine, by the binary file of sequence op code/data to forming.Bytecode is a kind of intermediate code, and it is more abstract than machine code.It often is counted as the binary file that comprises an executive routine, more as an object model.It is because each opcode is a byte long usually that bytecode is named like this, but the length of order code changes.Each instruction has a byte oriented operand of from 0 to 255 (or hexadecimal: 00 to FF), and for example register or memory address are followed by parameter.
During each test, when loading the required engineering code of current test, daily record output byte code is injected in the engineering code, therefore can cause modification to the source code of engineering code.The effect of described daily record output byte code is the hierarchical relationship that analyzes method call in the test script, and concrete analytical approach such as step 102 describe in detail.
Code in the test script mainly is the code of some class methods, has the level call relation of tree type between the method, and all methods can form a method call relational tree.
In the operational process of test script, each run is before will enter a method, the daily record output byte code that is injected into test script just carries out log recording with the call relation of this method and additive method, by another method call, this method can be called another method again such as this method.By such mode, just recorded the call relation between all methods in the test script in the daily record, form the method call level in the final journal file, also be the method call relational tree.The hierarchical relationship of this method call can be used to locate and causes script to move failed reason.
Concrete, step 103 can comprise following two sub-steps:
Substep a, according to the method call level in the described journal file, the current version of control methods and the last code that moves successful version;
In actual applications, owing to being the relation of calling layer by layer between the method, therefore for the failed test script of operation, need to find corresponding a plurality of files, carry out respectively comparing in twos of current version and the last successful version of operation.For example, for the failed test script of certain operation, hierarchical relationship according to method call has three files that record current version class methods codes, respectively file A1, file B1, file C1, also need to obtain these three files this moment in the successful edition code of the last time operation, such as file A2, file B2, file C2, then A1 and A2, B1 and B2, C1 and C2 are contrasted in twos, whether the code of finding out two versions has change.
Substep b, the change point that contrast is found carries out mark, and orientates the change point of mark as operation failed reason.
Above comparison process is a process that automatically performs, and in comparison process, if the code of two versions changes, then change point is marked, and these change points can help the user to navigate to fast the failed reason of script operation.
In addition, unchanged if contrast is found, step 103 can also comprise following substep:
Substep c, the possible cause that the prompting operation is failed, described possible cause comprise database change and/or configuration change.
If namely the code in the file does not change in two versions, then move unsuccessfully may be to change or configuration change causes owing to database to script.In addition, also may be caused by other reasons, the present embodiment is enumerated no longer one by one.
Need to prove, above-mentioned scheme by substep a, b, c performing step 103 is a preferred version of the present embodiment, can realize automatic location, need not the manual analysis location.But step 103 also can be located manually, namely finds the file that needs contrast, and then debugging code is found out change point step by step.Because step 101 and step 102 can automatic analysis go out the method call level in the test script, even therefore manual positioning change point is compared with the scheme that prior art realizes fully manually, also can increase work efficiency.
In addition, automatically performed after the step 102, step 103 can be carried out in following two kinds of situations:
1) a kind of situation is the click real-time analysis location according to the user, and is specific as follows:
When clicking the link of the failed test script of certain operation, according to the test script of this clicked operation failure of the method call step analysis in the described journal file, the reason of positioning trip failure.
In the operational process of test script, if move unsuccessfully, the daily record output byte code that is injected in the test script can record failed script, and the failed regeneration script url returns to the user, after the user clicks this link, will trigger in real time orientation problem reason of step 103.For example, the user clicks failed script url A, the problem reason of the real-time assignment test script of system A then, and positioning result is returned to the user check; If the user clicks failed script url B, the problem reason of the real-time assignment test script of system B and return to the user then.Hence one can see that, and the failed script url that the user does not click will can execution in step 103.
2) another kind of situation is first automatic analysis location, then shows positioning result according to user's click, and is specific as follows:
After execution of step 102, automatically perform: according to the failed test script of all operations of the method call step analysis in the described journal file, locate the failed reason of all operations;
Afterwards, also comprise: when clicking the link of the failed test script of certain operation, therefrom obtain the reason of corresponding operation failure.
Be that system does not check that elder generation orients the problem reason of all scripts automatically in the situation that the user has to click, and positioning result stored, when needing, the user clicks certain failed script url, system directly finds out corresponding positioning result fast from all positioning results of storage, and returns to the user and check.
In the practical application, can select above-mentioned any one mode to realize, the present embodiment is not done restriction to this.
In sum, this method of automatically locating failed use-case in continuing integrating process need not the manual debugging code, therefore can automatically navigate to easily and quickly the problem reason, deal with problems, and maintain easily, save plenty of time and energy, improved work efficiency.
Based on said method embodiment, the application also provides corresponding system embodiment.
With reference to Fig. 2, it is the described a kind of positioning system structure figure that continues integrated failed use-case of the embodiment of the present application.
Described system can comprise that bytecode injects unit 10, method call step analysis unit 20 and failed positioning unit 30, wherein:
Bytecode injects unit 10, when being used for loading the engineering code, injects daily record output byte code in the engineering code;
Method call step analysis unit 20, be used for when operation comprises the test script of described engineering code, call daily record by the recording method of described daily record output byte code before entering each method of test script, and form the journal file of method call level according to the method call daily record;
Failure positioning unit 30 is used for the failed test script of method call step analysis operation according to described journal file, the reason of positioning trip failure.
Preferably, in another system embodiment of the application, described failed positioning unit 30 specifically can comprise following two subelements:
Contrast subunit is used for the method call level according to described journal file, the current version of control methods and the last code that moves successful version;
The mark subelement is used for contrasting the change point of finding and carries out mark, and orientates the change point of mark as operation failed reason.
Preferably, unchanged if contrast is found, described failed positioning unit 30 further can also comprise following subelement:
The prompting subelement is used for the failed possible cause of prompting operation, and described possible cause comprises database change and/or configuration change.
Preferably, in another system embodiment of the application, with reference to shown in Figure 3, described positioning system can also comprise:
Unit 40 is checked in the first click, be used for when clicking the link of the failed test script of certain operation, triggering described failed positioning unit 30, described failed positioning unit 30 is according to the test script of this clicked operation failure of the method call step analysis in the described journal file, the reason of positioning trip failure.
Preferably, in another system embodiment of the application, with reference to shown in Figure 4, described failed positioning unit 30 can according to the failed test script of all operations of the method call step analysis in the described journal file, be located the failed reason of all operations;
Based on this, described positioning system can also comprise:
Unit 50 is checked in the second click, is used for obtaining the reason of corresponding operation failure from described failed positioning unit 30 when clicking the link of the failed test script of certain operation.
For above-mentioned positioning system embodiment because itself and embodiment of the method basic simlarity, so describe fairly simple, relevant part gets final product referring to the part explanation of embodiment of the method shown in Figure 1.
In order to make those skilled in the art more understand the application's realization, below by another more specifically example describe.In this embodiment, will be based on the location of ASM and the lasting integrated failed use-case of SVN Kit realization.
ASM is Java bytecode Treatment Analysis framework, can non-intrusion type ground on-the-fly modifies or generates class, and can drive class to the conversion of bytecode and carry out code analysis.Wherein, described " non-intrusion type " refers to on-the-fly modify or the process of production class can not exert an influence to source code.
SVN is the abbreviation of Subversion, is a kind of Version, by source code is carried out Version Control, thereby reaches the purpose that guarantees file synchronization.SVN Kit is the SVN client library of a pure Java, and the client of using SVN Kit to need not to install any SVN can operate the code of SVN server end.
With reference to Fig. 5, it is the described system construction drawing of another embodiment of the application, and this system is described below:
1) system core System Core can be based on ASM bytecode framework, and dynamically non-intrusion type ground injects daily record output byte code to the engineering code when loading the engineering code, and by the daily record output statement, forms the journal file of method call level;
Described ASM bytecode framework is an Open Framework, and the function of bytecode being injected the engineering code is provided, and utilizes this function, and the present embodiment can be injected into the daily record output byte code of custom feature in the engineering code of loading.When system's operation comprises the test script of described engineering code, before entering each method of test script by described daily record output byte code, the method call log recording can be got off, and form the journal file of method call level by the daily record output statement.
Wherein, described " dynamically " refers to inject daily record output byte code when each loading project file, and this is a dynamic injection process.Described " non-intrusion type " refers to that ASM bytecode framework can make the daily record output byte code that is injected in the engineering code not affect the source code of engineering code.
2) system core System Core can be based on SVN Kit client library, and according to the relation of the method call in the journal file, the current version of contrast class methods and the last time are moved the code of successful version, mark change point;
Described SVN Kit client library is different from the SVN client utility that background technology is mentioned: the SVN client utility is a client software, the user need to install described SVN client utility in client, could manually check code and find out the change point of different editions; And the client of using SVN Kit to need not to install any SVN can operate the code of SVN server end.
SVN Kit provides the file comparison function, but SVN Kit can only carry out single comparative analysis to file in twos.And as previously mentioned, in the embodiment of the present application, a test script is because the hierarchical relationship of method call with the file of a plurality of class methods of correspondence, therefore need to carry out to the file of a plurality of class methods the comparison of different editions.At this moment, the present embodiment can obtain according to the structure of method call relational tree the different editions file of all class methods that needs compare, then the single comparing function that calls SVN Kit contrasts one by one to the file of two versions of appointment, therefrom finds out change point.
3) system core System Core, but automatic monitoring script operation conditions also, if move unsuccessfully, then system can notify the related personnel to follow the tracks of in modes such as mail, instant messagings automatically;
4) related personnel clicks failed script url, and system can show according to the method change point of mark the situation of change of class methods, helps its quick positioning question reason.
With reference to Fig. 6, it injects the process flow diagram of daily record output byte code for ASM.Specific as follows:
Step 601 is injected daily record output byte code by ASM bytecode framework and is arrived in the engineering code (non-intrusion type);
The journal file that step 603, recording method are called;
Before entering each method, by daily record output byte code log recording is arrived specific catalogue, form the journal file of method call relation;
If script moves unsuccessfully, then record failed script, and failed script url is sent to the related personnel;
If script moves successfully, then process ends.
With reference to Fig. 7, it is the example according to user's the real-time comparative analysis of click for the process flow diagram of SVN Kit contrast code change, and is specific as follows:
Step 703 if change, then records and returns change point to the related personnel;
Step 704, otherwise prompting possible cause (such as reasons such as data, configuration changes) is given the related personnel.
In sum, said system is set by the method call that ASM bytecode frame analysis goes out in the Java code, then use the change point of the different editions of the upper associated with (Java code or configuration file) of SVN Kit client library contrast SVN, mark the modification change point, directly click can check which part is different, thereby more convenient, help the user automatically to navigate to the problem reason more quickly, deal with problems.
In addition, based on the application's thought, can also realize by following dual mode:
1) develops based on the kit (Cglib) of ASM encapsulation, analyze and draw the method call relational tree, then from SVN loading source code, manually check the change point of code or file by the SVN client utility.
In this scheme, kit (Cglib) function of ASM encapsulation is too powerful, except the function of injecting bytecode is provided, and the function that also provides more the application not relate to, therefore function is too redundant when realizing the application, has affected analysis efficiency.And, by the obvious mode not as good as automatic contrast shown in Figure 7 of the mode of the manual contrast of SVN client utility.
2) carry out the exploitation second time based on existing Open Source Code coverage rate instrument (Emma), analyze and draw the method call relational tree, then from SVN loading source code, manually check the change point of code or file by the SVN client utility.
With bytecode is injected the engineering code and comes the implementation of acquisition methods call relation to compare, need to develop a large amount of codes based on Emma, and be not suitable for the application, and have the manually problem of contrast.
In sum, the scheme that realizes of Fig. 5, Fig. 6 and Fig. 7 is the application's a preferred embodiment.
Need to prove, for aforesaid embodiment of the method, for simple description, therefore it all is expressed as a series of combination of actions, but those skilled in the art should know, the application is not subjected to the restriction of described sequence of movement, because according to the application, some step can adopt other orders or carry out simultaneously.Secondly, those skilled in the art also should know, the embodiment described in the instructions all belongs to preferred embodiment, and related action or unit module might not be that the application is necessary.
Each embodiment in this instructions all adopts the mode of going forward one by one to describe, and what each embodiment stressed is and the difference of other embodiment that identical similar part is mutually referring to getting final product between each embodiment.
Above a kind of localization method and system that continues integrated failed use-case that the application is provided, be described in detail, used specific case herein the application's principle and embodiment are set forth, the explanation of above embodiment just is used for helping to understand the application's method and core concept thereof; Simultaneously, for one of ordinary skill in the art, the thought according to the application all will change in specific embodiments and applications, and in sum, this description should not be construed as the restriction to the application.
Claims (10)
1. a localization method that continues integrated failed use-case is characterized in that, comprising:
When loading the engineering code, in the engineering code, inject daily record output byte code;
When operation comprises the test script of described engineering code, call daily record by the recording method of described daily record output byte code before entering each method of test script, and form the journal file of method call level according to the method call daily record;
According to the failed test script of the operation of the method call step analysis in the described journal file, the reason of positioning trip failure.
2. method according to claim 1 is characterized in that, described according to the failed test script of the operation of the method call step analysis in the described journal file, the reason of positioning trip failure comprises:
According to the method call level in the described journal file, the current version of control methods and the last code that moves successful version;
The change point that contrast is found carries out mark, and orientates the change point of mark as operation failed reason.
3. method according to claim 2 is characterized in that, and is unchanged if contrast is found, also comprises:
The possible cause that the prompting operation is failed, described possible cause comprise database change and/or configuration change.
4. according to claim 1 to 3 arbitrary described methods, it is characterized in that:
When clicking the link of the failed test script of certain operation, according to the test script of this clicked operation failure of the method call step analysis in the described journal file, the reason of positioning trip failure.
5. according to claim 1 to 3 arbitrary described methods, it is characterized in that,
According to the failed test script of all operations of the method call step analysis in the described journal file, locate after the failed reason of all operations, also comprise:
When clicking the link of the failed test script of certain operation, therefrom obtain the reason of corresponding operation failure.
6. a positioning system that continues integrated failed use-case is characterized in that, comprising:
Bytecode injects the unit, when being used for loading the engineering code, injects daily record output byte code in the engineering code;
Method call step analysis unit, be used for when operation comprises the test script of described engineering code, call daily record by the recording method of described daily record output byte code before entering each method of test script, and form the journal file of method call level according to the method call daily record;
The failure positioning unit is used for the failed test script of method call step analysis operation according to described journal file, the reason of positioning trip failure.
7. system according to claim 6 is characterized in that, described failed positioning unit comprises:
Contrast subunit is used for the method call level according to described journal file, the current version of control methods and the last code that moves successful version;
The mark subelement is used for contrasting the change point of finding and carries out mark, and orientates the change point of mark as operation failed reason.
8. system according to claim 7 is characterized in that, unchanged if contrast is found, described failed positioning unit also comprises:
The prompting subelement is used for the failed possible cause of prompting operation, and described possible cause comprises database change and/or configuration change.
9. according to claim 6 to 8 arbitrary described systems, it is characterized in that, also comprise:
The unit is checked in the first click, be used for when clicking the link of the failed test script of certain operation, triggering described failed positioning unit, described failed positioning unit is according to the test script of this clicked operation failure of the method call step analysis in the described journal file, the reason of positioning trip failure.
10. according to claim 6 to 8 arbitrary described systems, it is characterized in that:
Described failed positioning unit is located the failed reason of all operations according to the failed test script of all operations of the method call step analysis in the described journal file;
Described system also comprises:
The unit is checked in the second click, is used for obtaining the reason of corresponding operation failure from described failed positioning unit when clicking the link of the failed test script of certain operation.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110329521.8A CN103077111B (en) | 2011-10-26 | 2011-10-26 | A kind of localization method of continuous integrating failure use-case and system |
| HK13107354.0A HK1180082A1 (en) | 2011-10-26 | 2013-06-25 | Method and system for positioning a continuous integration failure example |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110329521.8A CN103077111B (en) | 2011-10-26 | 2011-10-26 | A kind of localization method of continuous integrating failure use-case and system |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN103077111A true CN103077111A (en) | 2013-05-01 |
| CN103077111B CN103077111B (en) | 2016-02-10 |
Family
ID=48153644
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110329521.8A Active CN103077111B (en) | 2011-10-26 | 2011-10-26 | A kind of localization method of continuous integrating failure use-case and system |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN103077111B (en) |
| HK (1) | HK1180082A1 (en) |
Cited By (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103488712A (en) * | 2013-09-10 | 2014-01-01 | 迈普通信技术股份有限公司 | Automatized testing method and automatized testing system |
| CN104239114A (en) * | 2013-11-12 | 2014-12-24 | 新华瑞德（北京）网络科技有限公司 | Application compiling method and device |
| CN104360920A (en) * | 2014-12-02 | 2015-02-18 | 微梦创科网络科技（中国）有限公司 | Automatic testing method and device for interface |
| CN104731692A (en) * | 2015-03-12 | 2015-06-24 | 用友网络科技股份有限公司 | Method and device for monitoring continuous integration state |
| CN106681725A (en) * | 2016-12-29 | 2017-05-17 | 广州华多网络科技有限公司 | Code quantity statistical method and device |
| CN107203464A (en) * | 2016-03-17 | 2017-09-26 | 阿里巴巴集团控股有限公司 | The localization method and device of traffic issues |
| CN107766236A (en) * | 2017-09-21 | 2018-03-06 | 平安科技（深圳）有限公司 | Test assignment automatic management method, apparatus, equipment and storage medium |
| CN108959041A (en) * | 2017-05-18 | 2018-12-07 | 腾讯科技（深圳）有限公司 | Method, server and the computer readable storage medium that information is sent |
| WO2019134223A1 (en) * | 2018-01-08 | 2019-07-11 | 平安科技（深圳）有限公司 | Log generation method and apparatus, computer device and storage medium |
| CN110990575A (en) * | 2019-12-18 | 2020-04-10 | 斑马网络技术有限公司 | Test case failure reason analysis method and device and electronic equipment |
| CN111930478A (en) * | 2020-06-08 | 2020-11-13 | 北京每日优鲜电子商务有限公司 | Service calling method and device based on dynamic bytecode |
| US11061808B2 (en) | 2019-10-03 | 2021-07-13 | Red Hat, Inc. | Troubleshooting test failures that occurred during a testing phase of a continuous integration pipeline |
| CN114996128A (en) * | 2022-05-19 | 2022-09-02 | 青矩技术股份有限公司 | Script processing method, device and equipment based on ASM framework and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1818885A (en) * | 2005-02-07 | 2006-08-16 | 佳能株式会社 | Operation logbook obtaining method |
| CN1885273A (en) * | 2005-06-21 | 2006-12-27 | 华为技术有限公司 | Function coverage ratio analysis method for logic test |
| CN101093514A (en) * | 2007-08-20 | 2007-12-26 | 中兴通讯股份有限公司 | Processing system for automated testing log |
| CN101556550A (en) * | 2009-05-22 | 2009-10-14 | 北京星网锐捷网络技术有限公司 | Analysis method for automatic test log and device |
-
2011
- 2011-10-26 CN CN201110329521.8A patent/CN103077111B/en active Active
-
2013
- 2013-06-25 HK HK13107354.0A patent/HK1180082A1/en unknown
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1818885A (en) * | 2005-02-07 | 2006-08-16 | 佳能株式会社 | Operation logbook obtaining method |
| CN1885273A (en) * | 2005-06-21 | 2006-12-27 | 华为技术有限公司 | Function coverage ratio analysis method for logic test |
| CN101093514A (en) * | 2007-08-20 | 2007-12-26 | 中兴通讯股份有限公司 | Processing system for automated testing log |
| CN101556550A (en) * | 2009-05-22 | 2009-10-14 | 北京星网锐捷网络技术有限公司 | Analysis method for automatic test log and device |
Cited By (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103488712A (en) * | 2013-09-10 | 2014-01-01 | 迈普通信技术股份有限公司 | Automatized testing method and automatized testing system |
| CN103488712B (en) * | 2013-09-10 | 2017-08-01 | 迈普通信技术股份有限公司 | A kind of automated testing method and system |
| CN104239114A (en) * | 2013-11-12 | 2014-12-24 | 新华瑞德（北京）网络科技有限公司 | Application compiling method and device |
| CN104360920A (en) * | 2014-12-02 | 2015-02-18 | 微梦创科网络科技（中国）有限公司 | Automatic testing method and device for interface |
| CN104360920B (en) * | 2014-12-02 | 2018-06-26 | 微梦创科网络科技（中国）有限公司 | A kind of automatic interface testing method and device |
| CN104731692B (en) * | 2015-03-12 | 2018-08-31 | 用友网络科技股份有限公司 | Monitor the method and device of continuous integrating state |
| CN104731692A (en) * | 2015-03-12 | 2015-06-24 | 用友网络科技股份有限公司 | Method and device for monitoring continuous integration state |
| CN107203464A (en) * | 2016-03-17 | 2017-09-26 | 阿里巴巴集团控股有限公司 | The localization method and device of traffic issues |
| CN107203464B (en) * | 2016-03-17 | 2020-09-08 | 阿里巴巴集团控股有限公司 | Method and device for positioning service problem |
| CN106681725A (en) * | 2016-12-29 | 2017-05-17 | 广州华多网络科技有限公司 | Code quantity statistical method and device |
| CN108959041A (en) * | 2017-05-18 | 2018-12-07 | 腾讯科技（深圳）有限公司 | Method, server and the computer readable storage medium that information is sent |
| CN107766236A (en) * | 2017-09-21 | 2018-03-06 | 平安科技（深圳）有限公司 | Test assignment automatic management method, apparatus, equipment and storage medium |
| WO2019134223A1 (en) * | 2018-01-08 | 2019-07-11 | 平安科技（深圳）有限公司 | Log generation method and apparatus, computer device and storage medium |
| US11061808B2 (en) | 2019-10-03 | 2021-07-13 | Red Hat, Inc. | Troubleshooting test failures that occurred during a testing phase of a continuous integration pipeline |
| CN110990575A (en) * | 2019-12-18 | 2020-04-10 | 斑马网络技术有限公司 | Test case failure reason analysis method and device and electronic equipment |
| CN110990575B (en) * | 2019-12-18 | 2023-06-23 | 斑马网络技术有限公司 | Test case failure cause analysis method and device and electronic equipment |
| CN111930478A (en) * | 2020-06-08 | 2020-11-13 | 北京每日优鲜电子商务有限公司 | Service calling method and device based on dynamic bytecode |
| CN114996128A (en) * | 2022-05-19 | 2022-09-02 | 青矩技术股份有限公司 | Script processing method, device and equipment based on ASM framework and storage medium |
| CN114996128B (en) * | 2022-05-19 | 2023-03-14 | 青矩技术股份有限公司 | Script processing method, device and equipment based on ASM framework and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN103077111B (en) | 2016-02-10 |
| HK1180082A1 (en) | 2013-10-11 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103077111B (en) | A kind of localization method of continuous integrating failure use-case and system | |
| US9940225B2 (en) | Automated error checking system for a software application and method therefor | |
| CN102402427B (en) | A kind of update method of java application and device | |
| Li et al. | ATOM: Automatic maintenance of GUI test scripts for evolving mobile applications | |
| US8839201B2 (en) | Capturing test data associated with error conditions in software item testing | |
| CN108536589A (en) | A kind of application program buries point methods and system | |
| US9684587B2 (en) | Test creation with execution | |
| EP3769223A1 (en) | Unified test automation system | |
| US20030212983A1 (en) | Method and system for modifying executable code to add additional functionality | |
| US20140109051A1 (en) | Cloud-based software testing | |
| CN104407971A (en) | Method for automatically testing embedded software | |
| US8949794B2 (en) | Binding a software item to a plain english control name | |
| US20140109052A1 (en) | Test environment managed within tests | |
| US9329985B1 (en) | Using emulation to disassociate verification from stimulus in functional test | |
| CN103631720A (en) | Method and device for generating test case | |
| CN101401333A (en) | A debugging method and apparatus for performing telecom class service development based on model driven | |
| WO2015117434A1 (en) | Method and device for manufacturing patch, and method and device for activating patch | |
| CN105528231A (en) | Intermediate auxiliary function-based method and intermediate auxiliary function-based system for dynamically updating software | |
| CN105302549A (en) | Multiple-language-supporting test process generating, debugging and executing system | |
| CN103631719A (en) | Web automated testing method and device | |
| Celik et al. | iCoq: Regression proof selection for large-scale verification projects | |
| CN104572428A (en) | Complicated control testing method based on windows operating system | |
| US10387294B2 (en) | Altering a test | |
| CN113254054B (en) | Intelligent contract one-stop development system and method | |
| US9292422B2 (en) | Scheduled software item testing |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: DE Ref document number: 1180082 Country of ref document: HK |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| REG | Reference to a national code |
Ref country code: HK Ref legal event code: GR Ref document number: 1180082 Country of ref document: HK |