CN103077111B - A kind of localization method of continuous integrating failure use-case and system - Google Patents
A kind of localization method of continuous integrating failure use-case and system Download PDFInfo
- Publication number
- CN103077111B CN103077111B CN201110329521.8A CN201110329521A CN103077111B CN 103077111 B CN103077111 B CN 103077111B CN 201110329521 A CN201110329521 A CN 201110329521A CN 103077111 B CN103077111 B CN 103077111B
- Authority
- CN
- China
- Prior art keywords
- failed
- test script
- code
- method call
- daily record
- 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
Abstract
This application provides localization method and the system of a kind of continuous integrating failure use-case, to solve the inefficient problem of manual positioning at present.Described method comprises: when loading engineering code, inject daily record output byte code in engineering code; When running package contains the test script of described engineering code, before entering each method of test script, call daily record by the recording method of described daily record output byte code, and form the journal file of method call level according to method call daily record; Failed test script is run, the reason of positioning trip failure according to the method call step analysis in described journal file.The application, without the need to manual debugging code, therefore automatically can navigate to questions and prospect easily and quickly, deal with problems, and maintain easily, and saves plenty of time and energy, improves work efficiency.
Description
Technical field
The application relates to measuring technology, particularly relates to the localization method of a kind of continuous integrating failure use-case, and, a kind of positioning system of continuous integrating failure use-case.
Background technology
Continuous integrating is a kind of practice mode of software development, the mode of robotization is utilized to carry out continuing building (comprise compile, issue, automatic test) to the newly-increased and code of amendment that team developer submits to, at least once a day, find code issue as soon as possible, thus ensure product quality.
A typical continuous integrating cycle comprises following step:
1) continuous integrating server constantly checks code status from version control server, sees whether code has renewal;
2) if find that code has up-to-date submission, so just up-to-date code is downloaded from version control server;
3), after etc. code upgrades completely, call robotization compilation script, carry out code compilation;
4) all automatic tests are run;
5) code analysis is carried out;
6) produce executable software, and be supplied to tester and test.
If wherein any one step failure, just represent this structure failure, continuous integrating server can give corresponding feedback.
When carrying out continuous integrating to projects, if developer revises the partial code in engineering or revises configuration file, all will cause test script failure, thus cause continuous integrating normally not carry out, have a strong impact on the effect and quality of continuous integrating to product development.Now, just must quick positioning question reason, and deal with problems continuous integrating is run well.
The more loaded down with trivial details poor efficiency of means of current orientation problem reason, mainly artificially by Eclipse instrument (Eclipse is famous cross-platform free Sets IDE (IDE)) step by step debugging code analyze program code problem, or artificially by SVN (Subversion, a kind of Version, by carrying out Version Control to source code, thus reach ensure the object of file synchronization) client utility Showlog check that recent code upgrades, and contrast the alteration of program code.
This current two schemes is all carry out analyzing and positioning problem by hand by artificial, now can relate to the problem such as technical experience, maintenance cost, probably find less than problem place when technical experience is not enough, and safeguard very difficult when script is hundreds and thousands of, need to consume a large amount of time and energy so artificially locate, affect work efficiency.
Summary of the invention
The object of the application is, provides localization method and the system of a kind of continuous integrating failure use-case, to solve the inefficient problem of manual positioning at present.
In order to solve the problem, this application discloses the localization method of a kind of continuous integrating failure use-case, comprising:
When loading engineering code, in engineering code, inject daily record output byte code;
When running package contains the test script of described engineering code, before entering each method of test script, call daily record by the recording method of described daily record output byte code, and form the journal file of method call level according to method call daily record;
Failed test script is run, the reason of positioning trip failure according to the method call step analysis in described journal file.
Preferably, the described test script failed according to the method call step analysis operation in described journal file, the reason of positioning trip failure, comprising: according to the method call level in described journal file, current version and the last code running successful version of control methods; The change point that contrast finds is marked, and the change point of mark is orientated as the failed reason of operation.
Preferably, if contrast finds unchanged, also comprise: prompting runs failed possible cause, and described possible cause comprises databases comparison and/or configuration change.
Preferably, when clicking certain and running the link of failed test script, according to the test script of this clicked operation failure of the method call step analysis in described journal file, the reason of positioning trip failure.
Preferably, failed test script is run according to the method call step analysis in described journal file is all, after locating the failed reason of all operations, also comprise: when clicking certain and running the link of failed test script, therefrom obtain the reason of corresponding operation failure.
Present invention also provides the positioning system of a kind of continuous integrating failure use-case, comprising:
Bytecode injection unit, during for loading engineering code, injects daily record output byte code in engineering code;
Method call step analysis unit, for when running package contains 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 method call daily record;
Failure positioning unit, for running failed test script according to the method call step analysis in described journal file, the reason of positioning trip failure.
Preferably, described failed positioning unit comprises:
Contrast subunit, for according to the method call level in described journal file, current version and the last code running successful version of control methods;
Mark subelement, marks for change point contrast found, and the change point of mark is orientated as the failed reason of operation.
Preferably, if contrast finds unchanged, described failed positioning unit also comprises:
Prompting subelement, run failed possible cause for pointing out, described possible cause comprises databases comparison and/or configuration change.
Preferably, described system also comprises: unit is checked in the first click, for triggering described failed positioning unit when clicking certain and running the link of failed test script, described failed positioning unit according to the test script of this clicked operation failure of the method call step analysis in described journal file, the reason of positioning trip failure.
Preferably, described failed positioning unit runs failed test script according to the method call step analysis in described journal file is all, locates the reason that all operations are failed; Described system also comprises: unit is checked in the second click, for when clicking certain and running the link of failed test script, obtains the reason of corresponding operation failure from described failed positioning unit.
Compared with prior art, the application comprises following advantage:
First, the application is in continuous integrating process, in engineering code, daily record output byte code is injected during by loading engineering code, described daily record output byte code is utilized to analyze method call level in test script, then run failed test script according to method call step analysis, finally automatically orient and run failed code point.The method of this automatic location failure use-case, without the need to manual debugging code, therefore automatically can navigate to questions and prospect easily and quickly, deal with problems, and maintain easily, save plenty of time and energy, improve work efficiency.
Secondly, the application uses SVNKit client library automatically to contrast current version and the last method successfully calling version, find out code wherein to change or configuration change, without the need to manual comparison change point, thus more convenient, automatically navigate to questions and prospect more quickly.
Again, all right automatic monitoring script operation conditions of the application, if run unsuccessfully, then in the mode such as mail, instant messaging, system can notify that related personnel follows the tracks of automatically.And related personnel clicks failed script url, system shows the situation of change of class methods according to the method change point of mark, helps its quick positioning question reason.
Certainly, the arbitrary product implementing the application not necessarily needs to reach above-described all advantages simultaneously.
Accompanying drawing explanation
Fig. 1 is the localization method process flow diagram of a kind of continuous integrating failure use-case described in the embodiment of the present application;
Fig. 2 is the positioning system structure figure of a kind of continuous integrating failure use-case described in the embodiment of the present application;
Fig. 3 is the positioning system structure figure of a kind of continuous integrating failure use-case described in another embodiment of the application;
Fig. 4 is the positioning system structure figure of a kind of continuous integrating failure use-case described in another embodiment of the application;
Fig. 5 is the system construction drawing described in 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 that middle SVNKit embodiment illustrated in fig. 5 contrasts code change.
Embodiment
For enabling above-mentioned purpose, the feature and advantage of the application more become apparent, below in conjunction with the drawings and specific embodiments, the application is described in further detail.
When carrying out continuous integrating to projects, in order to quick position is to questions and prospect, the application first automatic analysis goes out the hierarchical relationship of method call in test script, then runs failed test script according to method call step analysis, finally automatically orients and runs failed code point.
Below by embodiment, the application is described in detail.
With reference to Fig. 1, it is a kind of described in the embodiment of the present application localization method process flow diagram of continuous integrating failure use-case.
Step 101, when loading engineering code, injects daily record output byte code in engineering code;
Bytecode (Byte-code) be a kind ofly comprise executive routine, by sequence op code/data to the binary file formed.Bytecode is a kind of intermediate code, and it is more abstract than machine code.It is often counted as the binary file comprising an executive routine, more as an object model.It is because usual each opcode is a byte long that bytecode is named like this, but the length of order code is change.The byte oriented operand that each instruction has from 0 to 255 (or hexadecimal: 00 to FF), is followed by parameter such as register or memory address.
During each test, when loading the engineering code needed for current test, daily record output byte code being injected in engineering code, therefore can not causing amendment to the source code of engineering code.The effect of described daily record output byte code is the hierarchical relationship analyzing method call in test script, and concrete analytical approach such as step 102 describes in detail.
Step 102, when running package contains the test script of described engineering code, calls daily record by the recording method of described daily record output byte code before entering each method of test script, and forms the journal file of method call level according to method call daily record;
The code of mainly some class methods of the code in test script, there is the level call relation of tree-shaped between method, all methods can form a method call relational tree.
In the operational process of test script, each run is to before will entering a method, the call relation of this method and additive method is just carried out log recording by the daily record output byte code being injected into test script, if this method is by another method call, this method can call another method again.By such mode, just having recorded the call relation in test script between all methods, form method call level in final journal file in daily record, is also method call relational tree.The hierarchical relationship of this method call can be used to locate and causes script to run failed reason.
Step 103, runs failed test script according to the method call step analysis in described journal file, the reason of positioning trip failure.
Concrete, step 103 can comprise following two sub-steps:
Sub-step a, according to the method call level in described journal file, current version and the last code running successful version of control methods;
In actual applications, owing between method being the relation called layer by layer, therefore for running failed test script, needing to find corresponding multiple files, carrying out current version respectively and running comparing between two of successful version with the last time.Such as, failed test script is run for certain, three files that have recorded current version class methods code are had according to the hierarchical relationship of method call, file A1, file B1, file C1 respectively, now also need to obtain these three files and run successful edition code in the last time, as file A2, file B2, file C2, then A1 and A2, B1 and B2, C1 and C2 are contrasted between two, whether the code finding out two versions has change.
Sub-step b, marks the change point that contrast finds, and the change point of mark is orientated as the failed reason of operation.
Above comparison process is a process automatically performed, and in comparison process, if the code of two versions changes, is then marked by change point, and these change points can help user's quick position to run failed reason to script.
In addition, if contrast finds unchanged, step 103 can also comprise following sub-step:
Sub-step c, prompting runs failed possible cause, and described possible cause comprises databases comparison and/or configuration change.
If the code namely in file is not change in two versions, then script runs may be unsuccessfully because databases comparison or configuration change caused.In addition, also may be caused by other reasons, the present embodiment will not enumerate.
It should be noted that, the scheme realizing step 103 above by sub-step a, b, c is a preferred version of the present embodiment, can realize automatic location, locate without the need to manual analysis.But step 103 also can be located manually, namely find the file needing contrast, then debugging code finds out change point step by step.Because step 101 and step 102 can go out method call level in test script by automatic analysis, even if therefore manually locate change point, compared with the scheme realized completely manually with prior art, also can increase work efficiency.
In addition, after having automatically performed step 102, step 103 can perform in following two kinds of situations:
1) a kind of situation is located according to the click real-time analysis of user, specific as follows:
When clicking certain and running the link of failed test script, according to the test script of this clicked operation failure of the method call step analysis in described journal file, the reason of positioning trip failure.
In the operational process of test script, if run unsuccessfully, the daily record output byte code be injected in test script can record failed script, and failed regeneration script url returns to user, after user clicks this link, by triggered step 103 orientation problem reason in real time.Such as, user clicks failed script url A, then the questions and prospect of system real-time assignment test script A, and positioning result is returned to user checks; If user clicks failed script url B, then system real-time assignment test script B questions and prospect and return to user.It can thus be appreciated that the failed script url that user does not click, can not perform step 103.
2) another kind of situation is first automatic analysis location, then shows positioning result according to the click of user, specific as follows:
After execution of step 102, automatically perform: run failed test script according to the method call step analysis in described journal file is all, locate the reason that all operations are failed;
Afterwards, also comprise: when clicking certain and running the link of failed test script, therefrom obtain the reason of corresponding operation failure.
Namely system first orients the questions and prospect of all scripts automatically when user does not click and checks, and positioning result is stored, click certain failed script url when the user desires, system directly finds out corresponding positioning result fast from all positioning results stored, and returns to user and check.
In practical application, any one mode above-mentioned can be selected to realize, and the present embodiment does not limit this.
In sum, the method for this failed use-case in automatic location in continuous integrating process, without the need to manual debugging code, therefore can navigate to questions and prospect easily and quickly automatically, deal with problems, and maintain easily, save plenty of time and energy, improve work efficiency.
Based on said method embodiment, present invention also provides corresponding system embodiment.
With reference to Fig. 2, it is a kind of described in the embodiment of the present application positioning system structure figure of continuous integrating failure use-case.
Described system can comprise bytecode injection unit 10, method call step analysis unit 20 and failed positioning unit 30, wherein:
Bytecode injection unit 10, during for loading engineering code, injects daily record output byte code in engineering code;
Method call step analysis unit 20, for when running package contains 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 method call daily record;
Failure positioning unit 30, for running failed test script according to the method call step analysis in 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, for according to the method call level in described journal file, current version and the last code running successful version of control methods;
Mark subelement, marks for change point contrast found, and the change point of mark is orientated as the failed reason of operation.
Preferably, if contrast finds unchanged, described failed positioning unit 30 can also comprise following subelement further:
Prompting subelement, run failed possible cause for pointing out, described possible cause comprises databases comparison and/or configuration change.
Preferably, in another system embodiment of the application, with reference to shown in Fig. 3, described positioning system can also comprise:
Unit 40 is checked in first click, for triggering described failed positioning unit 30 when clicking certain and running the link of failed test script, described failed positioning unit 30 according to the test script of this clicked operation failure of the method call step analysis in described journal file, the reason of positioning trip failure.
Preferably, in another system embodiment of the application, with reference to shown in Fig. 4, described failed positioning unit 30 allly according to the method call step analysis in described journal file can run failed test script, locates the reason that all operations are failed;
Based on this, described positioning system can also comprise:
Unit 50 is checked in second click, for when clicking certain and running the link of failed test script, obtains the reason of corresponding operation failure from described failed positioning unit 30.
For above-mentioned positioning system embodiment, due to itself and embodiment of the method basic simlarity, so description is fairly simple, the part of relevant part embodiment of the method shown in Figure 1 illustrates.
In order to the realization making those skilled in the art more understand the application, below by another more specifically example be described.In this embodiment, the location of continuous integrating failure use-case will be realized based on ASM and SVNKit.
ASM is Java bytecode Treatment Analysis framework, can on-the-fly modify non-intrusion type or generate class, and class can be driven to the conversion of bytecode and carry out code analysis.Wherein, described " non-intrusion type " refers to and to on-the-fly modify or the process of production class can not have an impact to source code.
SVN is the abbreviation of Subversion, is a kind of Version, by carrying out Version Control to source code, thus reaches the object ensureing file synchronization.SVNKit is the SVN client library of a pure Java, using SVNKit without the need to installing the client of any SVN, can operate the code of SVN server end.
With reference to Fig. 5, it is the system construction drawing described in another embodiment of the application, and this system is described below:
1) system core SystemCore, based on ASM bytecode framework, dynamically can inject daily record output byte code to engineering code when loading engineering code non-intrusion type, and by daily record output statement, form the journal file of method call level;
Described ASM bytecode framework is an Open Framework, provides function bytecode being injected engineering code, utilizes this function, and the daily record output byte code of custom feature can be injected in the engineering code of loading by the present embodiment.When system cloud gray model comprises the test script of described engineering code, by described daily record output byte code before each method entering test script, method call log recording can be got off, and form the journal file of method call level by daily record output statement.
Wherein, described " dynamically " refers to the injection 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 be injected in engineering code not affect the source code of engineering code.
2) system core SystemCore, can based on SVNKit client library, and according to the method call relation in journal file, current version and the last code running successful version of contrast class methods, mark change point;
Described SVNKit client library is different from the SVN client utility that background technology is mentioned: SVN client utility is a client software, user needs to install described SVN client utility in client, manually could check code and find out the change point of different editions; And use SVNKit without the need to installing the client of any SVN, the code of SVN server end can be operated.
SVNKit provides file comparison function, but SVNKit can only carry out single comparative analysis to file between two.And as previously mentioned, in the embodiment of the present application, a test script, because the hierarchical relationship of method call is by the file of multiple for correspondence class methods, therefore needs the comparison file of multiple class methods being carried out to different editions.Now, the present embodiment can obtain according to the structure of method call relational tree the different editions file needing to carry out all class methods contrasted, then the file of single comparing function to specify two versions calling SVNKit contrasts one by one, therefrom finds out change point.
3) system core SystemCore, also can automatic monitoring script operation conditions, if run unsuccessfully, then in the mode such as mail, instant messaging, system can notify that related personnel follows the tracks of automatically;
4) related personnel clicks failed script url, and system can show the situation of change of class methods according to the method change point of mark, help its quick positioning question reason.
With reference to Fig. 6, it is the process flow diagram of ASM injection daily record output byte code.Specific as follows:
Step 601, injects daily record output byte code to (non-intrusion type) in engineering code by ASM bytecode framework;
Step 602, testing results script;
Step 603, the journal file that recording method is called;
Before entering each method, by daily record output byte code by log recording to specific catalogue, form the journal file of method call relation;
Step 604, judges the running status of test script;
If script runs unsuccessfully, then record failed script, and failed script url is sent to related personnel;
If script runs successfully, then process ends.
With reference to Fig. 7, it is the process flow diagram of SVNKit contrast code change, is the example analyzed according to the click real time contrast of user, specific as follows:
Step 701, related personnel receives unsuccessfully the message of script, clicks the link of failed script;
Step 702, based on SVNKit client library, according to the method call relation in journal file, current version and the last code running successful version of contrast class methods;
Step 703, if change, then records and returns change point to related personnel;
Step 704, otherwise prompting possible cause (as the reason such as data, configuration change) is to related personnel.
In sum, said system goes out the method call tree in Java code by ASM bytecode frame analysis, then the change point of the different editions of associated with (Java code or configuration file) on SVNKit client library contrast SVN is used, mark amendment change point, direct click can check which part is different, thus more convenient, more quickly help user automatically navigate to questions and prospect, deal with problems.
In addition, based on the thought of the application, can also be realized by following two kinds of modes:
1) kit (Cglib) based on ASM encapsulation is developed, and analyzes and draws method call relational tree, then from SVN loading source code, manually checked the change point of code or file by SVN client utility.
In this scheme, kit (Cglib) function of ASM encapsulation is too powerful, and except providing the function of injection bytecode, additionally provide the function that more the application do not relate to, therefore the function too redundancy when realizing the application, have impact on analysis efficiency.And the mode manually contrasted by SVN client utility is obviously not as good as the mode of contrast automatically shown in Fig. 7.
2) carry out second time exploitation based on existing Open Source Code coverage rate instrument (Emma), analyze and draw method call relational tree, then from SVN loading source code, manually checked the change point of code or file by SVN client utility.
With bytecode is injected engineering code and comes compared with the implementation of acquisition methods call relation, to need to develop a large amount of code based on Emma, and be not suitable for the application, and there is the problem of manually contrast.
In sum, the scheme that Fig. 5, Fig. 6 and Fig. 7 realize is a preferred embodiment of the application.
It should be noted that, for aforesaid embodiment of the method, in order to simple description, therefore it is all expressed as a series of combination of actions, but those skilled in the art should know, the application is not by 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 instructions all belongs to preferred embodiment, and involved 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 the difference with other embodiments, between each embodiment identical similar part mutually see.
Above to localization method and the system of a kind of continuous integrating failure use-case that the application provides, be described in detail, apply specific case herein to set forth the principle of the application and embodiment, the explanation of above embodiment is just for helping method and the core concept thereof of understanding the application; Meanwhile, for one of ordinary skill in the art, according to the thought of the application, all will change in specific embodiments and applications, in sum, this description should not be construed as the restriction to the application.
Claims (8)
1. a localization method for continuous integrating failure use-case, is characterized in that, comprising:
When loading engineering code, in engineering code, inject daily record output byte code, wherein, described daily record output byte code is for analyzing the hierarchical relationship of method call in test script;
When running package contains the test script of described engineering code, daily record is called by the recording method of described daily record output byte code before entering each method of test script, and the journal file of method call level is formed according to method call daily record, wherein, described method call log recording has the call relation of described method and additive method;
Failed test script is run, the reason of positioning trip failure according to the method call step analysis in described journal file;
Wherein, the described test script failed according to the method call step analysis operation in described journal file, the reason of positioning trip failure, comprising: according to the method call level in described journal file, current version and the last code running successful version of control methods; The change point that contrast finds is marked, and the change point of mark is orientated as the failed reason of operation.
2. method according to claim 1, is characterized in that, if contrast finds unchanged, also comprises:
Prompting runs failed possible cause, and described possible cause comprises databases comparison and/or configuration change.
3., according to the arbitrary described method of claim 1 to 2, it is characterized in that:
When clicking certain and running the link of failed test script, according to the test script of this clicked operation failure of the method call step analysis in described journal file, the reason of positioning trip failure.
4., according to the arbitrary described method of claim 1 to 2, it is characterized in that,
Run failed test script according to the method call step analysis in described journal file is all, after locating the failed reason of all operations, also comprise:
When clicking certain and running the link of failed test script, therefrom obtain the reason of corresponding operation failure.
5. a positioning system for continuous integrating failure use-case, is characterized in that, comprising:
Bytecode injection unit, during for loading engineering code, injects daily record output byte code in engineering code, and wherein, described daily record output byte code is for analyzing the hierarchical relationship of method call in test script;
Method call step analysis unit, for when running package contains the test script of described engineering code, daily record is called by the recording method of described daily record output byte code before entering each method of test script, and the journal file of method call level is formed according to method call daily record, wherein, described method call log recording has the call relation of described method and additive method;
Failure positioning unit, for running failed test script according to the method call step analysis in described journal file, the reason of positioning trip failure;
Wherein, described failed positioning unit comprises: contrast subunit, for according to the method call level in described journal file, and current version and the last code running successful version of control methods; Mark subelement, marks for change point contrast found, and the change point of mark is orientated as the failed reason of operation.
6. system according to claim 5, is characterized in that, if contrast finds unchanged, described failed positioning unit also comprises:
Prompting subelement, run failed possible cause for pointing out, described possible cause comprises databases comparison and/or configuration change.
7., according to the arbitrary described system of claim 5 to 6, it is characterized in that, also comprise:
Unit is checked in first click, for triggering described failed positioning unit when clicking certain and running the link of failed test script, described failed positioning unit according to the test script of this clicked operation failure of the method call step analysis in described journal file, the reason of positioning trip failure.
8., according to the arbitrary described system of claim 5 to 6, it is characterized in that:
Described failed positioning unit runs failed test script according to the method call step analysis in described journal file is all, locates the reason that all operations are failed;
Described system also comprises:
Unit is checked in second click, for when clicking certain and running the link of failed test script, obtains the reason of corresponding operation failure from described failed positioning unit.
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 CN103077111A (en) | 2013-05-01 |
| CN103077111B true 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) |
Families Citing this family (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| 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 |
| 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 |
| 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 |
| CN108959041B (en) * | 2017-05-18 | 2021-09-07 | 腾讯科技（深圳）有限公司 | Method for transmitting information, server and computer readable storage medium |
| CN107766236B (en) * | 2017-09-21 | 2021-03-02 | 平安科技（深圳）有限公司 | Test task automatic management method, device, equipment and storage medium |
| CN108228461A (en) * | 2018-01-08 | 2018-06-29 | 平安科技（深圳）有限公司 | A kind of daily record generation method, device, computer equipment 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 |
| 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 |
| CN114996128B (en) * | 2022-05-19 | 2023-03-14 | 青矩技术股份有限公司 | 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| HK1180082A1 (en) | 2013-10-11 |
| CN103077111A (en) | 2013-05-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN103077111B (en) | A kind of localization method of continuous integrating failure use-case and system | |
| CN106909510B (en) | Method for obtaining test case and server | |
| Li et al. | ATOM: Automatic maintenance of GUI test scripts for evolving mobile applications | |
| US7478366B2 (en) | Debugger and method for debugging computer programs across multiple programming languages | |
| CN102402427B (en) | A kind of update method of java application and device | |
| EP2017983A1 (en) | A debugging method and apparatus for performing telecom class service development based on model driven | |
| CN104407971A (en) | Method for automatically testing embedded software | |
| CN105718251A (en) | Multilanguage SDK (software development kit) automatic implementation method and system | |
| CN104407973A (en) | Automatic unit test realizing method and device | |
| CN102063324A (en) | Method and system for implementing automatic programming | |
| CN105512036A (en) | Test template for automatically generating test case according to preset rules and test method | |
| CN105528231A (en) | Intermediate auxiliary function-based method and intermediate auxiliary function-based system for dynamically updating software | |
| CN103699385A (en) | Continuous code integration method | |
| JP2010250378A (en) | Software development support apparatus, system, function extension method for software development support apparatus and program | |
| Celik et al. | iCoq: Regression proof selection for large-scale verification projects | |
| CN110704314A (en) | Fault injection method for embedded software test | |
| CN104317580A (en) | Integrated development environment for virtual test application (APP) | |
| CN110928760B (en) | Unit test method and device in embedded system | |
| CN110750310B (en) | Binary and source code switching method based on IOS system componentization development | |
| Pacheco | Postmortem debugging in dynamic environments | |
| CN103678485A (en) | Virtual experiment process node driving and movable packaging system | |
| CN107797926B (en) | System and method for realizing linux application test automation | |
| Asghar et al. | Efficient debugging of large algorithmic modelica applications | |
| CN112130867B (en) | Research, development and test integrated system | |
| CN115407997A (en) | Agile development application method and system based on low codes |
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 |