CN1366241A - Program error management system - Google Patents
Program error management system Download PDFInfo
- Publication number
- CN1366241A CN1366241A CN 01100565 CN01100565A CN1366241A CN 1366241 A CN1366241 A CN 1366241A CN 01100565 CN01100565 CN 01100565 CN 01100565 A CN01100565 A CN 01100565A CN 1366241 A CN1366241 A CN 1366241A
- Authority
- CN
- China
- Prior art keywords
- bug
- management system
- servomechanism
- tester
- debug
- 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.)
- Pending
Links
Images
Abstract
A system of program for managing bug can automatically transfer data and flow path processed by the said program without need of manual work to take part in. Data related to the bug is managed by a server. Bug discovered by a testing person is filled automatically, and relevant data are transferred to a debug person who can also transfer the data back through the server after data being processed. Testing person can view the data transferred back in order to make sure whether the result in correct or not. The invention helps to manage and analyze the debugging program and speed up the processing time. The server makes the resource shared.
Description
The present invention relates to a kind of management system, management, analysis and statistics that it is applied to program error particularly relate to a kind of system that comes the supervisory routine mistake by network servicer and database.
The original text of program error is Bug, and original meaning is meant little bedbug, and amplification afterwards is the minor error in the middle of the program, so that make calling program have no idea normally to carry out, or carry out the result who obtains mistake; Bug is meant the mistake on the logic of language mostly, but not phraseological mistake.Generally speaking, software product or program be in last step of production run, some basic functions of test products conformance with standard whether normally, and find out Bug as much as possible, this work is by quality management (QualityAssurance mostly; QA) personnel or tester carry out, and in addition, software product is also often with distribution α or the popular common test of β beta version cause consumer.
Although most Bug can not influence program implementation, but probably can cause program abnormal end or program to crash, and make and to want the loss of data of preserving, so, when finding Bug is arranged, in circulation on the market, then can release new correction (patch) file as product, upgrade voluntarily (update) for the user, to avoid similar thing.
Now general existing Bug treatment scheme, be to test by the tester, when discovery has Bug,, it is passed to suitable debug (debug) personnel again with the Email or the form of file, such mode, be difficult to make test data to share, and same problem, many different people notes and commentary may be arranged again at the same time, thereby cause a problem to be difficult to obtain a satisfactory solution, and influence the ageing and accuracy of many problems.On the other hand, in the management of data, also can cause many problems, the problem of same kind is handled if assign by different people, because resource can't share effectively, and causes the phenomenon of the duplication of labour; And as with the manual delivery file, also may throw into question and can not in time solve because of human negligence.
The object of the present invention is to provide a kind of Bug management system, to address the above problem, the related data that it can transmit Bug does not automatically need manual delivery, and can manage the Bug related data effectively, the purpose that reaches resource sharing and in time handle problems.
Bug management system disclosed according to the present invention, be by a servomechanism, can automatically the tester be found Bug and the related data of filling in, send responsible debug personnel to, and the debug personnel also can pass back to servomechanism with the data that dispose by servomechanism, and servomechanism also can send it to relevant tester automatically, make the tester to inspect, and confirm its result, utilize the convenience of network thus, can make things convenient for management and the analysis of Bug, and can reach the purpose of resource sharing and clear-cut job responsibility, and can not incur loss through delay the processing time by servomechanism.
Below in conjunction with accompanying drawing shown in the embodiment, purpose of the present invention, architectural feature and function thereof are described in further detail.
Fig. 1 is a synoptic diagram of the present invention;
The process flow diagram that Fig. 2 handles for tester of the present invention;
The process flow diagram that Fig. 3 handles for debug personnel of the present invention.
Bug management system disclosed according to the present invention, as shown in Figure 1, the tester enters system at test lead 14, utilize the mode of browser, the Bug related data of being found is sent to servomechanism 12, servomechanism 12 can the Bug related data is sent to debug end 13 gives the debug of being responsible for personnel automatically, after the debug personnel receive the Bug related data, just begin to handle, after disposing, the Bug related data after will handling again uploads on the servomechanism 12, similarly, servomechanism 12 also can be given original tester with automatic data transmission, inspects for it; If disagree with result, can send back to the debug personnel and handle again; If confirm errorless after, Bug relevant treatment program and data that servomechanism 12 can be this time backup in the database 11, and when running into same problem after can being provided with, the phenomenon of the duplication of labour in order to avoid take place in the future in addition reference.
Certainly, in processing procedure, all personnel can be by the mode of browser, to servomechanism 12, go to inquire about relevant data, reach the purpose of resource sharing, and responsible debug personnel are arranged because specify, so can reach clear-cut job responsibility, not worry its ageing and accuracy.On the other hand,, transmit automatically by servomechanism because the data transfer of all is by network, thus the time of manual delivery can be saved, and artificial carelessness, can manage progress and flow process effectively simultaneously.
The actual situation of carrying out, please refer to Fig. 2, test required module (step 21) of testing by the tester, when being found to Bug, then fill in the related data (step 22) of Bug, and personnel's (step 23) of the responsible debug of decision institute, if do not fill in, an appointment Module Design person for this reason automatically then; During actual filling in, be to fill in the single information table of a Bug, include following column:
● the Bug recording mechanism;
● the single numbering of Bug produces in filling in automatically;
● Bug place module numbering, each module all has numbering in the program, is recorded as Bug place mould
Block number;
● start context, the start context of this program;
● the discoverer numbers, and finds the tester's of this Bug numbering;
● the Bug priority level, the seriousness of problem, the priority of Chu Liing just, can be A,
B, C etc.;
● the question marks model, the type number of this problem, for example 101 is interface problem, 102
For database problem, 103 is boundary problem or the like;
● the single main points of Bug, the main points of this list;
● find the date;
● problem points describes in detail, problem is done the description of a summary by the tester;
● the problem points attribute, the attribute of problem is that software issue, H are the hardware problems for S for example
Or the like.
Certainly, during practical application, list does not limit has this some columns, need see the actual needs decision.The data that to fill in upload to servomechanism (step 24) then, and afterwards, servomechanism produces a Bug state table (step 25) automatically, receive for the debug personnel, include:
● Bug recording mechanism, the same recording mechanism;
● find the date;
● discoverer's numbering;
● the single main points of Bug, problem is done the description of a summary by the tester;
● the single state of Bug, define present state, for example 101 be in the debug personnel countermeasure, 102
For the tester confirm in, 104 for regain, 107 for disposing etc.;
● the Bug treatment step, which step record arrives when pre-treatment, and for example 1 for treating debug personnel place
Reason, 2 is personnel's affirmation to be tested etc.;
● Bug place module numbering;
● debug personnel numbering;
And flow process is automatically recorded (step 26), is recorded in Bug single process table, include:
● process recording number;
● the Bug recording mechanism;
● the Bug treatment step, which step record arrives when pre-treatment, and for example 1 for treating debug personnel place
Reason, 2 is personnel's affirmation to be tested etc.;
● Bug place module numbering;
● the date of Bug treatment step, be the date of above-mentioned treatment step, just previous step is intact suddenly
The time that becomes;
● processor's numbering of Bug treatment step;
● the action of Bug treatment step, for example 102 for agree, 104 for regain, 106 for retransmit,
107 transmit or the like;
● the time of Bug treatment step action, be the time of above-mentioned processor's processing;
● processor's suggestion, for recording processing person fills in suggestion;
On the other hand, when the tester fill in be finished after, the debug personnel that are responsible for can or utilize the mode of inquiring about by the inbox on the browser, obtain the related data of Bug, and receive Bug state table (step 31), the processing (step 32) of being correlated with then, or forwarding (step 33), the debug personnel that data are given to other handle, after disposing, fill in corresponding column in the Bug state table, data are back to servomechanism (step 34), servomechanism can be recorded in flow process and data in the Bug single process table (step 35) more then.
And servomechanism can send related data to responsible tester again, the tester can inspect its result, if judge not all right, can handle by retransmitting to return once more to the debug personnel that are responsible for, and if results verification can after, then confirm to wind up the case, servomechanism can be automatically with all data, the flow process and the related data that comprise processing backup to the single filing table of a Bug, include:
● the Bug recording mechanism;
● the single numbering of Bug;
● Bug place module numbering;
● start context;
● discoverer's numbering;
● the Bug priority level;
● the question marks model;
● the single main points of Bug;
● find the date;
● problem points describes in detail;
● the problem points attribute;
● the state of winding up the case;
● wind up the case the date;
Certainly, as previously mentioned, only list the column of some important informations at this, the actual execution is not limited to this, and so backup can be for the usefulness of inquiry in the future.So the present invention utilizes network to transmit the Bug related data, and the treatment scheme that can effectively manage Bug.
The present invention utilizes database and webpage to realize Bug management system based on browser, and its advantage is as follows:
1. utilize internet information servomechanism (Internet Information Server; IIS) realize management, analysis, the statistics of Bug with the technology of database, system maintenance easy, all event handlings are all carried out at servo driver end, and client only needs a browser to get final product.
2. can fully utilize the test data of accumulation, realize sharing of resource, the inquiry of problem points is followed the trail of, and systematic searching is convenient, and result for retrieval can be downloaded by servo driver end at any time or mailing is sent to the related personnel.
3. handle for the people who is responsible for, thereby form clear-cut job responsibility, and can in time deal with problems each positioning problems.
Transmit 4.Bug handle automatically, system can automatically transmit down each Bug, need not manual delivery.
The above only is the present invention's preferred embodiment wherein, is not to be used for limiting practical range of the present invention; All equal variation and modifications of doing according to claim of the present invention, the protection domain that is claim of the present invention is contained.
Claims (15)
1. Bug management system is characterized in that including:
The Bug related data that it has can be managed, deposits and be transmitted to one servomechanism;
One test lead can be for the binding of tester and this servomechanism, and fills in the Bug related data of being found and be sent to this servomechanism; And
One debug end can be for the binding of debug personnel and this servomechanism, and the Bug related data that can be found from this servomechanism acceptance test personnel, and transmits Bug related data after this debug to this servomechanism, inspects it for the tester.
2. Bug management system as claimed in claim 1 is characterized in that this test lead and this debug end are to utilize a browser to upload or data download.
3. Bug management system as claimed in claim 1 is characterized in that this server-side is the mode by Email, with the Bug related data that the tester found, sends responsible debug personnel to.
4. Bug management system as claimed in claim 1 is characterized in that this debug personnel are the modes by inquiry, downloads the tester to this servomechanism and finds the Bug related data.
5. Bug management system as claimed in claim 1 is characterized in that this tester is sent to this servomechanism by filling in the single information table of a Bug with the Bug related data of its discovery.
6. Bug management system as claimed in claim 5 is characterized in that the single information table of this Bug is the column that includes Bug recording mechanism, the single numbering of Bug, Bug place module numbering, start context, discoverer's numbering, Bug priority level, question marks model, the single main points of Bug, finds date, problem points detailed description and problem points attribute.
7. Bug management system as claimed in claim 1 is characterized in that this servomechanism is to fill in the Bug related data of being found according to the tester, produces a Bug state table automatically and downloads for the debug personnel.
8. Bug management system as claimed in claim 7 is characterized in that this Bug state table is to include the column that Bug recording mechanism, discovery date, discoverer's numbering, the single main points of Bug, the single state of Bug, Bug treatment step, Bug place module numbering and debug personnel number.
9. Bug management system as claimed in claim 7 is characterized in that this debug personnel go to other debugs personnel by an action of transmitting with this Bug state table and handle.
10. Bug management system as claimed in claim 7 is characterized in that this servomechanism is to utilize this Bug state table to inspect it for the tester.
11. Bug management system as claimed in claim 10 is characterized in that after this tester inspects, and judges this Bug state table to be retransferred to this servomechanism when wrong, handles for this debug personnel.
12. Bug management system as claimed in claim 1 is characterized in that this servomechanism is that the process recording automatically this Bug handled is in a Bug single process table.
13. Bug management system as claimed in claim 12 is characterized in that this Bug single process table is the column of time of action, the action of Bug treatment step of processor's numbering, the Bug treatment step of date of including process recording number, Bug recording mechanism, Bug treatment step, Bug treatment step, Bug treatment step and processor's suggestion.
14. Bug management system as claimed in claim 12 is characterized in that this tester inspects to finish, confirm that this Bug handles after, this servomechanism is to set up the single filing table of a Bug according to this Bug single process table, for the usefulness of backup.
15. Bug management system as claimed in claim 12 is characterized in that also including a database, in order to store the Bug related data of backup.
16. Bug management system as claimed in claim 14 is characterized in that the single filing table of this Bug is to include Bug recording mechanism, the single numbering of Bug, Bug place module numbering, start context, discoverer's numbering, Bug priority level, question marks model, the single main points of Bug, discovery date, problem points detailed description, problem points attribute, the wind up the case state and the column on the date of winding up the case.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 01100565 CN1366241A (en) | 2001-01-15 | 2001-01-15 | Program error management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN 01100565 CN1366241A (en) | 2001-01-15 | 2001-01-15 | Program error management system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN1366241A true CN1366241A (en) | 2002-08-28 |
Family
ID=4651696
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN 01100565 Pending CN1366241A (en) | 2001-01-15 | 2001-01-15 | Program error management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN1366241A (en) |
-
2001
- 2001-01-15 CN CN 01100565 patent/CN1366241A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8707310B2 (en) | Batch processing of jobs on multiprocessors based on estimated job processing time | |
| US7437713B2 (en) | Automated system that tests software on multiple computers | |
| CN111158674B (en) | Component management method, system, device and storage medium | |
| CN1541348A (en) | Experiment management system, method and medium | |
| CN110109681B (en) | Method and system for converting codes between different platforms | |
| CN109344053B (en) | Interface coverage test method, system, computer device and storage medium | |
| EP2572294A2 (en) | System and method for sql performance assurance services | |
| CN1787000A (en) | System and method for centralized managing and dispatching of batch work | |
| CN111522728A (en) | Method for generating automatic test case, electronic device and readable storage medium | |
| CN111381940B (en) | Distributed data processing method and device | |
| CN1976320A (en) | Data access control method and system | |
| US7536404B2 (en) | Electronic files preparation for storage in a server | |
| CN111125213A (en) | Data acquisition method, device and system | |
| CN113568604A (en) | Method and device for updating wind control strategy and computer readable storage medium | |
| CN1366241A (en) | Program error management system | |
| CN111737349A (en) | Data consistency checking method and device | |
| CN113704077A (en) | Test case generation method and device | |
| CN1374604A (en) | Error managing system in program | |
| CN111026947A (en) | Crawler method and embedded crawler implementation method based on browser | |
| CN1760903A (en) | Flow verification system and method | |
| CN109525642B (en) | LIMS system client data automatic reporting method under user mechanism | |
| CN1945586A (en) | Automatic construction system and method for electronic circuit design | |
| CN100340991C (en) | Cross-platform computer testing system and method | |
| CN1842048A (en) | Data relay method and data relay apparatus | |
| CN117389841B (en) | Method and device for monitoring accelerator resources, cluster equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C02 | Deemed withdrawal of patent application after publication (patent law 2001) | ||
| WD01 | Invention patent application deemed withdrawn after publication |