CN100347682C - Automatic detection building method - Google Patents
Automatic detection building method Download PDFInfo
- Publication number
- CN100347682C CN100347682C CNB2004100892043A CN200410089204A CN100347682C CN 100347682 C CN100347682 C CN 100347682C CN B2004100892043 A CNB2004100892043 A CN B2004100892043A CN 200410089204 A CN200410089204 A CN 200410089204A CN 100347682 C CN100347682 C CN 100347682C
- Authority
- CN
- China
- Prior art keywords
- defective
- test
- management system
- test procedure
- defect
- 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.)
- Expired - Fee Related
Links
Images
Abstract
The present invention relates to an automatic test building method which comprises the steps: obtaining a newest tested object; obtaining a newest test program; generating a test program running list; running a corresponding test program to obtain a running output result; generating an initial fault test program list; leading the fault test program list in a defect managing system; generating a test building report and outputting a test result; modifying a corresponding defect state; generating a new running fault test program list at the next time. The automatic test building method using the steps automatically completes the discovery of defects and the verification after repair, raises the efficiency of development and the test, ensures a uniform code source shared by a developing group, greatly raises the efficiency of the integration test, ensures the reliability of an execution process and the accuracy of defect location and simultaneously provides references for the quality of products.
Description
Technical field
The present invention relates to field of computer technology, the software administration process field of particularly moving in the computer environment specifically is meant a kind of automatic detection building method.
Background technology
Test builds is to carry out the test of software by the mode of robotization.If this building process be carry out every day once be exactly day make up (Daily Build) or be called every day integrated, if repeatedly just be called every day continue integrated.
General software development flow normally, project back allocating task that is decomposed is responsible for different software parts by different people, after exploitation is finished, again each one parts are integrated, form complete software, but this way but there are a lot of problems in practice.
At first, this mode is fit to work between the developer does not have the situation of common factor each other, this in the past phenomenon is very common, but now, along with the expansion of software size, the intensification of sharing out the work and help one another, the degree that interdepends between the developer is more and more higher, and it is more and more difficult that this segregation of duties has clearly become.
Secondly, when software is integrated, tend to occur various problems, but be difficult to where be found to end problem.As if everyone code is all no problem, a large amount of problems occurs but just combine.
So day just make up and to convert integrated work rare to see at ordinary times to frequently carry out job, thereby make complexity integrated become a simple working.By integrated, get rid of defective (Bug) and just become a thing easily with the sky.
The purpose of test builds is in order to find defective, and the defective that checking is repaired in can test builds afterwards.In the prior art, all on the books about test builds process, defect management etc., but this several sections is all relatively independent in the prior art integrated.The test builds technology is a pith of software quality assurance, is the automatic testing process to product.Relevant for the knowledge of test builds with relevant for the flow process of test builds process, a basic premise wherein realizing test builds is to make up to combine with version control system in technique known; For fault management system, generally a relatively independent system in technique known; For project management system, in technique known, also be a relatively independent system generally.
The process of existing test builds, because and fault management system is the process of independently carrying out, like this when the test procedure in test builds is found defective, this defective needs record and management in addition, simultaneously in order to guarantee that each test builds only finds new problem, need in original test builds process manually to make that to have found defective and the test procedure of repairing as yet not out of service.After defective is repaired, the supvr of defective can notify the test builds personnel, manually that is found that again the test procedure of defective joins in next time the test builds, the test builds process can be carried out the checking to this defect repair situation next time, if also have problem just to need to repeat as above operation again.
Flow process as above all is manual, concerning the operator, will be very hard work.
Simultaneously, in existing fault management system, because it is a self-enclosed system, can only write down, follow the tracks of and manage by the user and manually be filled up to defective in the system, after defective is repaired, can only the status report of this defect repair be come out by the user, therefore can not realize interaction with the test builds process, can not import the problem of finding in the test builds automatically, the defective of repairing can not be joined automatically and go checking in the test builds process.
Therefore, fault management system, project management system and the relatively independent problem of test builds process in the prior art, make information sharing and transmission between automatic testing process and the fault management system to realize, can not solve the defective of finding in the software process automatically and verify the defective of repairing, nor can realize the problem of the correspondence of test procedure and tested object automatically.
Summary of the invention
The objective of the invention is to have overcome above-mentioned shortcoming of the prior art, a kind of automatic detection building method based on defect management is provided, this method has realized the integrated of test builds and fault management system, can import to the problem of finding in the test builds process in the fault management system automatically, in test builds next time, treated data in the defective system can be derived again, automatically verify the defective of after last once test builds process, repairing, realize the robotization of test builds process discovery defective and checking repair-deficiency.
Another object of the present invention is to provide a kind of automatic detection building method based on version control tool, binding deficient management system and project management system, this method has realized the combination of project management system and fault management system, make in project management system the name source file of fetcher code on version control tool automatically just by code, realized the combination of project management system and fault management system simultaneously, test procedure and tested object have been combined.
In order to realize above-mentioned purpose, automatic detection building method of the present invention is as follows:
This automatic detection building method, its principal feature is may further comprise the steps:
(1) obtains up-to-date tested object;
(2) obtain up-to-date test procedure and corresponding standard input information and standard output information at this tested object;
(3) from the management system of software defect, obtain make mistakes test procedure tabulation of operation, and, in the up-to-date test procedure that step (2) obtains, reject corresponding testing program, the tabulation of generating run test procedure according to this operation test procedure tabulation that makes mistakes;
(4) the operation test procedure tabulation operation corresponding testing program that generates according to step (3), the result is exported in the operation that obtains corresponding test procedure;
(5) operation output result and the corresponding standard output information with the test procedure in the step (4) compares, if operation output result and standard output information are inconsistent, then writes down the title of test procedure, generates the original test procedure tabulation that makes mistakes;
(6) the original test procedure tabulation that makes mistakes that step (5) is generated imports the management system of software defect;
(7) information of the management system treatment step (6) of software defect importing, and generate this test builds report;
(8) management system of software defect is exported this test builds result;
What (9.1) version control tool record developer submitted to carries out the file name information of defect repair at tested object;
What (9.2) project management system write down simultaneously also that corresponding developer submits to carries out the file name information of defect repair at tested object, and sets up the defect repair record according to this information;
(9.3), corresponding defect state in the management system of software defect is made amendment according to described defect repair record;
(10) when the test builds process begins next time, the management system of software defect generates the new operation test procedure tabulation that makes mistakes.
Obtain up-to-date tested object in this automatic detection building method, may further comprise the steps:
(1) if tested to as if source code, then obtain up-to-date source code earlier, compile this source code then, generate tested object;
(2) if tested to as if the file that can carry out, then directly obtain these files.
Obtain up-to-date test procedure in this automatic detection building method, may further comprise the steps at this tested object:
(1) if test procedure is a source code, then obtains up-to-date test code earlier, compile this test code then, generate test procedure;
(2) if test procedure is the file that can directly carry out, then directly obtain this test procedure.
Standard input information in this automatic detection building method is the standard files input form.
Standard output information in this automatic detection building method is the standard output file form.
The operation output result of the test procedure in this automatic detection building method is operation output destination file form.
The management system of the software defect in this automatic detection building method is handled the original test procedure list information of makeing mistakes that imports, and may further comprise the steps:
(1) according to the original test procedure list information of makeing mistakes, the management system of software defect is carrying out providing information after the respective handling, and pending defect information is submitted to the user automatically;
(2) user handles pending defect information according to this information.
The management system of the software defect in this automatic detection building method is carrying out providing information after the respective handling, may further comprise the steps:
(1) inquires about in the management system of software defect according to the original test procedure list information of makeing mistakes, if this test procedure does not have record in the management system of software defect, then produce the information of " this defective is a new defective " as the case may be, perhaps produce the information of " this defective is a kind of graunch ";
(2) through inquiry, if this test procedure has record in the management system of software defect, then inquire about its corresponding defect repair time, if the time of this defect repair is after the last time test builds, then produce the information of " this defective that test builds was repaired later in last time may really not repaired; repair authentication failed; this defective need be set to not repair state once more " as the case may be, perhaps produce the information of " the new defective that this defective is found for this test procedure "; If the time of this defect repair is before the last time test builds, then produce the information of " this defective is that a defective that has been found that recurs once more " as the case may be, and defective content that will be relevant with this test procedure offers the user, the information of perhaps generation " this defective is the new defective that this test procedure is found ";
(3) do not appear at test procedure in the original test procedure tabulation that makes mistakes once more for the defective of repairing after the last time test builds, the management system of software defect produces the information of " this defective is successfully repaired ".
User in this automatic detection building method handles pending defect information according to this information, may further comprise the steps:
(1) if it is a new defective that this information shows this defective, then the user according to circumstances submits new defective to, and the management system of software defect is bound the test procedure name of this defective and discovery defective automatically;
(2) do not repair success if this information shows this defective, then this defect state of having repaired of user is set to not repair state;
(3) if this information shows the defective of this defective for recurring once more, then this defect state of having repaired of user is set to the recurrence state;
(4) if this information shows this defective is successfully repaired, then user's defect state that will keep this to repair is constant.
User in this automatic detection building method is other users of the management system of structure responsible official or software defect.
Test builds report in this automatic detection building method comprises the quantity report of the quantity and the recurrence defective of this test builds new discovery defects count, normal repair-deficiency, newfound defective title report, normal defective title report of repairing, the title report of recurrence defective, test procedure is found the quantity of defective and the statistical report that test procedure accumulative total is found the quantity of defective in this test builds.
The management system of the software defect in this automatic detection building method comprises the mode of this test builds result output by Email the test builds object information is sent to the developer, provides a fixing URL link by developer's visit and obtain this test builds result.
In this automatic detection building method according to described defect repair record, corresponding defect state in the management system of software defect is made amendment, may further comprise the steps:
(1) project management system will be set up incidence relation between the associated disadvantages in the management system of this defect repair record and software defect;
(2) management system of software defect is set to repair state according to the state of the related information associated disadvantages of the defect repair record of project management system.
Further comprising the steps of after the step of the management system of the original test procedure tabulation importing software defect of makeing mistakes that this test builds process is generated in this automatic detection building method:
The historical information of the corresponding defective of test procedure during (1) management system of software defect is tabulated according to this original test procedure of makeing mistakes and this defective of in the past finding is located the code file relevant with this defective by associated defect repair record in project management system;
(2) in project management system, submit record to, determine corresponding developer and record according to the relevant later code of code file inquiry test builds last time of this defective;
(3), then set up the degree of coupling factor between this defective and the associated code file if this defective is to occur first; If this defective repeats, then increase the value of the degree of coupling factor between this defective and the associated code file.
The new operation that the management system of the software defect in this automatic detection building method generates make mistakes in the test procedure tabulation test procedure for all by last time, the test builds process was found but pairing test procedure of defective that also is not repaired and the new management system that imports this software defect but the pairing test procedure of defective also do not handled by the user.
User in this automatic detection building method is other users of the management system of structure responsible official or software defect.
Adopted the automatic detection building method of this invention, because the test builds process based on defect management is that defect management and building process are combined, make the discovery of defective and the checking after the reparation to finish automatically, improve the efficient of development﹠ testing, saved personnel's work input; Because fault management system and project management system also all are based on the source code management, code file name in the project management system and the test file name in the fault management system can automatically link to the respective file on the version control tool, have guaranteed that a development teams shares unified code source; Because the result of test builds process can directly import in the fault management system, for the details of test result can be complete note, and played directive function for follow-up test builds, make the efficient of integration testing improve greatly; Because whole test builds process is all carried out automatically, there is not human intervention, the combination of fault management system and project management system simultaneously, therefore assignment test program and tested object have fully guaranteed the reliability of implementation and the accuracy of defect location automatically; Simultaneously, owing to by the combining of test builds system and fault management system, the problem of finding in each test builds can be analyzed and added up, and pass through column diagram, modes such as coordinate diagram show, for the quality of product provide can be for reference foundation.
Description of drawings
Fig. 1 is the test builds process model process flow diagram of standard.
Fig. 2 is the test builds process model process flow diagram based on defect management of the present invention.
Fig. 3 handles the process flow diagram of the original test procedure list information of makeing mistakes that imports for fault management system of the present invention.
Fig. 4 changes the process flow diagram of the defect state in the fault management system automatically according to defect repair for project management system of the present invention.
Fig. 5 is that version control tool of the present invention, project management system and fault management system are in conjunction with the process flow diagram of setting up the incidence relation of test procedure and tested object jointly.
Embodiment
In order more to be expressly understood technology contents of the present invention, describe in detail especially exemplified by following examples.
Whole automatic detection building method overall process comprises the combination of following four modules:
● version control tool
● fault management system
● project management system
● the test builds process
1. version control tool
Source code is the chief component of performance history, comes the managed source code can unify the code source of whole development teams by version control tool.A lot of version control tools is arranged in technique known, can be used for carrying out the source code management.Here the version control tool of indication must possess following feature:
● can carry out the Version Control (user can carry out checking in of file and detect operation) of file
● there is instrument can carry out checking in and detecting of file automatically based on order line
2. fault management system
The effect of fault management system is the defective of finding in record, tracking and the management software performance history (Bug).A lot of fault management systems are arranged in technique known.Want to realize the above-mentioned combination in the automatic detection building method, fault management system must increase following feature:
● can write down and operational deficiencies
● defective must possess information such as state (defective of reparation does not still have the defective of reparation), temporal information (repair time) and defect repair responsible official
● defective can be related with a corresponding test procedure, and defective can be found (but under most situation, defective is not to find by test procedure) by test procedure
3. project management system
Project management system can be with the job analysis in the whole performance history, simultaneously in the performance history, the developer is to the change of file on the version control tool, must in project management system, carry out record, just can visit code content on version control tool automatically by the filename of visiting in these records.A lot of project management tools are arranged in technique known.The combination of Shi Xianing in the present invention, project management system must possess following feature:
● there is work to divide in the project management system
● the implementation process of working in the project management system has the submission and the record of code, the code of submitting to can with combine with version control tool, all are submitted to the file on the version control tool, the Checkin record is arranged in project management system, record comprises which being arranged the file of this change (that is to say to have a plurality of files, these a plurality of files are a collection of, finish certain specific function), realize which type of function
● defect repair also is the operation to code, can change defect state automatically when submitting record in project management system
4. test builds process
The test builds process, automatic test course just, it is realized by finishing following committed step automatically:
(1) obtains (perhaps generating) up-to-date tested object (product)
(2) obtain (perhaps generating) up-to-date test procedure (this test procedure need write in advance) at tested object
(3) move all test procedures
(4) result of compare test program run output if the output result and the standard output of giving in advance are inconsistent, writes down the title of test procedure
(5) with the test procedure name output of pinpointing the problems
The test procedure of the structure that takes one's test also must possess following three features except the characteristics with general application program:
● test procedure need be write in advance
● test procedure does not need user intervention when carrying out.In the process of implementation, should not require to continue operation again behind the user's input information, otherwise just not accomplish robotization.Consider this singularity, we substitute user's input information with document form, and this document definition is the input file of standard
● test procedure needed the output file of a standard given in advance before carrying out.This file content is exactly not have the normal postrun output result of test procedure under the situation of defective at tested object, with regard to a similar model answer, has had model answer to compare, and can know just whether the postrun output result of each test procedure is correct.
● the operation result of each test procedure all must output in the file.The operation result of general procedure is directly to output to screen, and this causes realizing the robotization tested, and file that we define this record output object information is the output destination file of test procedure operation.
In the present invention, the characteristics based on the test builds process of source code version control tool integration project management system and fault management system are as follows:
(1) the test builds process can be controlled by script, and system regularly carries out, and whole test builds process does not need user intervention.
(2) test procedure document and the standard output file of each participation test builds need be write in advance, may also comprise the input file of standard sometimes.
(3) test builds needs a comparison process, relatively the difference of the actual output of each test procedure and standard output.
(4) defective of Xiu Fuing can be verified in the test builds process next time automatically.
(5) mistake found of each test builds can in time be recorded in the fault management system, and the test procedure of pinpointing the problems can not continue to participate in test builds next time, guarantees that each test builds all only can find new mistake.
(6) the test builds process can generate the test builds process report automatically.
Further specify below in conjunction with accompanying drawing each exemplary applications be elaborated:
1. the test builds process model of standard
See also shown in Figure 1, test builds begin be by one regularly execution script start, also can manually carry out.Major part all has the function of system timer or plan target in some known operating systems, and permission can activate the program that can carry out at certain special time.
(1) beginning test builds
(2) obtain up-to-date tested object (product)
● situation one: tested to liking source code
■ obtains up-to-date source code earlier
The ■ compile source code generates tested object
● situation two: tested to as if the file that can carry out
■ directly obtains these executable files
(3) obtain up-to-date test procedure and corresponding standard input file and standard output file
● situation one: test procedure is a source code
■ obtains up-to-date test code
■ compiles test code, generates test procedure
● situation two: test procedure can directly be carried out
■ directly obtains these executable test procedures
(4) operation test procedure, tabulation moves test procedure one by one according to the operation test procedure, obtains the output result of each test procedure
(5) output and the standard that contrasts each test procedure exported, if different, sign is made mistakes
(6) the test builds process is finished, and all original test procedure tabulations that make mistakes of pinpointing the problems have been write down in the report of output test builds, report.
2. based on the test builds process model of defect management
See also shown in Figure 2ly again, this test builds process may further comprise the steps:
(1) before generating the test procedure inventory, the test builds process and the standard constructing process of binding deficient management are as broad as long, all will carry out cleaning and obtain up-to-date tested object, the operation of obtaining up-to-date test procedure;
(2) after having obtained test procedure tabulation, the operation that has increased record from fault management system, obtaining before in the test builds model based on the defect management step of test procedure tabulation (test procedure in this tabulation is that each test builds process adds up to join in the fault management system automatically) of makeing mistakes.With rejecting make mistakes test procedure in the test procedure tabulation of the operation of from fault management system, obtaining in the tabulation of the test procedure of front, just generated operation test procedure tabulation essential in this test builds process;
(3) according to operation test procedure tabulation operation corresponding testing program, continue the test builds process;
(4) verify the output of each test procedure, and the output destination file that will write down compares with the standard output file given in advance, wherein the inconsistent test procedure title of result is noted, and generates the original test procedure of makeing mistakes and tabulates;
(5) the above-mentioned original test procedure tabulation that makes mistakes is imported in the fault management system;
(6) in fault management system, handle the information of above-mentioned importing automatically, generate this test builds report.
Carried out the aforesaid operations step, fault management system has just write down the test procedure title that operation makes mistakes in each test builds process, these test procedures will can not continue participating in operation in the test builds process next time, improved the efficient of test builds like this, also helped the test builds process and find new defective.
By above-mentioned cohesive process with fault management system and test builds process, each test procedure of defective of finding is noted by fault management system, in test builds process next time, the test procedure that is recorded is not participated in operation, but fault management system is not also effectively managed defective.But this test builds process can generate the test builds report that comprises following content:
● the test procedure title of new discovery problem
● the test procedure quantity of makeing mistakes
● the quantity before the contrast generates the contrast statistical graph
See also again shown in Figure 3, in the test builds process model based on defect management, after test builds is finished, the original test procedure tabulation that makes mistakes is imported in fault management system, and in fault management system, for the above-mentioned tabulation of new importing, following processing is carried out in unification:
(1) with this newfound test procedure problem, fault management system is carrying out providing information after the respective handling, and pending defect information is submitted to the structure responsible official automatically handle.This information comprises following several situation:
● if this test procedure does not have record in fault management system, then information is:
■ confirms as a new defective with it
■ may be a kind of graunch
● if this test procedure has record in fault management system
If the time of ■ defect repair is that then information is after the last time test builds:
◆ may may really do not repaired in the later defective of repairing of test builds last time, repair authentication failed, this defective need be re-set as the state of reparation
◆ the defective that possible this test procedure is found is new defective
If the time of ■ defect repair is that then information is before last once test builds:
◆ may be that a defective that has been found that recurs once more, and defective content that will be relevant with this test procedure offer the structure responsible official
◆ the defective that possible this test procedure is found is new defective
● the test procedure (promptly not appearing at the test procedure in the original test procedure tabulation that makes mistakes once more) that does not go wrong once more for the defective of after last once test builds, repairing, system is prompted to the structure responsible official with the name of these defectives, and these defectives of prompting explanation are successfully repaired.
(2) make up the responsible official information as above handled, may have following several operation:
● submit new defective (system binds the test procedure title of this defective and discovery defective automatically) to
● a defect state of having repaired is set to not repair state.
● a defect state of having repaired is set to the recurrence state.
(3) generate following test builds report:
● the quantity report of the quantity of this test builds new discovery defects count, normal repair-deficiency and recurrence defective
● newfound defective title report
● normal defective title report of repairing
● the title report of recurrence defective
● the statistical test program is found the quantity of defective, that can comprise this and report accumulative total
(4) with test builds result output, test builds is finished, and this output can be adopted following dual mode simultaneously:
● the mode of transmission.It generally be by Email will be as above information send to the developer, timely transmission that can guarantee information
● the mode that allows the exploitation personnel get, exactly a fixing URL link is offered developer's visit, allow object information that they obtain output (in general, this mode is essential, current record can keep as system journal, also can be used for comparing with later test builds result)
(5) when the test builds process begins next time, fault management system can produce the new operation test procedure tabulation that makes mistakes, and exports it to test builds process, and the test procedure in this tabulation is:
● all find defectives but test procedure that defective also is not repaired
● new import but also do not obtain the test procedure that the user handles
Be somebody's turn to do in the test builds process model based on defect management, its user can also can be other users in the fault management system for making up the responsible official.
3. the automatic checking building process model of the defect repair that combines with project management system of fault management system
Version control tool is responsible for the management of code, the important process content of software project is to write and change the code of product, relation between the code is not isolated fully, one group of (one or more) source code is to be used for realizing or finishing a function, so the interpolation of code or change are carried out often in batches, such change is significant to our record of work, so we are when having changed the code on the version control tool, these codes also are recorded in the project management system, and require submission person to provide the purposes that this batch code is submitted to, finish relevant informations such as which type of function.Two things have been set forth in explanation as above, and a record can be to comprise a plurality of code files, and another one is that the change of code needs other system log (SYSLOG).
On the basis of as above combination, further realize the combination of project management system and fault management system.At first, the initial period of exploitation is just added code, these codes are in order to realize function one by one, but may there be deficiency in the function that these codes are realized, the code that has added does not in other words conform to the function of expection, the said defective of having found that Here it is, we with this defect record in fault management system, at this moment fault management system can be at the given unique numbering of this defective, and prompting will realize that this function development personnel carry out the reparation of defective.Afterwards the developer carry out repair-deficiency process in fact still to the operation of code, by change with delete original code, also may be to increase new code to finish.Operation after finishing is again that the submission of one group of code (is added, change and deletion all are to submit to), this submission is recorded in the project management system again, require again simultaneously to submit to the personnel record to change specifically, the work in current recording mode and stage incipient stage much at one, the purpose of the current change of unique difference is in order to repair a defective that has existed, because each defective has unique numbering, so other something is done in carrying of current record when meeting at submission, change exactly in the fault management system this numbering the state of corresponding defective, never repair state, transfer the reparation state to.
See also shown in Figure 4ly again,, corresponding defect state in the fault management system made amendment, need may further comprise the steps according to the information of defect repair:
(1) file name information of the code that carries out defect repair of version control tool record developer submission;
(2) project management system also writes down the file name information of the code that carries out defect repair of corresponding developer's submission simultaneously, and sets up the defect repair record according to this information;
(3) project management system will be set up incidence relation between the associated disadvantages in this defect repair record and the fault management system;
(4) fault management system is set to repair state according to the state of the related information associated disadvantages of the defect repair record of project management system.
Realized the combination of project management system and fault management system according to above-mentioned steps after, the state that just can change defective automatically submitted in record, but whether current change is effective, also needs this this change is verified.And this moment, test builds exactly can be carried out this checking, test builds joins the pairing test procedure of repairing of defective in this test builds earlier when beginning, whether the operation result of checking this test procedure in the test builds process is correct, if correct, then information is that current defect repair is correct; If incorrect, information may be failed for this this repair.Here the information of saying is only submitted to the user with this situation as the possibility of maximum and is handled, rather than the defective that will repair last time automatically transfers the state of reparation to from the reparation state automatically, because we will consider that this test procedure may find new mistake in current test builds, so the change of state need just can be carried out after the user confirms.
4. the test builds process model of the related and project management system combination of defective
Test generally is divided into two parts, test procedure and tested object, for test procedure generally be what relatively to determine, but the tested object great majority are unascertainable, the associated codes of submitting to by numbering and certain batch of as above certain defective, test procedure and defective is related in addition, has just realized the associated codes that test procedure and certain batch are submitted to, has also just realized the related of test procedure and tested object.
See also shown in Figure 5ly again, between project management system and fault management system, set up test procedure and may further comprise the steps with the related of tested object:
The historical information of the corresponding defective of test procedure during (1) fault management system is tabulated according to this original test procedure of makeing mistakes and this defective of in the past finding is located the code file relevant with this defective by associated defect repair record in project management system;
(2) in project management system, submit record to, determine corresponding developer and record according to the relevant later code of code file inquiry test builds last time of this defective;
(3), then set up the degree of coupling factor between this defective and the associated code file if this defective is to occur first; If this defective repeats, then increase the value of the degree of coupling factor between this defective and the associated code file.
According to the association that above-mentioned steps is set up, possible this association is not an one-one relationship very clearly, but can be as a kind of foundation.When a test procedure is pinpointed the problems in new test builds once more, and when being recorded to fault management system, fault management system can be found the history of defective according to this defective in the past, locate associated code file, the later code of inquiry test builds last time is submitted record in project management system, just can tentatively determine personnel and record that defective is introduced, be who introduces this defective when the code of which time is submitted to prompting thereby can provide automatically.Each in addition affirmation process can be used for changing the degree of coupling factor, increases the value of the corresponding degree of coupling factor when certain defective repeats, and makes that the defective that reappears can be identified and locate in project management system automatically.
This process model combines project management and defect management, make project code record under development in version control tool, and the name of these codes of record in project system simultaneously, the name by code in project management system is the source file of fetcher code on version control tool automatically just.The combination of project management and defect management, can be in fault management system with the defect record in the project, in project management system, will be converted into the specific defects record of repair-deficiency system automatically, and this process can be finished automatically to the record of submitting to certain defect repair.In addition, because being certain test procedure in the test builds process, this defective finds, so this combination just can combine test procedure and tested object (one group of code of repair-deficiency).
Realize the method for test builds process as above,, also need the support of some script files except project management system and fault management system combination:
● from version control tool, obtain up-to-date code and carry out script
● automatic compilation script
● from defective system, obtain the test procedure inventory of not participating in this structure and carry out script
● test procedure inventory after will making up and structure daily record are written to fault management system and carry out script
● handle the information in the defective system automatically and carry out once making up contrast and gathering script with preceding
● Email sends script automatically
Adopt the automatic test building process method based on defect management of the present invention to have following advantage:
1. unify code source
Guarantee that whole development teams shares unified code source, proprietary code is all summed up together, this is the basis of test builds, defect management and project management also all are based on the source code management, and code file name in the project management system and the test file name in the fault management system can automatically link on the respective file of version control tool.
2. help integration testing
Test should all be finished, rather than the mistake that runs into test run is just abandoned test process.Include the detailed information of the test of the detecting information of detecting information, failure of success and failure in the test result.Last result will be notified to corresponding developer by certain mode, require them to revise design or test (if words of the problem of test itself).
3. improve efficient and the work efficiency of finding defective
If test builds is to carry out (day makes up) every day, can find the defective that the coding change of submission on the same day produces in the fastest time, find removing early morning, can improve the efficient of product greatly.The defective of Xiu Fuing can be verified in the test builds process next time automatically in addition, has removed the workload of proof procedure from.
4. guarantee the accuracy of implementation
Whole test builds process is all carried out automatically, does not have human intervention, has fully guaranteed the reliability and the accuracy of implementation.Defect management and project management combination simultaneously, can test procedure and tested object locate automatically.
5. the each result that makes up of contrast guarantees product quality
By with the combining of fault management system, can write down the problem of finding in each test builds automatically, and fault management system can be analyzed to this and add up, and passes through column diagram, modes such as coordinate diagram show the result, for the quality of product provide can be for reference foundation.
In this instructions, the present invention is described with reference to its certain embodiments.But, still can make various modifications and conversion obviously and not deviate from the spirit and scope of the present invention.Therefore, instructions and accompanying drawing are regarded in an illustrative, rather than a restrictive.
Claims (16)
1, a kind of automatic detection building method is characterized in that, described automatic detection building method may further comprise the steps:
(1) obtains up-to-date tested object;
(2) obtain up-to-date test procedure and corresponding standard input information and standard output information at this tested object;
(3) from the management system of software defect, obtain make mistakes test procedure tabulation of operation, and, in the up-to-date test procedure that step (2) obtains, reject corresponding testing program, the tabulation of generating run test procedure according to this operation test procedure tabulation that makes mistakes;
(4) the operation test procedure tabulation operation corresponding testing program that generates according to step (3), the result is exported in the operation that obtains corresponding test procedure;
(5) operation output result and the corresponding standard output information with the test procedure in the step (4) compares, if operation output result and standard output information are inconsistent, then writes down the title of test procedure, generates the original test procedure tabulation that makes mistakes;
(6) the original test procedure tabulation that makes mistakes that step (5) is generated imports the management system of software defect;
(7) information of the management system treatment step (6) of software defect importing, and generate this test builds report;
(8) management system of software defect is exported this test builds result;
What (9.1) version control tool record developer submitted to carries out the file name information of defect repair at tested object;
What (9.2) project management system write down simultaneously also that corresponding developer submits to carries out the file name information of defect repair at tested object, and sets up the defect repair record according to this information;
(9.3), corresponding defect state in the management system of software defect is made amendment according to described defect repair record;
(10) when the test builds process begins next time, the management system of software defect generates the new operation test procedure tabulation that makes mistakes.
2, automatic detection building method according to claim 1 is characterized in that, describedly obtains up-to-date tested object, may further comprise the steps:
(1) if tested to as if source code, then obtain up-to-date source code earlier, compile this source code then, generate tested object;
(2) if tested to as if the file that can carry out, then directly obtain these files.
3, automatic detection building method according to claim 1 is characterized in that, the described up-to-date test procedure that obtains at this tested object may further comprise the steps:
(1) if test procedure is a source code, then obtains up-to-date test code earlier, compile this test code then, generate test procedure;
(2) if test procedure is the file that can directly carry out, then directly obtain this test procedure.
4, automatic detection building method according to claim 1 is characterized in that, described standard input information is the standard files input form.
5, automatic detection building method according to claim 1 is characterized in that, described standard output information is the standard output file form.
6, automatic detection building method according to claim 1 is characterized in that, the operation output result of described test procedure is operation output destination file form.
7, automatic detection building method according to claim 1 is characterized in that, the management system of described software defect is handled the original test procedure list information of makeing mistakes that imports, and may further comprise the steps:
(1) according to the original test procedure list information of makeing mistakes, the management system of software defect is carrying out providing information after the respective handling, and pending defect information is submitted to the user automatically;
(2) user handles pending defect information according to this information.
8, automatic detection building method according to claim 7 is characterized in that, the management system of described software defect is carrying out providing information after the respective handling, may further comprise the steps:
(1) inquires about in the management system of software defect according to the original test procedure list information of makeing mistakes, if this test procedure does not have record in the management system of software defect, then produce the information of " this defective is a new defective " as the case may be, perhaps produce the information of " this defective is a kind of graunch ";
(2) through inquiry, if this test procedure has record in the management system of software defect, then inquire about its corresponding defect repair time, if the time of this defect repair is after the last time test builds, then produce the information of " this defective that test builds was repaired later in last time may really not repaired; repair authentication failed; this defective need be set to not repair state once more " as the case may be, perhaps produce the information of " the new defective that this defective is found for this test procedure "; If the time of this defect repair is before the last time test builds, then produce the information of " this defective is that a defective that has been found that recurs once more " as the case may be, and defective content that will be relevant with this test procedure offers the user, the information of perhaps generation " this defective is the new defective that this test procedure is found ";
(3) do not appear at test procedure in the original test procedure tabulation that makes mistakes once more for the defective of repairing after the last time test builds, the management system of software defect produces the information of " this defective is successfully repaired ".
9, automatic detection building method according to claim 8 is characterized in that, described user handles pending defect information according to this information, may further comprise the steps:
(1) if it is a new defective that this information shows this defective, then the user according to circumstances submits new defective to, and the management system of software defect is bound the test procedure name of this defective and discovery defective automatically;
(2) do not repair success if this information shows this defective, then this defect state of having repaired of user is set to not repair state;
(3) if this information shows the defective of this defective for recurring once more, then this defect state of having repaired of user is set to the recurrence state;
(4) if this information shows this defective is successfully repaired, then user's defect state that will keep this to repair is constant.
According to claim 7,8 or 9 described automatic detection building methods, it is characterized in that 10, described user is other users of the management system of structure responsible official or software defect.
11, automatic detection building method according to claim 1, it is characterized in that, described test builds report comprises the quantity report of the quantity and the recurrence defective of this test builds new discovery defects count, normal repair-deficiency, newfound defective title report, normal defective title report of repairing, the title report of recurrence defective, test procedure is found the quantity of defective and the statistical report that test procedure accumulative total is found the quantity of defective in this test builds.
12, automatic detection building method according to claim 1, it is characterized in that the management system of described software defect comprises the mode of this test builds result output by Email the test builds object information is sent to the developer, provides a fixing URL link by developer's visit and obtain this test builds result.
13, automatic detection building method according to claim 1 is characterized in that, and is described according to described defect repair record, and corresponding defect state in the management system of software defect is made amendment, and may further comprise the steps:
(1) project management system will be set up incidence relation between the associated disadvantages in the management system of this defect repair record and software defect;
(2) management system of software defect is set to repair state according to the state of the related information associated disadvantages of the defect repair record of project management system.
14, automatic detection building method according to claim 13 is characterized in that, the described original test procedure tabulation that makes mistakes that this test builds process is generated imports after the step of management system of software defect further comprising the steps of:
The historical information of the corresponding defective of test procedure during (1) management system of software defect is tabulated according to this original test procedure of makeing mistakes and this defective of in the past finding is located the code file relevant with this defective by associated defect repair record in project management system;
(2) in project management system, submit record to, determine corresponding developer and record according to the relevant later code of code file inquiry test builds last time of this defective;
(3), then set up the degree of coupling factor between this defective and the associated code file if this defective is to occur first; If this defective repeats, then increase the value of the degree of coupling factor between this defective and the associated code file.
15, automatic detection building method according to claim 1, it is characterized in that, the new operation that the management system of described software defect generates make mistakes in the test procedure tabulation test procedure for all by last time, the test builds process was found but pairing test procedure of defective that also is not repaired and the new management system that imports this software defect but the pairing test procedure of defective also do not handled by the user.
16, automatic detection building method according to claim 15 is characterized in that, described user is other users of the management system of structure responsible official or software defect.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100892043A CN100347682C (en) | 2004-12-08 | 2004-12-08 | Automatic detection building method |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2004100892043A CN100347682C (en) | 2004-12-08 | 2004-12-08 | Automatic detection building method |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1648872A CN1648872A (en) | 2005-08-03 |
| CN100347682C true CN100347682C (en) | 2007-11-07 |
Family
ID=34869299
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2004100892043A Expired - Fee Related CN100347682C (en) | 2004-12-08 | 2004-12-08 | Automatic detection building method |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100347682C (en) |
Families Citing this family (18)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101339532B (en) * | 2007-07-06 | 2012-09-05 | 中国银联股份有限公司 | Web application system automatized test method and apparatus |
| CN101267645B (en) * | 2008-02-29 | 2011-03-02 | 中兴通讯股份有限公司 | Automatic test method and system for service flow software development of W base station |
| DE102009014698A1 (en) * | 2009-03-27 | 2010-10-07 | Abb Ag | System and method for automatic testing of a program for safety-related automation systems |
| CN101739339B (en) * | 2009-12-29 | 2013-03-27 | 北京航空航天大学 | Program dynamic dependency relation-based software fault positioning method |
| CN101982815A (en) * | 2010-11-03 | 2011-03-02 | 北京世纪高通科技有限公司 | Software test system and method |
| CN103226488B (en) * | 2013-05-06 | 2016-08-24 | 中国农业银行股份有限公司 | A kind of efficiency control method formalized in code building and device |
| CN103488533A (en) * | 2013-09-06 | 2014-01-01 | 乐视致新电子科技（天津）有限公司 | Program executing method, program executing equipment and program executing system |
| TWI510918B (en) * | 2014-02-20 | 2015-12-01 | Wistron Corp | Method and system for quick testing and detectiing mobile devices |
| CN103970657B (en) * | 2014-05-09 | 2017-02-15 | 中国联合网络通信集团有限公司 | software defect detection method and device |
| CN105407012A (en) * | 2015-10-27 | 2016-03-16 | 浪潮(北京)电子信息产业有限公司 | Automatic test method and device |
| CN106227669B (en) * | 2016-07-29 | 2019-07-12 | 北京金山安全软件有限公司 | Code testing method and device and electronic equipment |
| CN107193677B (en) * | 2017-04-18 | 2020-11-20 | 广州视源电子科技股份有限公司 | Method and system for notifying code defects |
| CN107480049A (en) * | 2017-07-14 | 2017-12-15 | 东软集团股份有限公司 | Defect-restoration method therefor, device and computer equipment |
| CN107729235B (en) * | 2017-09-29 | 2020-11-13 | 百度在线网络技术（北京）有限公司 | Method, apparatus, device and computer readable medium for locating code defect producer |
| CN109840191B (en) * | 2017-11-24 | 2023-12-08 | 南京大学 | An Zhuozhong packet test feedback method based on step prompt |
| CN108197033A (en) * | 2018-01-24 | 2018-06-22 | 智慧海派科技有限公司 | A kind of method that automatic test result notifies related personnel automatically |
| CN110879883B (en) * | 2019-11-29 | 2021-05-28 | 杭州迪普科技股份有限公司 | Software defect repair authorization method and device, computer equipment and storage medium |
| CN113051180B (en) * | 2021-04-30 | 2023-09-29 | 中国平安人寿保险股份有限公司 | Method, device, equipment and storage medium for monitoring test task |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6430708B1 (en) * | 1998-04-17 | 2002-08-06 | Visa International Service Association | Method and apparatus for testing job control language (JCL) members |
| JP2003121511A (en) * | 2001-10-15 | 2003-04-23 | Olympus Optical Co Ltd | Apparatus for generating ic test program |
| JP2003208330A (en) * | 2001-11-19 | 2003-07-25 | Agilent Technol Inc | Electronic test system and method for creating its software program |
| JP2003330748A (en) * | 2002-05-09 | 2003-11-21 | Agilent Technol Inc | Method and apparatus for generating electronic test program and data structure |
-
2004
- 2004-12-08 CN CNB2004100892043A patent/CN100347682C/en not_active Expired - Fee Related
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6430708B1 (en) * | 1998-04-17 | 2002-08-06 | Visa International Service Association | Method and apparatus for testing job control language (JCL) members |
| JP2003121511A (en) * | 2001-10-15 | 2003-04-23 | Olympus Optical Co Ltd | Apparatus for generating ic test program |
| JP2003208330A (en) * | 2001-11-19 | 2003-07-25 | Agilent Technol Inc | Electronic test system and method for creating its software program |
| JP2003330748A (en) * | 2002-05-09 | 2003-11-21 | Agilent Technol Inc | Method and apparatus for generating electronic test program and data structure |
Also Published As
| Publication number | Publication date |
|---|---|
| CN1648872A (en) | 2005-08-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN100347682C (en) | Automatic detection building method | |
| CN1257465C (en) | Method and apparatus for new device driver installation by operating system | |
| CN1215529C (en) | Substrate processing system for managing device information of substrate processing device | |
| CN1680959A (en) | Process editing apparatus and method and process management apparatus and method | |
| CN1666203A (en) | Method and apparatus for automatic sensor installation | |
| CN1942888A (en) | Service activity management system and method for semiconductor manufacturing equipment | |
| CN1271440A (en) | Sckema chauge within a database | |
| CN1967488A (en) | Task allocation method and task allocation apparatus | |
| CN1656599A (en) | Method and apparatus for monitoring tool performance | |
| CN1347054A (en) | Semiconductor article production and producing apparatus, and electronic transaction system and method | |
| CN1703657A (en) | Process for determining competing cause event probability and/or system availability during the simultaneous occurrence of multiple events | |
| CN1532751A (en) | Service processer, service processing method | |
| CN1744054A (en) | Automatic test auxiliary system and corresponding software automatic test method | |
| CN1794647A (en) | Method and its system upload terminal information in equipment management | |
| CN1870028A (en) | Work flow system, work flow processing method and work flow processing program | |
| CN1694224A (en) | Substrate processing system for managing device information of substrate processing device | |
| CN1229728C (en) | WEB application system having management/distributed management function and mechanism for operating the same | |
| CN1258704C (en) | Method for using synergic multiple computer engines based on gridding environment | |
| CN101031884A (en) | Processor | |
| CN101055569A (en) | Function collection method and device of electronic data table | |
| CN1444161A (en) | Resolution method of material detailed list (BOM) data | |
| CN1623826A (en) | Control system for data monitoring device on bus and its method | |
| CN1148651C (en) | Moving object, moving object control method, method and apparatus for generating moving objects, and storage medium for program for generating moving objects | |
| CN1804842A (en) | System and method for database query | |
| CN1301362A (en) | Apparatus for producing software and method for producing software |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20071107 Termination date: 20151208 |
|
| EXPY | Termination of patent right or utility model |