Once a Bug is discovered during testing The Bug is in the new state . 1. The details of the Bug are entered in the defect tracking tool. (details here refers like steps involved in reproducing the Bug build details and error logs if any.) Bug details entered in the defect tracking tool will help the developer to reproduce the bug and providing quick fix to the bug. This state of the Bug is referred to as "OPEN". 2. The developer now starts working on the BUG and fixes the same. Once the Bug is resolved. it is in "Fixed" state. 3. The Tester now proceeds ahead to retest/ reproduce the Bug. Now If the Bug is no more observed during testing then it is declared as "CLOSED" state. 4. if the same Bug is reported by one or many testers then this state of Bug is refferred to as "Duplicate".
Tester verifies the result with the requirement given if there is a change then is known as bug While testing when a bug is found it is reported in the bug tracking tool.
State 1: NEW The bug is reported in the bug tracking tool as NEW state.
The details entered in the bug tracking tool is as follows for a web based application a. Category b. Reproducibility c. Priority d. Severity e. Summary f. Description : OS Environment and Version URL and Login Details Steps to reproduce Expected result Actual Result State 2: ASSIGNED/DEFFERED
The bug is analyzed by the project manager and it is ASSIGNED to the concern developer if the bug is related to the build If it is not a bug then it is reported as DEFFERED. State 3:FEEDBACK
When the tester/developer posts as a QUERY in the bug tracking tool then the developer answers to the query and change the status as FEEDBACK State 4.RESOLVED/FIXED The developer makes the necessary code changes and changes the status as FIXED and passed to the testing team State 5: REOPEN The application with modified code is retested if the bug is reproduced by the testing team then the status is changed to REOPEN and once again it is assigned to the appropriate developer State 6: CLOSED If the bug is rectified or the problem is solved then the status is change to CLOSED
1. Ensure that it is a bug by running the test step again. 2. Ensure that you are testing the right version 3. Ensure that you are testing in the right environment 4. Take narrative (descriptive) screen shots. i.e take screen shots and type directions with it so the developer generates the defect as well. 5. Ensure you assign it to the right developer.
I feel the process is same at any time.. if tester found any job just log it in BTS and need to report to test lead.. he can take the neccesary actions...
Most companies have a bug tracking tool for reporting the bug (eg. Bugzilla is the most popular)
If not then write the steps to reproduce & the Actual & Expected result in an excel sheet & send bug reports to concerned person on daily or weekly basis.
Hope this was what you wanted..if not can you elaborate on exactly what you asked?
