Wishing You All a Blessed New Year

With Love,
Jerry

How to write a good Defect Report

Here is the key(s)

1. Be very specific when describing the bug. Don’t let there be any room for interpretation. More concise means less ambiguous, so less clarification will be needed later on.
2. Calling windows by their correct names (by the name displayed on the title bar) will eliminate some ambiguity.
3. Don’t be repetitive. Don’t repeat yourself. Also, don’t say things twice or three times.
4. Try to limit the number of steps to recreate the problem. A bug that is written with 7 or more steps can usually become hard to read. It is usually possible to shorten that list.
5. Start describing with where the bug begins, not before. For example, you don't have to describe how to load and launch the application if the application crashes on exit.
6. Proofreading the bug report is very important. Send it through a spell checker before submitting it.
7. Make sure that all step numbers are sequenced. (No missing step numbers and no duplicates.)
8. Please make sure that you use sentences. This is a sentence. This not sentence.
9. Don’t use a condescending or negative tone in your bug reports. Don’t say things like "It's still broken", or “It is completely wrong”.
10. Don’t use vague terms like “It doesn’t work” or “not working properly”
11. If there is an error message involved, be sure to include the exact wording of the text in the bug report. If there is a GPF (General Protection Fault) be sure to include the name of the module and address of the crash.
12. Once the text of the report is entered, you don’t know whose eyes will see it. You might think that it will go to your manager and the developer and that’s it, but it could show up in other documents that you are not aware of, such as reports to senior management or clients, to the company intranet, to future test scripts or test plans. The point is that the bug report is your work product, and you should take pride in your work.

Hope this will help you to write a proper Bug Report.

Thanks to Pavan for his help on this.

Cheers,

-jerry-

DETAILS ON DEFECT TRACKING

Here r few things to be included in the Defect Tab.
(M) - Mandatory
(D) - Default Appearance


DETAILS ON DEFECT TRACKING

1. Use Case Package (M)
2. Test Case (M)
3. Detected By (M) (D)
4. Detected On Date (M) (D)
5. Defect Type
6. Status (M) (D)
7. Detected in Version (M)
8. Build Number (M)
9. Assigned To (M) (D)
10. Business Impact / Severity (M)
11. Priority
12. Reproducible (M) (D) 'Y'
13. Testing Impact (M)
14. Module / Page
15. Environment
16. Defect Summary (M)
17. Defect Description (M)
18. Comments
19. Attachments
    

Hope this will help a little.

Cheers,

-jerry-

Wishing you all a Blessed Christmas

With Love

-jerry-

AST's Official Magazine December Edition

Here we GO,

AST (Association for Software Testing) released their December 2007 Issue of Sapient Testing.
Another Good Work from them. Keep it up friends.

http://www.sapienttesting.com/files/December.Final.pdf

Cheers,
-jerry-

Instant Performance Test

Hi All,

Like to do a instant performance test on your site with no cost. Here we go,
http://www.gomez.com/info_center/instant_test.php
try your site with this and get the instant performance details of it.

Thanks to sapienttesting and Scott Barber for his wonder ful work on December edition.

Cheers,
-jerry-

The 10 Commandments of Load Testing

Here r the 10 Commandments of Load Testing.

1. Thou shalt know how thy test tool works.
2. Thou shalt gather realistic usage data.
3. Thou shalt have testable requirements.
4. Thou shalt write a test plan.
5. Thou shalt test for the worst case.
6. Thou shalt monitor your test environment infrastructure.
7. Thou shalt enforce change control on your environment.
8. Thou shalt use a defect tracking tool.
9. Thou shalt rule out thy own errors before raising a defect.
10. Thou shalt pass on your knowledge.

Visit http://www.myloadtest.com/ten-commandments-of-load-testing/ for full details.

Thanks to Stuart Moncrieff for his wonderful blog and his great service to Our Community.

Don't forget to visit his http://www.mypentest.com/ - security testing blog

and http://www.myloadtest.com/ - load testing blog.

Cheers,

-jerry-