Can you List the Top Ten Tips for Bug Tracking?

What are the defects in TRACEABILITY MATRIX?


" There wont be defects as such in RTM RTm basically means mapping the requirements with test cases.to make sure that all the requirements are covered in test cases. "

- Vignesh

What are the fields in the summary report preparation.

"EXECUTIVE SUMMARY TEST OVERVIEW Test Approach Test Strategy Test Scope In Scope: Out of Scope: ENTRY/EXIT CRITERIA SIT Entry Criteria SIT Exit Criteria UAT Entry Criteria UAT Exit Criteria TEST SCHEDULE Calendar of Activities Test Cycles/Results DEFECT SUMMARY effect Severity Levels Defect Count RECOMMENDED NEXT STEP TEST TEAM PARTICIPANTS SIT Testing Support SIT Technical Support UAT Team SUCCESSFUL ACTIVITIES / EVENTS LESSONS LEARNED / RECOMMENDATIONS APPENDIX A (with list of open defects/issues)

- Vignesh

What are tolerance bugs?

"The bug which will not impact the application or performance of the application and can be fixed later "

- Vignesh

What are Attributes of a Bug?

"1. Defect ID
2. Corresponding Test Case ID
3. Summary
4. Steps to reproduce
5. Severity
6. Priority
7. Test Cycle
8. Test Phase
9. Test Environment
10. Detailed Description
12. Module/Sub System defect is noticed
13. Attachments
14. Status
15. Detected By
16. Assigned to
17. Detected On
18. Provision for comments "


- Vignesh

What is Pareto Analysis? Where it will be used?

"Pareto Analysis is a "Problem Identification Tool"...

The Pareto concept is one of the most pwerful quality available to the quality practitioner and is extremely useful in identifying oppurtunities for process improvement."

- Vignesh

What is Pareto Principle?


"Pareto Principle:

Pareto Principle means 80% of the errors comes in 20% of the code..

if we concentrate on 20% code(main functionality) we can redude the number

of defects..."

- Vignesh

What is Test Summary Report ? What are its contents, its format and fields

"Test summary report gives the status of Testing by us,it is nothing but daily report regarding testing .
It consists of different columns based on the company.Some of the columns are
Test case field
No.of test cases executed
No.of pass
No.of fail
Pass percentage
Fail percentage
Comments "

- Vignesh

What is Test Incident Report ? What does it all contain ? What is its format and fields..?


"Test Incident Report:

detailing, for any test that failed, the actual versus expected result, and other information intended to throw light on why a test has failed. This document is deliberately named as an incident report, and not a fault report. The reason is that a discrepancy between expected and actual results can occur for a number of reasons other than a fault in the system. These include the expected results being wrong, the test being run wrongly, or inconsistency in the requirements meaning that more than one interpretation could be made. The report consists of all details of the incident such as actual and expected results, when it failed, and any supporting evidence that will help in its resolution. The report will also include, if possible, an assessment of the impact upon testing of an incident ."

- Vignesh

What are the most common bugs that we find on a daily basis in web based testing. Also can some one give examples of high priority real time bugs and how they solved them?


"Network Problems:

- Page not loading properly
- Accessing the application
- Page breaking
- Data base connections

GUI :

- Java script errors "

- Vignesh

what are the different categories in which the bugs are grouped under in general?

" In general the different categories of bugs are as follows:
1.Bug
2.Cosmetics
3.Enhancements
4.Inaccurate Text
5.Issue"

- Vignesh

what is the process of bug fixing.

" Testing application --> finding the bug---> save to the bug into bug tracking tool with the some unique number --> review by the supervisor--> assigned to the developer---> solve the bug by developer ---> test by the developer ---> i) fixed
ii) Unfixed

If Fixed---> send the new buld for testing ----> create the envirement ----> test by the tester----> no bug found other wise reopen.

This process is continue is going on ."

- Vignesh

what is the difference between bug, defect, problem , fault and issue

"According to me the definition and difference is as under:

Error:
It is the term used to describe a non-conformance to the explicitly stated requirement.

For example: Let me explain with an example. If the requirement mentions 5 Plus 3 Divided by 4; the programmer codes to add 5 and 3 first; and then divides the result [8] by 4 to arrive at result 2.
But if the actual/intended application requirement is to first divide 3 by 4 and then add 5; expecting a result 5.75 then this is a classic Design/Code Error.


Bug:
Assume that the programmer has actually understood the intended requirement correctly but has declared/stored the result as an integer to show a result of 5 instead of 5.75 – this is called a Bug. Here the programmer has to declare the variable as “double or float” and not “int”.

Defect:
A defect is any of the above but found/un-covered in the “released-application” - running in the “Production Servers” [gone “Live”] or may be in “Beta-Release”.

“Defect Trackers” have been christened as such, because they are used to report “Defects” in the software post-release; whereas the issues reported by the Testing Team are predominantly called “Incident Reports” and not “Defect Reports”!

However each organization follows its own terminologies for different contexts and processes; many individuals, may want to contradict and confront me with his/her opinion, on this. But that is a fact-of-life in Software Industry and an Occupational Hazard at that!!!

Fault:
When the application runs without any issues in the intended Production Environment under normal circumstances, but misbehaves after continuously running for about a month or after performing about a million transactions, then we call this condition as Fault.

Let me explain this with an example – Lets say an ‘Order Entry cum Processing’ application has been deployed in a server accessed by public to place orders for movie tickets. Initially when the application starts running – that is when the Application Server is re-started with old log files trashed/removed – the application runs with a throughput of 100 transactions per minute. But after about one million transactions, if the application’s throughput reduces to about 50 transactions per minute, then, we call this condition as a FAULT.

Technically, in this case, probably the Database connections are not closed properly, leading to too many Open Connections and hence waiting for a DB connection-object in the Connection Pool - leading to degradation of performance/throughput. Or may be the application is constructed to create avoidable “new” objects and expecting the JVM to clean up the garbage – which may also cause degradation in throughput over time. This is what I call as Fault. On restart the application works fine – so this is a classic case, where you don’t find any apparent Error.

Oxford Definitions are as under:

ERROR >>> :

noun 1 a mistake. 2 the state of being wrong in conduct or judgment. 3 technical a measure of the estimated difference between the observed or calculated value of a quantity and its true value.

ORIGIN Latin, from errare ‘to stray, err’

BUG >>> :

noun - an error in a computer program or system.

ORIGIN of unknown origin

DEFECT >>> :

noun - a shortcoming, imperfection, or lack.

ORIGIN Latin defectus, from deficere ‘desert or fail’

FAULT >>> :

noun 1 an unattractive or unsatisfactory feature; a defect or mistake. 2 responsibility for an accident or misfortune. 3 (in tennis) a service that infringes the rules. 4 Geology an extended break in a rock formation, marked by the relative displacement and discontinuity of strata.

DERIVATIVES faultless adjective faultlessly adverb.

ORIGIN from Latin fallere ‘deceive’

- Vignesh

what are the characteristic of efficient bug reporting ?

"Fundamentals of the bug reporting can be explained but the actual reporting depends on factors like tools used, management focus, information availability, etc.

Important Charecteristics:

1. Present the As-Is data, do not modify to please any section of recepient. This happens quite often

2. Group the defect causes and highlight the ones which cause most defects (Pareto), don't just report bugs provide analysis and possible resolutions

3. Provide statistics of test progression and corresponding defects count

4. Highlight showstoppers

5. Graphical representation of test progress helps higher management to get a better perspective into the progress without having to read through the entire document.

6. Emphasize on the turn around time taken to resolve bugs

- Vignesh

What are the severity and priority levels in Rational Clear Quest.

"The ClearQuest Administrator can probably define these levels to suit the company's individual needs.

I have seen the Priority Levels defined as:

1 - High, 2 - Medium, 3 - Low. The priority level is normally determined by the end-user's need for the fix.

I have seen the Severity Levels defined as:

1 - Critical, 2 - Serious, 3 - Moderate, 4 - Minor, 5 - Cosmetic. The severity level is normally determined by the impact the defect has on the end-user process. "

- Vignesh

What is biggest bug you ever found in Testing Environment ?

"During system testing, when the exe file was executed that will initiate the application failed to run. Similar issues were found during other phases also like integration testing when the login module that accepts the username and password which takes the user to the next module.. the system did not respond as expected "

- vignesh

What is meant by P1 bug? any another similar bugs


"P1 bug is a critical bug which needs an immediate fix without which the application can't continue functioning. P1 bug needs an immediate attention and needs to be fixed within 4 hours from the time it's been reported.

For example, let's consider a banking application. If the server is crashing for every 2 mins then it's a P1 bug"

what do mean by bug tracking?give example?

" The "Bug Tracking" is a Tracking process of the status of the bug once it is detected and reported by the tester. The client and your PM or the test leads gets to know the number of bugs found and what is its status like : Assigned to the developer , Reopened or closed and also the severity and the priority of the bug.This is done with the help of various tools: Bugzilla, Test Director. "


- Vignesh

What is GOLDEN BUG?

" Golden Bug Means wich effect more critical parts and majore functions in application.this one is identified by using tracebility matrix.no of functions it will effect "


- Vignesh

what is bug leak?

" The defect which can be found and Re-produced by End user/Client people the same we(Test Engineer) unable to found at the time of testing. This is also known as "Defect Leakage"."


- Vignesh