jerry.testing

Few Good Scenarios for ATM Mechines

noreply@blogger.com (jerry) — Mon, 25 Aug 2008 10:24:00 +0000

1.To verify ATM card Insertion
2.To verify ATM card Insertion in wrong angle
3.To verify invalid ATM card Insertion
4.To verify Language selection
5.To verify Pin entry
6.To verify invalid Pin entry
7.To verify invalid Pin entry 3 times
8.To verify Account Type selection
9.To verify Invalid Account Type selection with respectiveto inserted card
10.verify withdrawal option selection
11.verify Amount entry
12.verify Amount entry with wrong denominations(fr eg:00.999Rs)
13.verify withdrawal success operation
14.Verify operation when our entered amount is grater thanpossible balance
15.Verify operation when our entered amount is grater thanday limit
16.Verify when our ATM have lack of Amount
17.Verify when our ATM have network problem
18.Verify Current transaction No.exceeded than day limit
19.Verify operation with exceeded delay in betweenoperations in ATM
20.Verify Cancel after insert card
21.Verify Cancel after Language selection
22.Verify Cancel after Pin entry
23.Verify Cancel after Amount type selection
24.Verify Cancel after withdrawal operation
25.Verify Cancel after Amount entry
26.Verify correction of Amount during entry
27.Verify after successful transaction If customer doesn'ttake the money

QTP Life Saving Tips _1

noreply@blogger.com (jerry) — Sat, 23 Aug 2008 02:55:00 +0000

QTP Testing Process

1. Preparation for Test Flow and Recording.
2. Recording/Scripting Test flow.
3. Enhancing the Test.
4. Debugging the Test.
5. Setup the Test inside FrameWork.
6. Running the Test.
7. Analyzing the Result.

Types of Recording

1. Context Sensitive (Based on Objects)
Window("Index Page").Dialog("Sign In User").WinButton("SignIn").Click
2. Analog (Based on Mouse Moments)
Window("Index Page").RunAnalog "Track 3"
3. Low Level (Based on Coordinates)
Window("Index Page").Dialog("Sign In User").WinButton("SignIn").Click 25,5

Object Repository

1. Local Object Repository
Action specific, can not call in other actions and tests
2. Shared Object Repository
Test Specific, can call in other actions and tests.

Object Identification

1. Normal Identification
First Mandatory Properties and then Assistive Properties until getting the unique description. If both fails QTP will user Ordinal Identifiers (Location and Index).
2. Smart Identification
If this enabled QTP will not use Ordinal Identifiers and will use Base Filter Properties and Optional Filter Properties respectively.

Two Good SQL Tricks

noreply@blogger.com (jerry) — Mon, 14 Jul 2008 12:19:00 +0000

Actually these two things are not Tricks for SQL Masters, but for dummies like me hope this will help a lot.
1. To find the specific table name, with a part of table name we can use this Query
sp_tables '%USR%' This will give u the result of table name with "USR" word.
2. Once you got a table name to get all the details. Just use the table name in ur editor then select the table name fully and press "ALT+F1". This will give you the details about the table, its contents and options inside.

Good Day

Font Setting for QTP Scripting

noreply@blogger.com (jerry) — Sun, 22 Jun 2008 04:49:00 +0000

Here is the best Font setting for QTP Scripting.

The need of Team Support in Testing

noreply@blogger.com (jerry) — Mon, 19 May 2008 05:16:00 +0000

Do not distrub a sleeping Tester

noreply@blogger.com (jerry) — Tue, 29 Apr 2008 10:01:00 +0000

Cool Change Request flow for a good project

noreply@blogger.com (jerry) — Tue, 19 Feb 2008 08:23:00 +0000

Top Ten Mistakes in Web Design

noreply@blogger.com (jerry) — Thu, 14 Feb 2008 10:31:00 +0000

Here is a good link on Top mistakes in Web Design...
worth to know as tester.
http://www.useit.com/alertbox/9605.html

Thanks to Jakob.

Cheers,
Jerald

Screen Resolutin for ur web application

noreply@blogger.com (jerry) — Thu, 14 Feb 2008 10:27:00 +0000

Here is a good link to understand Resolution test
http://www.useit.com/alertbox/screen_resolution.html

If u want to do a little resolution test online....
Here we go...use this link...
http://www.webconfs.com/web-page-screen-resolution.php

Cheers,
Jerald

Few ideas for Regression Test

noreply@blogger.com (jerry) — Thu, 14 Feb 2008 10:22:00 +0000

REGRESSION TEST

Regression test case selection methodology

Code Base Regression Test Selection (CBRTS)
Specification Based Regression Test Selection (SBRTS)
Risk Based Regression Test Selection (RBRTS)

Regression test Folder Structure

Module Level structure (Just with Modules)
Easy to Add
Easy to locate in high level
Easy to maintain in high level

UC level structure under Module (Existing structure of System Tests)
Easy to maintain in functional level / module level
Easy to locate in low level
Easy to maintain in low level
Easy use in future

Regression test selection from System tests

1. Risk Based Tests from every UC.
2. Test case that covers the primary objective / summary outline of the UC.
3. Test case that covers the priority E2E functionalities from that UC.
4. Integrated E2E test cases from UC level.

Conditions to be followed on Regression Test selection

1. Selected tests must cover all the major functionalities of the module.
2. No –ve tests in RT.
3. Selected tests must not concentrate on data type / data change / screen design.
4. Selected tests must not get affected on DBCR/UICR.
5. Selected Regression tests must cover most of the UAT cases.
6. Selected tests must cover all the possible High Risk areas in functional flow.

An wonderful note on ET (Exploratory Testing)

noreply@blogger.com (jerry) — Thu, 24 Jan 2008 05:48:00 +0000

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

noreply@blogger.com (jerry) — Mon, 14 Jan 2008 11:10:00 +0000

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.

noreply@blogger.com (jerry) — Fri, 11 Jan 2008 06:30:00 +0000

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

noreply@blogger.com (jerry) — Tue, 01 Jan 2008 03:28:00 +0000

With Love,
Jerry

How to write a good Defect Report

noreply@blogger.com (jerry) — Fri, 21 Dec 2007 09:32:00 +0000

Here is the key(s)

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.
Calling windows by their correct names (by the name displayed on the title bar) will eliminate some ambiguity.
Don’t be repetitive. Don’t repeat yourself. Also, don’t say things twice or three times.
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.
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.
Proofreading the bug report is very important. Send it through a spell checker before submitting it.
Make sure that all step numbers are sequenced. (No missing step numbers and no duplicates.)
Please make sure that you use sentences. This is a sentence. This not sentence.
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”.
Don’t use vague terms like “It doesn’t work” or “not working properly”
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.
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

noreply@blogger.com (jerry) — Fri, 21 Dec 2007 09:15:00 +0000

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

DETAILS ON DEFECT TRACKING

Use Case Package (M)
Test Case (M)
Detected By (M) (D)
Detected On Date (M) (D)
Defect Type
Status (M) (D)
Detected in Version (M)
Build Number (M)
Assigned To (M) (D)
Business Impact / Severity (M)
Priority
Reproducible (M) (D) 'Y'
Testing Impact (M)
Module / Page
Environment
Defect Summary (M)
Defect Description (M)
Comments
Attachments

Hope this will help a little.

Cheers,

-jerry-

Wishing you all a Blessed Christmas

noreply@blogger.com (jerry) — Thu, 20 Dec 2007 11:15:00 +0000

With Love

-jerry-

AST's Official Magazine December Edition

noreply@blogger.com (jerry) — Tue, 18 Dec 2007 12:43:00 +0000

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

noreply@blogger.com (jerry) — Tue, 18 Dec 2007 12:37:00 +0000

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

noreply@blogger.com (jerry) — Wed, 12 Dec 2007 08:34:00 +0000

Here r the 10 Commandments of Load Testing.

Thou shalt know how thy test tool works.
Thou shalt gather realistic usage data.
Thou shalt have testable requirements.
Thou shalt write a test plan.
Thou shalt test for the worst case.
Thou shalt monitor your test environment infrastructure.
Thou shalt enforce change control on your environment.
Thou shalt use a defect tracking tool.
Thou shalt rule out thy own errors before raising a defect.
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-

Automation Testing Framework for Distributed Systems

noreply@blogger.com (jerry) — Wed, 12 Dec 2007 08:27:00 +0000

BizUnit
The adoption of an automated testing strategy is fundamental in reducing the risk associated with software development projects, it is key to ensuring that you deliver high quality software. Often, the overhead associated with developing automated tests is seen as excessive and a reason to not adopt automated testing.

BizUnit is a framework and as such does not have any dependency on either NUnit of VS Unit Testing, either of these make a great way to drive BizUnit test cases, though equally you could write custom code to do the same.

For further Details Vist :http://www.codeplex.com/bizunit
Thanks to kevinsmi for his great work.

Cheers,
-jerry-

Mother of all checklist for Software testing

noreply@blogger.com (jerry) — Wed, 12 Dec 2007 08:10:00 +0000

Hi All,
Here is the Mother of All Check List for software testing.
Hope this will be very helpful for most of our testing.
http://www.sqaforums.com/download.php?Number=437212
or
http://www.4shared.com/file/31856547/84194eaf/Mother_of_All_CheckListdoc.html

Thanks to Shreya for his wonderful work.

Cheers,
-jerry-

Project Testing Folder Structure

noreply@blogger.com (jerry) — Wed, 05 Dec 2007 11:19:00 +0000

Here is a good Testing Folder Structure. (just a sample)

Cheers,

-Jerry-

Entry and Exit criteria discussion in a Forum - ofcourse me too..

noreply@blogger.com (jerry) — Wed, 05 Dec 2007 11:07:00 +0000

More_Enjoy--
I am testing an web application. Any one can tell me what will be the entry and exist criteria for it.

Joe--
Entry Criteria : A set of decision-making guidelines used to determining whether a system under test is ready to move into, or enter, a particular phase of testing. Entry criteria tend to become more rigorous as the test phases progress. [R. Black]
Exit Criteria : A set of decision-making guidelines used to determining whether a system under test is ready to exit a particular phase of testing. When exit criteria are met, either the system under test moves on to the next test phase or the test project is considered complete. Exit criteria tend to become more rigorous as the test phases progress. [R. Black]

Jerryrajan (Me)--
Here comes the biggest problem of Software Testing. In my view specific definitions will not work for these cases. Because most of the people understand the testing terms in their own way and the very important thing is either they r in the right path or not.In my view the Entry Criteria is a collection of conditions / Objects that are very important to start testing; with out that if you start your testing that will be a failure.Exit Criteria is also collection of conditions / Objects that decides whether you can stop the testing or not.

Richard--
Which part of the definitions that Joe posted do not fulfill what you are saying? As I read them they match up.

Jerryrajan (Me)--
That is my own view Richard, not specifically for Joe.In simple words, "A set of decision-making guidelines" if someone got all guidelines and no resource to follow that.What are the entry criteria?If you r going to prepare a tour plan for your family using your car. What are the entry criteria?You, car, family, then the set of guidelines...correct me if I'm wrong.

Richard--
The guidelines will be specific per project, so the guidelines for deciding if you are going on your road trip would be: - Has the design documents been completed? (Tour plan written)- Are the resources available? (Car, people, luggage, holiday booked) If you can say yes, then you can decided to go live (go on the trip) So the entry criteria and exit criteria should include everything you need to go to the next stage of development, not some of it.

Jerryrajan (Me)--
Agreed.

Portable code editors

noreply@blogger.com (jerry) — Wed, 28 Nov 2007 11:48:00 +0000

As a Test Analyst, one must aware of the code behaviour. To work with codes occasionally some portable code editors are necessary. Here r two good code editors.
Notepad++ supports lot of languages.
VBS edit supports VB Script only. (specifically useful for QTP scripting)

Both are unregistered versions, (freeware anyway) and also portable.
So extract them and run it. (No installation required)
Pls purchase them if you feel they are useful.

http://www.4shared.com/file/30592543/d30fe88a/Notepad_Portable.html
http://www.4shared.com/file/30592566/91537e87/vbsedit_Portable.html

Cheers,
-Jerry-