An wonderful note on ET (Exploratory Testing)

Hi All,

Here is a good note on ET by Galvan...
http://www.testingreflections.com/node/view/6455

and one more...
http://shrinik.blogspot.com/2007/12/exploratory-testing-challenged-part-i.html

Cheers,
Jerald

MOBILE CAR LOCK AND START

Suddenly I got this idea in my mind. Now a days most of the people got car they always carry the car key with their remote lock where ever they go. Hence the things we have to carry get increased, like wallet, credit card, mobile phone, car key with remote lock and watch etc. To reduce that I got this simple idea "Mobile Car Lock".

The usual remote car lock works with IR or Blue tooth. Since now a day's most of the mobile comes with both the features, we can use our mobile itself as our car's remote key. But for that we can not use the same hardware mechanism inside our mobile. The problem is if u changed your mobile then u have to change your car lock or its mechanical part inside your mobile.

To avoid that, we can develop a little java mobile program (kind of program that can be run in all mobiles not only in symbian) which will transfer a secure key though IR/BT to the Lock system installed in the car and unlock the car.

More then that we can even make that as car's key, so that we can lock/unlock our car and even start our car with our mobile. Its not necessary to carry our car key and its remote lock everywhere.

If you changed our mobile or lost it, simply install the application in your new mobile and enter your secret code on that. It will lock/unlock/start your car.

If some car company or Lock company created that then this will be an awesome tool to use with.

This may have lot of security issues with that, but they r after all comes with the existing locking mechanisms. More that that we can improve the locking program and make it more secure.

Cheers,
Jerald

Wanna test your webpage live load time.

Here is a little tool free in the web. You can find the page loading time in live and come to an conclusion on your page size, image weight and interface load time.
http://www.hashemian.com/tools/page-load-timer.htm

Also find some usefull tools in that site
http://www.hashemian.com/tools/

Thanks to Hashemian.

Cheers,
Jerry

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-