An Empirical Study of Test Management in Bug Tracking System

Bug-Tracking mechanism is employed only is some of the large software development houses. Most of the others never bothered with bug tracking at all, and instead simply relied on shared lists and email to monitor the status of defects. This procedure is error-prone and tends to cause those bugs judged least significant by developers to be dropped or ignored. Bug-Tracking System is an ideal solution to track the bugs of a product, solution or an application. Bug Tacking System allows individual or groups of developers to keep track of outstanding bugs in their product effectively. This can also be called as Defect Tracking System.


Introduction
The aim of this paper is to prepare the design and functionality of the CAC's Test Management and Defect Management application. This document describes the prototype and database structure of CAC Test Management tool. Our intentions are to produce a user friendly and customizable application according to their business needs.
This document describes the operational use of the application to the project stakeholders (like Business Analyst, Solution Architect and Development Team) and helps them in effective communication, Test estimation, Reuse, effective tracking, able to see assigned test cases and reported defects as well as history of test cases used in different projects.

Literature Survey
Bug Tracking System is an ideal solution to track the bugs of a product, solution or an application. Bug Tracking System allows individual or groups of developers to keep track of outstanding bugs in their product effectively. This can also be called as Defect Tracking System.
The Bug Tracking System can dramatically increase the productivity and accountability of individual employees by providing a documented work flow and positive feedback for good performance.
For many years, bug-tracking mechanism is employed only in some of the large software development houses. Most of the others never bothered with bug tracking at all, and instead simply relied on shared lists and email to monitor the status of defects. This procedure is error-prone and tends to cause those bugs judged least significant by developers to be dropped or ignored.
In any software development bugs are inevitable. Let it be any kind of product bugs arise to any phase of development. One has to take a great care in proper maintenance and resolution of the bugs. In the Existing system the bugs are not properly maintained and they are simply relied on shared lists and email to monitor the bugs. In this type of system it becomes difficult to track a bug if a bug is over looked then it may be cause tremendous errors in the next phase and IJTSRD | May-Jun 2017 Available Online @www.ijtsrd.com can improve the cost of project whatever necessary effort spent on the bug maintenance may not be worthy. So bug history has to be maintained properly. And there is no efficient search technique. One has to search the whole database for the details of particular bug which might have occurred sometime earlier. It is both time consuming and error prone. And it is very difficult to share the bug among several users as there is no proper maintenance of the bugs.
In order to have an efficient product bugs must be maintained properly and should be resolved in time both to reduce time and money spent on the development.

Previous System
In any software development bugs are inevitable. Let it be in any kind of product bugs arise at any phase of development. One has to take a great care in the proper maintenance and resolution of the bugs. In the Existing system the bugs are not properly maintained and they are simply relied on shared lists and email to monitor the bugs.
In this type of system it becomes difficult to track a bug if a bug is over looked then it may cause tremendous errors in the next phase and can improve the cost of project whatever necessary effort spent on the bug maintenance may not be worthy. So bug history has to be maintained properly. And there is no efficient search technique.
One has to search the whole database for the details of particular bug which might have occurred sometime earlier. It is both time consuming and error prone.
And it is very difficult to share the bug among several users as there is no proper maintenance of the bugs. In order to have an efficient product bugs must be maintained properly and should be resolved in time both to reduce time and money spent on the development.

Proposed System
This system maintains the products, Bugs and bug tracking. It has advantage of maintaining bug history it stores all the details from bug origin to bug resolution. Each product can have versions for easy maintenance of the product and all the user of the product is stored in the database. It provides the advantage of maintaining users to the bugs and resolutions provided by them.
Our System provides the searching based on status, priority, and operating system. It provides with user and bug hierarchy, which would be helpful in knowing the relation between bugs and users allotted to the bug. It is provided with a fully authenticated system with password encryption. And has the facility for storing attachments for a bug. One can keep a track of the bug in a product with much lower cost and effort. The most advantage of this system is maintaining log records which are helpful in knowing any errors or misuse of the system by other users. It is shown in the below figure1. In Progress: The Bug is been addressed by the developer and examination is in progress. This stage results in two possible outcomes which are: Fixed or Solved or Rejected Deferred: When a bug cannot be fixed in that particular release it is deferred to future release Rejected: When a bug is invalid it is rejected citing "Not a Bug"

Re-Test: The Bug is fixed and is ready for Re-Test
Re-Open: If the Re-Test failed then the bug is Re-Opened and sent back to the development team Verified: The Bug is retested and retest passed Closed: It is the final stage of the Bug that can be performed only when the Verification or Rejection is complete and validated by the test lead.

Experimental Result
CAC's Test Management and Bug Tracking System is a Windows Forms Application which has been written in C#.NET with the .NET Framework 4.0.
The platform used to design the application is Microsoft Visual Studio 2010 while the database used is MS Access 2013 to store data such as the new test cases or defects created on the front-end. The MS Access database also helps retrieve values and display into the application for the purpose of amending defect statuses and displaying a graph for the report.

Conclusion
We concluded that CAC Test Manager as a tool will ease the communication process between the various project stakeholders and also make testing process more effective by implementing the work flow in the tool. Configuration Management for test cases will be very useful when version control process is followed in the tool. CAC Test Management tool also supports senior management in monitoring the testing metrics and defect metrics dynamically and taking critical decisions about the delivery of project and continuous improvements in the software delivery process (using defect cause).