S/w fAQ's
S.No   Category views Poted On
1 SQA and testing frequently asked definitions

TESTING

 999 01/01/08
2 Load testing interview questions

TESTING

 2547 01/01/08
3 Performance Testing Considerations

TESTING

 525 01/01/08
4 what is testing?

TESTING

 658 01/01/08
5 blackbox testing tips

TESTING

 4254 01/01/08
6 Tester Tips

TESTING

 6589 01/01/08
7 Interview with Brian Marick on How to do Good Test..

TESTING

 254 01/01/08
8

WEB Testing Interview Questions For software teste...

TESTING

 5846 02/02/08
9 General interview questions

TESTING

 5554 02/02/08
10 Latest Questions in Testing Definations

TESTING

 5885 02/02/08
11 Software Testing Interview Questions

TESTING

 556 02/02/08
12 Interview Questions for Software Testers.

TESTING

 658 02/02/08
13 Testing Interview Questions

TESTING

 2135 02/02/08
14 Testing Tools Interview Questions

TESTING

 245 02/02/08
15 TESTING TOOLS INTERVIEW QUESTIONS-Part2

TESTING

 546 02/02/08
16 TESTING TOOLS INTERVIEW QUESTIONS-Part1

TESTING

 879 02/02/08
17 Fuzz testing

TESTING

 1245 02/02/08
18 Defect Tracking & Formal Verification

TESTING

 471 02/02/08
19 Test Cases, Suits, Scripts

TESTING

 501 02/02/08
20 Compatibility Testing

TESTING

 2456 02/02/08
21 System Testing & Regression Testing

TESTING

 4511 02/02/08
22 Beta Testing & Product Testing

TESTING

 6548 02/02/08
23 Installation Testing & Alpha Testing

TESTING

 235 02/02/08
24 Stability Testing & Acceptance Testing

TESTING

 546 02/02/08
25 Usability Testing

TESTING

 546 02/02/08
26 Stress Testing & Security Testing

TESTING

 856 02/02/08
27 Performance Testing

TESTING

 214 02/02/08
28 Unit Testing & Integration Testing

TESTING

 568 02/02/08
29 White Box & Black Box Testing

TESTING

 546 02/02/08
30 Interview questions on WinRunner TESTING 125 03/02/08
31 Testing Tools Interview Questions TESTING 658 03/02/08
32 Testing Tools Interview Questions-2 TESTING 5488 03/02/08
33 Testing Tools Interview Questions-3 TESTING 254 03/02/08
34 Testing Tools Interview Questions-4 TESTING 987 03/02/08
35 Testing Tools Interview Questions TESTING 2456 03/02/08
36 Testing Tools Interview Questions TESTING 2145 03/02/08
37 Software Testing 10 Rules-Bugs and fixes TESTING 985 03/02/08
38 How to Write a Fully Effective Bug Report TESTING 357 03/02/08
39 Testing Reviews--methodology and techniques TESTING 159 03/02/08
40 Load and Performance Test Tools TESTING 658 03/02/08
41 TESTING 856 03/02/08
42 Debugging Strategies, Tips, and Gotchas TESTING 2145 03/02/08
43 Web services programming tips and tricks: Stress t... TESTING 84754 03/02/08
44 Web services programming tips and tricks: improve ... TESTING 2358 03/02/08
45 WinRunner Interview Questions TESTING 3569 03/02/08
46 LoadRunner Interview Questions TESTING 1245 03/02/08
47 SilkTest Interview Question TESTING 845 03/02/08
48 Software QA and Testing Frequently-Asked-Questions... TESTING 21 03/02/08
49 Systematic Software Testing TESTING 254 03/02/08
50 Software Testing-Introduction TESTING 2586 03/02/08
51 Tips for Releasing Software for Customer Testing TESTING 358 03/02/08
52 Software Regression Testing TESTING 951 03/02/08
53 TestComplete 4 - Automate the Non-Automatable. TESTING 32558 03/02/08
54 webtest tools TESTING 245 03/02/08
55 webtest tools TESTING 956 03/02/08
56 Applying Patterns to Software Testing TESTING 845 03/02/08
57 The Software Testing Automation Framework TESTING 326 03/02/08
58 Testing Tools Interview Questions and Faqs-unanswe... TESTING 745 03/02/08
53 latest and unanswered Questions in Rational Robot ... TESTING 5125 03/02/08
54 Buttons TESTING 648 03/02/08
55 XPLANNER TESTING 213 03/02/08
56 Testing Tools Interview Questions TESTING 9547 03/02/08
57 Web services programming tips and tricks: TESTING 852 03/02/08
         

How to Write a Fully Effective Bug Report

To write a fully effective report you must:
- Explain how to reproduce the problem - Analyze the error so you can describe it in a minimum number of steps.
- Write a report that is complete and easy to understand.

Write bug reports immediately; the longer you wait between finding the problem and reporting it, the more likely it is the description will be incomplete, the problem not reproducible, or simply forgotten.

Writing a one-line report summary (Bug's report title) is an art. You must master it. Summaries help everyone quickly review outstanding problems and find individual reports. The summary line is the most frequently and carefully read part of the report. When a summary makes a problem sound less severe than it is, managers are more likely to defer it. Alternatively, if your summaries make problems sound more severe than they are, you will gain a reputation for alarmism. Don't use the same summary for two different reports, even if they are similar. The summary line should describe only the problem, not the replication steps. Don't run the summary into the description (Steps to reproduce) as they will usually be printed independently of each other in reports.

Ideally you should be able to write this clearly enough for a developer to reproduce and fix the problem, and another QA engineer to verify the fix without them having to go back to you, the author, for more information. It is much better to over communicate in this field than say too little. Of course it is ideal if the problem is reproducible and you can write down those steps. But if you can't reproduce a bug, and try and try and still can't reproduce it, admit it and write the report anyway. A good programmer can often track down an irreproducible problem from a careful description. For a good discussion on analyzing problems and making them reproducible, see Chapter 5 of Testing Computer Software by Cem Kaner.

The most controversial thing in a bug report is often the bug Impacts: Low, Medium, High, and Urgent. Report should show the priority which you, the bug submitter, believes to be appropriate and doe