Art of Testing

Software Testing

noreply@blogger.com (S.U.Sankar) — Fri, 07 Aug 2009 00:36:00 PDT

What is Software Testing?

In general, testing is finding out how well something works. In terms of human beings, testing tells what level of knowledge or skill has been acquired. In computer hardware and software development, testing is used at key checkpoints in the overall process to determine whether objectives are being met. For example, in software development, product objectives are sometimes tested by product user representatives. When the design is complete, coding follows and the finished code is then tested at the unit or module level by each programmer; at the component level by the group of programmers involved; and at the system level when all components are combined together. At early or late stages, a product or service may also be tested for usability.

At the system level, the manufacturer or independent reviewer may subject a product or service to one or more performance tests, possibly using one or more benchmarks. Whether viewed as a product or a service or both, a Web site can also be tested in various ways - by observing user experiences, by asking questions of users, by timing the flow through specific usage scenarios, and by comparing it with other sites.

The answer to the primary role of software testing is two fold:

Determine whether the system meets specifications (Producer View), and
Determine whether the system meets business and user needs (Customer View)

Testing encompasses three concepts:

The demonstration of the validity of the software at each stage in the system development life cycle.
Determination of the validity of the final system with respect to user needs and requirements.
Examination of the behavior of a system by executing the system on sample test data.

Your Ad Here

Software Metrics

noreply@blogger.com (S.U.Sankar) — Fri, 07 Aug 2009 00:33:00 PDT

METRICS

Although general set of standards has been agreed upon, the appropriate metrics to test how well software meets those standards are still poorly defined. Publications by IEEE, have presented numerous potential metrics that can be used to test each attribute. Different metrics may give different rank ordering of the same attribute, making comparisons across products difficult and uncertain.

List of Metrics available

Fault Density	Software purity level
Defect density	Estimated number of faults remaining (by seeding)
Cumulative failure profile	Requirements compliance
Fault days number	Test coverage
Functional or modular test coverage	Data or information flow complexity
Cause and effect graphing	Reliability growth function
Requirements traceability	Residual fault count
Defect indices	Failure analysis elapsed time
Error distribution (s)	Testing sufficiently
Software maturity index	Mean time to failure
Person-hours per major defect detected	Failure rate
Number of conflicting requirements	Software documentation and source listing
Software science measures	Software release readiness
Graph-theoretic complexity	Completeness
Cyclomatic Complexity	Test accuracy
Minimal unit test case determination	System performance reliability
Run reliability	Independent process reliability
Design structure	Combined hardware and software (system) availability
Mean time to discover the next K-faults

What makes good Metrics?

This is a very interesting question. Many people say that anything we do should be quantitative. Yes, that's absolutely correct. Working in a project, there should be certain measurement criteria for measuring the skills and productivity of every individual in the team. Metrics play an important role in giving a good analysis. Every organization should make a list of metrics applicable in the organization and each employee should be aware of it.

Now let us look at few attributes, which make up good metrics:

The metric should be simple and computable so that its easy and straight forward.
The metric should be measuring the correct attribute.
The metric results should be reproducible.
The metric should be consistent in units or dimensions.
The metric should be independent of programming language.
The metric should provide good and meaningful analysis.

what can be measured with Metrics?

Metrics can measure anything which is quantifiable, like:

Effort, time and expenditure in each stage of the project.
Number of functionalities implemented.
Number of errors reported.
Types of errors reported.
Project schedules.
Benchmark important milestones in the project.

Your Ad Here

Requirement Gathering Template

noreply@blogger.com (S.U.Sankar) — Mon, 20 Jul 2009 05:09:00 PDT

Requirement Gathering Template

Download Here

ASP.Net Tutorial Free Ebook

noreply@blogger.com (S.U.Sankar) — Sun, 19 Jul 2009 22:03:00 PDT

ASP.Net Tutorial Free Ebook Download

It is Good ASP.Net end-to-end tutorial that walks-through building a small, but complete, ASP.NET MVC application from scratch.

Download

Defect Tracking Template

noreply@blogger.com (S.U.Sankar) — Wed, 15 Jul 2009 04:27:00 PDT

Download

Enhanced Defect Tracking Template

Test Data For Time Field

noreply@blogger.com (S.U.Sankar) — Wed, 15 Jul 2009 04:25:00 PDT

00:00:00
00:00:01
01:01:01
11:59:59
12:00:00
12:01:01
23:59:59
(now)
(1 second ago)
(1 second from now)
(1 minute ago)
(1 mnute from now)
(1 hour ago)
(1 hour from now)
25:01:01
01:60:01
01:60:01
01:01:60
01:01:61
01::01
01::
01:01:xx
01:xx:01
xx:01:01

Test Data For Date Fields

noreply@blogger.com (S.U.Sankar) — Wed, 15 Jul 2009 04:23:00 PDT

0/0/0000
(yesterday)
(today)
(today with all leading zeros, like 01/01/2006)
(tomorrow)
(same day last week)
(same day next week)
(same day last month)
(same day next month)
(same day last year)
(same day next year)
(Jan 1 this year)
(Dec 31 this year)
(Jan 1 last year)
(Dec 31 last year)
(Jan 1 next year)
(Dec 31 next year)
1/1/1999
12/31/1999
1/1/2000
2/28/2000
2/29/2000
2/30/2000
2/31/2000
3/1/2000
12/31/2000
1/1/2001
1/1/202
2/28/2004
2/29/2004
3/1/2004
12/31/2004
9/9/9999
2/29/2001
4/31/2001
9/31/2001
2/29/2100
13/1/2006
00/1/2006
01/32/2006
01/00/2006
June 5, 2001
06/05/2001
6/5/2001
06/05/01
6/5/01
06-05-01
06-05-2001
6-5-01
6-5-2001

Test Steps for Check Box Field

noreply@blogger.com (S.U.Sankar) — Wed, 15 Jul 2009 04:20:00 PDT

Checked
Unchecked

Test Steps for Radio Button Field

noreply@blogger.com (S.U.Sankar) — Wed, 15 Jul 2009 04:16:00 PDT

On
Off
All buttons in a group Off
One button in a group On
More than one button in a group On
One button in a group Off
All buttons in a group On

Test Steps for List Box

noreply@blogger.com (S.U.Sankar) — Wed, 15 Jul 2009 04:14:00 PDT

None selected
Top item selected
Second item selected
Middle item selected
Next to bottom item selected
Bottom item selected
Top and bottom items selected
Several adjoining items selected
Several non-adjoining items selected
All items selected
All items except the top item selected
All items except the bottom item selected
All items except one middle item selected

Test Input Data for an Integer Field

noreply@blogger.com (S.U.Sankar) — Wed, 15 Jul 2009 04:13:00 PDT

Nothing
Empty field (clear any defaults)
More than the maximum number of digits or characters
0
Any valid value
Minimum - 1
Minimum
Maximum
Maximum + 1
Much less than the Minimum
Much more than the Maximum
Minimum number of digits or characters
Minimum - 1 number of digits or characters
Maximum number of digits or characters
Maximum + 1 number of digits or characters
Much more than the Maximum number of digits or characters
A negative value
Nondigits, expecially / (ASCII character 47) and : (ASCII character 58)
Wrong data type (e.g., decimal into integer)
Expressions
A single leading space
Many leading spaces
A single trailing space
Many trailing spaces
Lead and trailing spaces
Leading 0
Many leading zeros
Leading + sign
Many leading + signs
Nonprinting character (e.g., Ctrl+char)
Operating system filename reserved characters (e.g., "*.:")
Language-specific reserved characters
Upper ASCII (128-254) (a.k.a. ANSI) characters
ASCII 255 (often interpreted as end of file)
Uppercase characters
Lowercase characters
Modifiers (e.g., Ctrl, Alt, Shift-Ctrl, and so on)
Function key (F2, F3, F5, and so on)
254
255 (1-byte, tinyint)
256
32766
32767 (2-byte, smallint)
32768
65534
65535 (2-byte unsigned, smallint)
65536
2147483646
2147483647 (4 byte, int)
2147483648
4294967294
4294967295 (4-byte unsigned, int)
4294967296
9223372036854775806
9223372036854775807 (8 byte, bigint)
9223372036854775808
18446744073709551614
18446744073709551615 (8 byte unsigned, bigint)
18446744073709551616

The First Bug Report

noreply@blogger.com (S.U.Sankar) — Wed, 15 Jul 2009 04:03:00 PDT

Test Data – For Unit validation

noreply@blogger.com (S.U.Sankar) — Wed, 15 Jul 2009 03:55:00 PDT

Alphabhatic Characters

abcdefghijklmnopqrstuvwxyz

ABCDEFGHIJKLMNOPQRSTUVWXYZ

Special Characters

~!@#$%^&*()_+{}|:"<>?`-=[];',./

10 Characters
1234567890

123456789+

1234567.89

12345.6789

$123456.78

$12,345.67

12,345,678

123,456.78

abcdefghi+

abcdefghiX

ABCDEFGHI+

ABCDEFGHIx

WWWWWWWWWZ

~!@#$%^&*X

100 Characters
123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789+

1234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890

123456789+123456789+123456789+123456789+123456789+123456789+123456789+123456789+123456789+123456789+

abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstu+

abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuZ

ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEFGHIJKLMNOPQRSTUVWXYZABCDEFGHIJKLMNOPQRSTUVWXYZABCDEF

GHIJKLMNOPQRSTU+

ABCDEFGHIJKLMNOPQRSTUVWXYZABCDEFGHIJKLMNOPQRSTUVWXYZABCDEFGHIJKLMNOPQRSTUVWXYZABCDEF

GHIJKLMNOPQRSTUz

WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWW

WWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWWZ

~!@#$%^&*()_+{}|:"<>?`-=[];',./~!@#$%^&*()_+{}|:"<>?`-=[];',./~!@#$%^&*()_+{}|:"<>?`-=[];',./~!@#$%X

Test Data Country Codes

noreply@blogger.com (S.U.Sankar) — Thu, 09 Jul 2009 22:41:00 PDT

Country names	2 Digit Code	Country names	2 Digit Code
A		M
AFGHANISTAN	AF	MACAO	MO
ÅLAND ISLANDS	AX	MACEDONIA, THE FORMER YUGOSLAV REPUBLIC OF	MK
ALBANIA	AL	MADAGASCAR	MG
ALGERIA	DZ	MALAWI	MW
AMERICAN SAMOA	AS	MALAYSIA	MY
ANDORRA	AD	MALDIVES	MV
ANGOLA	AO	MALI	ML
ANGUILLA	AI	MALTA	MT
ANTARCTICA	AQ	MARSHALL ISLANDS	MH
ANTIGUA AND BARBUDA	AG	MARTINIQUE	MQ
ARGENTINA	AR	MAURITANIA	MR
ARMENIA	AM	MAURITIUS	MU
ARUBA	AW	MAYOTTE	YT
AUSTRALIA	AU	MEXICO	MX
AUSTRIA	AT	MICRONESIA, FEDERATED STATES OF	FM
AZERBAIJAN	AZ	MOLDOVA, REPUBLIC OF	MD
B		MONACO	MC
BAHAMAS	BS	MONGOLIA	MN
BAHRAIN	BH	MONTENEGRO	ME
BANGLADESH	BD	MONTSERRAT	MS
BARBADOS	BB	MOROCCO	MA
BELARUS	BY	MOZAMBIQUE	MZ
BELGIUM	BE	MYANMAR	MM
BELIZE	BZ	N
BENIN	BJ	NAMIBIA	NA
BERMUDA	BM	NAURU	NR
BHUTAN	BT	NEPAL	NP
BOLIVIA, PLURINATIONAL STATE OF	BO	NETHERLANDS	NL
BOSNIA AND HERZEGOVINA	BA	NETHERLANDS ANTILLES	AN
BOTSWANA	BW	NEW CALEDONIA	NC
BOUVET ISLAND	BV	NEW ZEALAND	NZ
BRAZIL	BR	NICARAGUA	NI
BRITISH INDIAN OCEAN TERRITORY	IO	NIGER	NE
BRUNEI DARUSSALAM	BN	NIGERIA	NG
BULGARIA	BG	NIUE	NU
BURKINA FASO	BF	NORFOLK ISLAND	NF
BURUNDI	BI	NORTHERN MARIANA ISLANDS	MP
C		NORWAY	NO
CAMBODIA	KH	O
CAMEROON	CM	OMAN	OM
CANADA	CA	P
CAPE VERDE	CV	PAKISTAN	PK
CAYMAN ISLANDS	KY	PALAU	PW
CENTRAL AFRICAN REPUBLIC	CF	PALESTINIAN TERRITORY, OCCUPIED	PS
CHAD	TD	PANAMA	PA
CHILE	CL	PAPUA NEW GUINEA	PG
CHINA	CN	PARAGUAY	PY
CHRISTMAS ISLAND	CX	PERU	PE
COCOS (KEELING) ISLANDS	CC	PHILIPPINES	PH
COLOMBIA	CO	PITCAIRN	PN
COMOROS	KM	POLAND	PL
CONGO	CG	PORTUGAL	PT
CONGO, THE DEMOCRATIC REPUBLIC OF THE	CD	PUERTO RICO	PR
COOK ISLANDS	CK	Q
COSTA RICA	CR	QATAR	QA
CÔTE D'IVOIRE	CI	R
CROATIA	HR	RÉUNION	RE
CUBA	CU	ROMANIA	RO
CYPRUS	CY	RUSSIAN FEDERATION	RU
CZECH REPUBLIC	CZ	RWANDA	RW
D		S
DENMARK	DK	SAINT BARTHÉLEMY	BL
DJIBOUTI	DJ	SAINT HELENA	SH
DOMINICA	DM	SAINT KITTS AND NEVIS	KN
DOMINICAN REPUBLIC	DO	SAINT LUCIA	LC
E		SAINT MARTIN	MF
ECUADOR	EC	SAINT PIERRE AND MIQUELON	PM
EGYPT	EG	SAINT VINCENT AND THE GRENADINES	VC
EL SALVADOR	SV	SAMOA	WS
EQUATORIAL GUINEA	GQ	SAN MARINO	SM
ERITREA	ER	SAO TOME AND PRINCIPE	ST
ESTONIA	EE	SAUDI ARABIA	SA
ETHIOPIA	ET	SENEGAL	SN
F		SERBIA	RS
FALKLAND ISLANDS (MALVINAS)	FK	SEYCHELLES	SC
FAROE ISLANDS	FO	SIERRA LEONE	SL
FIJI	FJ	SINGAPORE	SG
FINLAND	FI	SLOVAKIA	SK
FRANCE	FR	SLOVENIA	SI
FRENCH GUIANA	GF	SOLOMON ISLANDS	SB
FRENCH POLYNESIA	PF	SOMALIA	SO
FRENCH SOUTHERN TERRITORIES	TF	SOUTH AFRICA	ZA
G		SOUTH GEORGIA AND THE SOUTH SANDWICH ISLANDS	GS
GABON	GA	SPAIN	ES
GAMBIA	GM	SRI LANKA	LK
GEORGIA	GE	SUDAN	SD
GERMANY	DE	SURINAME	SR
GHANA	GH	SVALBARD AND JAN MAYEN	SJ
GIBRALTAR	GI	SWAZILAND	SZ
GREECE	GR	SWEDEN	SE
GREENLAND	GL	SWITZERLAND	CH
GRENADA	GD	SYRIAN ARAB REPUBLIC	SY
GUADELOUPE	GP	T
GUAM	GU	TAIWAN, PROVINCE OF CHINA	TW
GUATEMALA	GT	TAJIKISTAN	TJ
GUERNSEY	GG	TANZANIA, UNITED REPUBLIC OF	TZ
GUINEA	GN	THAILAND	TH
GUINEA-BISSAU	GW	TIMOR-LESTE	TL
GUYANA	GY	TOGO	TG
H		TOKELAU	TK
HAITI	HT	TONGA	TO
HEARD ISLAND AND MCDONALD ISLANDS	HM	TRINIDAD AND TOBAGO	TT
HOLY SEE (VATICAN CITY STATE)	VA	TUNISIA	TN
HONDURAS	HN	TURKEY	TR
HONG KONG	HK	TURKMENISTAN	TM
HUNGARY	HU	TURKS AND CAICOS ISLANDS	TC
I		TUVALU	TV
ICELAND	IS	U
INDIA	IN	UGANDA	UG
INDONESIA	ID	UKRAINE	UA
IRAN, ISLAMIC REPUBLIC OF	IR	UNITED ARAB EMIRATES	AE
IRAQ	IQ	UNITED KINGDOM	GB
IRELAND	IE	UNITED STATES	US
ISLE OF MAN	IM	UNITED STATES MINOR OUTLYING ISLANDS	UM
ISRAEL	IL	URUGUAY	UY
ITALY	IT	UZBEKISTAN	UZ
J		V
JAMAICA	JM	VANUATU	VU
JAPAN	JP	VATICAN CITY STATE	VA
JERSEY	JE	VENEZUELA, BOLIVARIAN REPUBLIC OF	VE
JORDAN	JO	VIET NAM	VN
K		VIRGIN ISLANDS, BRITISH	VG
KAZAKHSTAN	KZ	VIRGIN ISLANDS, U.S.	VI
KENYA	KE	W
KIRIBATI	KI	WALLIS AND FUTUNA	WF
KOREA, DEMOCRATIC PEOPLE'S REPUBLIC OF	KP	WESTERN SAHARA	EH
KOREA, REPUBLIC OF	KR	Y
KUWAIT	KW	YEMEN	YE
KYRGYZSTAN	KG	Z
L		ZAMBIA	ZM
LAO PEOPLE'S DEMOCRATIC REPUBLIC	LA	ZIMBABWE	ZW
LATVIA	LV
LEBANON	LB
LESOTHO	LS
LIBERIA	LR
LIBYAN ARAB JAMAHIRIYA	LY
LIECHTENSTEIN	LI
LITHUANIA	LT
LUXEMBOURG	LU

Test Data Countries List

noreply@blogger.com (S.U.Sankar) — Wed, 08 Jul 2009 00:09:00 PDT

S.No	English Name	Local Name

A
1	Afghanistan	Afghanestan
2	Albania	Shqiperia
3	Algeria	Al Jaza'ir
4	American Samoa	American Samoa
5	Andorra	Andorra
6	Angola	Angola
7	Anguilla	Anguilla
8	Antarctica	Antarctica
9	Antigua and Barbuda	Antigua and Barbuda
10	Argentina	Argentina
11	Armenia	Hayastan
12	Aruba	Aruba
13	Ascension Island	Ascension
14	Australia	Australia
15	Austria	Österreich
16	Azerbaijan	Azarbaycan

B
17	Bahamas	Bahamas
18	Bahrain	Al Bahrayn
19	Bangladesh	Bangladesh
20	Barbados	Barbados
21	Belarus	Byelarus
22	Belgium	Belgique/Belgie
23	Belize	Belize
24	Benin	Benin
25	Bermuda	Bermuda
26	Bhutan	Bhutan
27	Bolivia	Bolivia
28	Bosnia and Herzegovina	Bosna i Hercegovina
29	Botswana	Botswana
30	Bouvet Island	Bouvet Island
31	Brazil	Brasil
32	British Indian Ocean Territory	abbreviation: BIOT
33	Brunei Darussalam	Negara Brunei Darussalam
34	Bulgaria	Bulgaria
35	Burkina Faso	Burkina Faso
36	Burundi	Burundi

C
37	Cambodia	Kampuchea
38	Cameroon	Cameroon
39	Canada	Canada
40	Cape Verde	Cabo Verde
41	Cayman Islands	Cayman Islands
42	Central African Republic	Republique Centrafricaine
43	Chad	Tchad
44	Chile	Chile
45	China	Zhong Guo
46	Christmas Island	Christmas Island
47	Cocos (Keeling) Islands	Cocos (Keeling) Islands
48	Colombia	Colombia
49	Comoros	Comores
50	Democratic Republic of the Congo(Kinshasa)	République Démocratique du Congo
51	Congo, Republic of (Brazzaville)	République du Congo
52	Cook Islands	Cook Islands
53	Costa Rica	Costa Rica
54	Ivory Coast	Cote d'Ivoire
55	Croatia	Hrvatska
56	Cuba	Cuba
57	Cyprus	Kibris, Kypros
58	Czech Republic	Ceska Republika

D
59	Denmark	Danmark
60	Djibouti	Djibouti
61	Dominica	Dominica
62	Dominican Republic	Dominicana, Republica

E
63	East Timor Timor-Leste	Timor
64	Ecuador	Ecuador
65	Egypt	Misr
67	El Salvador	El Salvador
68	Equatorial Guinea	Guinea Ecuatorial
69	Eritrea	Hagere Ertra
70	Estonia	Eesti Vabariik
71	Ethiopia	Ityop'iya

F
72	Falkland Islands	Islas Malvinas
73	Faroe Islands	Foroyar
74	Fiji	Fiji
75	Finland	Suomen Tasavalta
76	France	France
77	French Guiana	Guyane
78	French Metropolitan	France Métropolitaine
79	French Polynesia	Polynésie Française
80	French Southern Territories	Terres Australes et Antarctiques Françaises

G
81	Gabon	Gabon
82	Gambia	The Gambia
83	Georgia	Sak'art'velo
84	Germany	Deutschland
85	Ghana	Ghana
86	Gibraltar	Gibraltar
87	Great Britain	Great Britain
88	Greece	Ellas or Ellada
89	Greenland	Kalaallit Nunaat
90	Grenada	Grenada
91	Guadeloupe	Guadeloupe
92	Guam	Guam
93	Guatemala	Guatemala
94	Guernsey	Guernsey
95	Guinea	Guinee
96	Guinea-Bissau	Guine-Bissau
97	Guyana	Guyana

H
98	Haiti	Haiti
99	Heard and Mc Donald Islands	Heard and Mc Donald
100	Holy See	Status Civitatis Vaticanæ
101	Honduras	Honduras
102	Hong Kong	Xianggang
103	Hungary	Magyarorszag

I
104	Iceland	Lyoveldio Island
105	India	Bharat
106	Indonesia	Indonesia
107	Iran (Islamic Republic of)	Iran
108	Iraq	Iraq
109	Ireland	Éire
110	Isle of Man	Isle of Man
111	Israel	Yisra'el
112	Italy	Italia

J
113	Jamaica	Jamaica
114	Japan	Nippon
115	Jersey	Jersey
116	Jordan	Al Urdun

K
117	Kazakhstan	Qazaqstan
118	Kenya	Kenya
119	Kiribati	Kiribati, Kiribas
120	Korea, Democratic People's Rep. (North Korea)	Choson
121	Korea, Republic of (South Korea)	Han-guk
122	Kuwait	Al Kuwayt
123	Kyrgyzstan	Kyrgyz Respublikasy

L
124	Lao, People's Democratic Republic	Lao
125	Latvia	Latvija
126	Lebanon	Lubnan
127	Lesotho	Lesotho
128	Liberia	Liberia
129	Libya	Libiyah
130	Liechtenstein	Liechtenstein
131	Lithuania	Lietuva
132	Luxembourg	Luxembourg, Letzebuerg

M
133	Macau	Aomen
134	Macedonia, Rep. of	Makedonija
135	Madagascar	Madagascar
136	Malawi	Malawi
137	Malaysia	Malaysia
138	Maldives	Dhivehi Raajje
139	Mali	Mali
140	Malta	Malta
141	Marshall Islands	Marshall Islands
142	Martinique	Martinique
143	Mauritania	Muritaniyah
144	Mauritius	Mauritius
145	Mayotte	Mayotte
146	Mexico	Estados Unidos Mexicanos
147	Micronesia, Federal States of	Micronesia
148	Moldova, Republic of	Moldova
149	Monaco	Monaco
150	Mongolia	Mongol Uls
151	Montenegro	Crna Gora
152	Montserrat	Montserrat
153	Morocco	Al Maghrib
154	Mozambique	Mocambique
155	Myanmar, Burma	Myanma Naingngandaw

N
156	Namibia	Namibia
157	Nauru	Nauru
158	Nepal	Nepal
159	Netherlands	Nederland/Holland
160	Netherlands Antilles	Nederlandse Antillen
161	New Caledonia	Nouvelle-Calédonie
162	New Zealand	Aotearoa
163	Nicaragua	Nicaragua
164	Niger	Niger
165	Nigeria	Nigeria
166	Niue	Niue
167	Norfolk Island	Norfolk Island
168	Northern Mariana Islands	Northern Mariana Islands
169	Norway	Norge

O
170	Oman	Saltanat Uman

P
171	Pakistan	Pakistan
172	Palau	Belau
173	Palestinian National Authority	Filastin
174	Panama	Panama
175	Papua New Guinea	Papua Niu Gini
176	Paraguay	Paraguay
177	Peru	Peru
178	Philippines	Pilipinas
179	Pitcairn Island	Pitcairn Island
180	Poland	Polska
181	Portugal	Portugal
182	Puerto Rico	Puerto Rico

Q
183	Qatar	Dawlat Qatar

R
184	Reunion Island	Ile de la Réunion
185	Romania	Romania
186	Russian Federation	Rossiya
187	Rwanda	Rwanda

S
188	Saint Kitts and Nevis
189	Saint Lucia	Saint Lucia
190	Saint Vincent and the Grenadines
191	Samoa	Samoa
192	San Marino	San Marino
193	Sao Tome and Príncipe	Sao Tome e Principe
194	Saudi Arabia	Al Arabiyah as Suudiyah
195	Senegal	Senegal
196	Serbia	Srbija
197	Seychelles	Seychelles
198	Sierra Leone	Sierra Leone
199	Singapore	Singapore
200	Slovakia (Slovak Republic)	Slovensko
201	Slovenia	Slovenija
202	Solomon Islands	Solomon Islands
203	Somalia	Somalia
204	South Africa	South Africa
205	South Georgia and South Sandwich Islands
206	Spain	España
207	Sri Lanka	Sri Lanka
208	Saint Helena	Saint Helena
209	St. Pierre and Miquelon	Saint-Pierre et Miquelon
210	Sudan	As-Sudan
211	Suriname	Suriname
212	Svalbard and Jan Mayen Islands	Spitzbergen
213	Swaziland	Swaziland
214	Sweden	Sverige
215	Switzerland	Schweiz (German), Suisse (French), Svizzera (Italian)
216	Syria, Syrian Arab Republic	Suriyah

T
217	Taiwan (Republic of China)	T'ai-wan
218	Tajikistan	Jumhurii Tojikiston
219	Tanzania	Tanzania
220	Thailand	Prathet Thai
221	Tibet	Bod
222	Timor-Leste (East Timor)	Timor
223	Togo	Republique Togolaise
224	Tokelau	Tokelau
225	Tonga	Tonga
226	Trinidad and Tobago	Trinidad, Tobago
227	Tunisia	Tunis
228	Turkey	Turkiye
229	Turkmenistan	Turkmenistan
230	Turks and Caicos Islands	Turks and Caicos Islands
231	Tuvalu	Tuvalu

U
232	Uganda	Uganda
233	Ukraine	Ukrayina
234	United Arab Emirates	Al Imarat al Arabiyah al Muttahidah
235	United Kingdom	United Kingdom
236	United States	United States
237	U.S. Minor Outlying Islands	U.S. Minor Outlying Islands
238	Uruguay	Republica Oriental del Uruguay
239	Uzbekistan	Uzbekiston Respublikasi

V
240	Vanuatu	Vanuatu
--	Vatican City State (Holy See)	Status Civitatis Vaticanæ
241	Venezuela	Venezuela
242	Vietnam	Viet Nam
243	Virgin Islands (British)
244	Virgin Islands (U.S.)	Virgin Islands

W
245	Wallis and Futuna Islands	Wallis et Futuna
246	Western Sahara

Y
247	Yemen	Al Yaman

Z
--	Zaire (see Congo, Democratic People's Republic)	Zaire
248	Zambia	Zambia
249	Zimbabwe	Zimbabwe

Test Data For Credit Cards Validation

noreply@blogger.com (S.U.Sankar) — Wed, 08 Jul 2009 00:03:00 PDT

Test Data - Credit Card Numbers
American Express	Discover Card	MasterCard	Visa
American Express numbers start with 34 or 37 and are 15 digits long	Discover Card number start with 6011 or 650 and are 16 digits long	MasterCard numbers start with 51-55 and are 16 digits long	Visa numbers start with 4 and are 13 or 16 digits long
340000000000009 341111111111111 370000000000002 371449635398431 372425119311008 378282246310005 378734493671000	6011000000000004 6011000000000012 6011000990139424 6011111111111117 6011601160116611	5105105105105100 5276440065421319 5424000000000015 5431111111111111 5500000000000004 5555555555554444	4007000000027 4012888818888 4222222222222 4012888888881881 4111111111111111

Also see:

http://www.darkcoding.net/credit-card-numbers/

http://en.wikipedia.org/wiki/Luhn_algorithm

http://en.wikipedia.org/wiki/Credit_card_number

Major Bugs with Most Notable Consequences

noreply@blogger.com (Hakkimabdula) — Mon, 29 Jun 2009 02:31:00 PDT

Space exploration
A booster went off course during launch, resulting in the destruction of NASA Mariner 1. This was the result of the failure of a transcriber to notice an overbar in a written specification for the guidance program, resulting in the coding of an incorrect formula in its FORTRAN software. (July 22, 1962).
The Russian Space Research Institute's Phobos 1 deactivated its attitude thrusters and could no longer properly orient its solar arrays or communicate with Earth, eventually depleting its batteries. (September 10, 1988).
The European Space Agency's Ariane 5 Flight 501 was destroyed 40 seconds after takeoff (June 4, 1996). The US$1 billion prototype rocket self-destructed due to a bug in the on-board guidance software.
NASA Mars Polar Lander was destroyed because its flight software mistook vibrations due to atmospheric turbulance for evidence that the vehicle had landed and shut off the engines 40 meters from the Martian surface (December 3, 1999). Its sister spacecraft Mars Climate Orbiter was also destroyed, but due to human error and not, as is sometimes reported, due to a software bug.
A mis-sent command from Earth caused the software of the NASA Mars Global Surveyor to incorrectly assume that a motor had failed, causing it to point one of its batteries at the sun - subsequently overheating it. (November 2, 2006).

Medical
A bug in the code controlling the Therac-25 radiation therapy machine was directly responsible for at least five patient deaths in the 1980s when it administered excessive quantities of X-rays.
A Medtronic heart device was found vulnerable to remote attacks in March 2008

Computing
The year 2000 problem spawned fears of worldwide economic collapse and an industry of consultants providing last-minute fixes.[13] In addition, it is possible the problem could recur in 2038 (the year 2038 problem), as many Unix systems calculate the time in seconds since 1 January 1970, and store this figure as a 32-bit signed integer, for which the maximum possible value is 231 (2,147,483,648).

Electric power transmission
The 2003 North America blackout was triggered by a local outage that went undetected due to a race condition in General Electric Energy's XA/21 monitoring software.

Telecommunications•
AT&T long distance network crash (January 15, 1990), in which the failure of one switching system would cause a message to be sent to nearby switching units to tell them that there was a problem. Unfortunately, the arrival of that message would cause those other systems to fail too - resulting in a 'wave' of failure that rapidly spread across the entire AT&T long distance network.
In January 2009, Google's search engine erroneously notified users that every web site world wide was potentially malicious.

Military
The software error of a MIM-104 Patriot, caused its system clock to drift by one third of a second - resulting in failure to locate and intercept an incoming missile. The scud impacted in a military compound in Dhahran, Saudi Arabia (February 25, 1991), killing 28 Americans.
A Chinook crash on Mull of Kintyre in June 1994. A Royal Air Force Chinook helicopter crashed into the Mull of Kintyre, killing 29. This was initially dismissed as pilot error, but an investigation by Computer Weekly uncovered sufficient evidence to convince a House of Lords inquiry that it may have been caused by a software bug in the aircraft's engine control computer.
Smart ship USS Yorktown was left dead in the water in 1998 for nearly 3 hours after a divide by zero error.
A software glitch in a South African antiaircraft cannon had killed 9 soldiers and seriously injured 14 others in 2007 during a shooting exercise.

Media
Eve Online's deployment of the Trinity patch, which erased the boot.ini file from several thousand users' computers, rendering them unable to boot. This was due to the usage of a legacy system within the game that was also named boot.ini. As such, the deletion had targeted the wrong directory instead of the /eve directory.
In the Sony BMG CD copy prevention scandal (October 2005), Sony BMG produced a Van Zant music CD that employed a copy protection scheme that covertly installed a "rootkit" on any Windows PC that was used to play it. Their intent was to hide the copy protection mechanism to make it harder to circumvent. Unfortunately, the rootkit inadvertently opened a security hole resulting in a wave of successful trojan horse attacks on the computers of those who had innocently played the CD. Sony's subsequent efforts to provide a utility to fix the problem actually exacerbated it.

Encryption
In order to fix a warning issued by Valgrind, a maintainer of Debian patched OpenSSL and broke the random number generator in the process. The patch was uploaded in September 2006 and made its way into the official release; it was not reported until April 2008. Every key generated with the broken version is compromised, as is all data encrypted with it, threatening many applications that rely on encryption such as S/MIME, TOR, SSL or TLS protected connections and SSH.

GUI Testing Checklist

noreply@blogger.com (S.U.Sankar) — Mon, 08 Jun 2009 03:15:00 PDT

GUI Testing Checklist
A checklist to help testers check GUI screens
CONTENTS:
Section 1 - Windows Compliance Standards
1.1. Application
1.2. For Each Window in the Application
1.3. Text Boxes
1.4. Option (Radio Buttons)
1.5. Check Boxes
1.6. Command Buttons
1.7. Drop Down List Boxes
1.8. Combo Boxes
1.9. List Boxes
Section 2 - Tester's Screen Validation Checklist
2.1. Aesthetic Conditions
2.2. Validation Conditions
2.3. Navigation Conditions
2.4. Usability Conditions
2.5. Data Integrity Conditions
2.6. Modes (Editable Read-only) Conditions
2.7. General Conditions
2.8. Specific Field Tests
       2.8.1. Date Field Checks
       2.8.2. Numeric Fields
       2.8.3. Alpha Field Checks
Section 3 - Validation Testing - Standard Actions
3.1. On every Screen
3.2. Shortcut keys / Hot Keys
3.3. Control Shortcut Keys
Section 4 - Origin & Inspiration
4.1. Document origin
4.2. Sources of Inspiration & information
4.3. Contacting the author.
Section 1 - Windows Compliance Testing
1.1. Application
Start Application by Double Clicking on its ICON. The Loading message should show the application name,
version number, and a bigger pictorial representation of the icon (a 'splash' screen).
No Login is necessary
The main window of the application should have the same caption as the caption of the icon in Program Manager.
Closing the application should result in an "Are you Sure" message box
Attempt to start application Twice
This should not be allowed - you should be returned to main Window
Try to start the application twice as it is loading.
On each window, if the application is busy, then the hour glass should be displayed. If there is no hour glass
(e.g. alpha access enquiries) then some enquiry in progress message should be displayed.
All screens should have a Help button, F1 should work doing the same.


1.2. For Each Window in the Application
If Window has a Minimise Button, click it.
Window Should return to an icon on the bottom of the screen
This icon should correspond to the Original Icon under Program Manager.
Double Click the Icon to return the Window to its original size.
The window caption for every application should have the name of the application and the window name -
especially the error messages. These should be checked for spelling, English and clarity , especially on the top
of the screen. Check does the title of the window makes sense.
If the screen has an Control menu, then use all ungreyed options.
Check all text on window for Spelling/Tense and Grammar
Use TAB to move focus around the Window. Use SHIFT+TAB to move focus backwards.
Tab order should be left to right, and Up to Down within a group box on the screen. All controls
should get focus - indicated by dotted box, or cursor. Tabbing to an entry field with text in it should highlight
the entire text in the field.
The text in the Micro Help line should change - Check for spelling, clarity and non-updateable etc.
If a field is disabled (greyed) then it should not get focus. It should not be possible to select them with either
the mouse or by using TAB. Try this for every greyed control.
Never updateable fields should be displayed with black text on a grey background with a black label.
All text should be left-justified, followed by a colon tight to it.
In a field that may or may not be updateable, the label text and contents changes from black to grey depending
on the current status.
List boxes are always white background with black text whether they are disabled or not. All others are grey.
In general, do not use goto screens, use gosub, i.e. if a button causes another screen to be displayed, the
screen should not hide the first screen, with the exception of tab in 2.0
When returning return to the first screen cleanly i.e. no other screens/applications should appear.
In general, double-clicking is not essential. In general, everything can be done using both the mouse and
the keyboard.
All tab buttons should have a distinct letter.


1.3. Text Boxes
Move the Mouse Cursor over all Enterable Text Boxes. Cursor should change from arrow to Insert Bar.
If it doesn't then the text in the box should be grey or non-updateable. Refer to previous page.
Enter text into Box
Try to overflow the text by typing to many characters - should be stopped Check the field width with capitals W.
Enter invalid characters - Letters in amount fields, try strange characters like + , - * etc. in All fields.
SHIFT and Arrow should Select Characters. Selection should also be possible with mouse. Double Click should
select all text in box.

1.4. Option (Radio Buttons)
Left and Right arrows should move 'ON' Selection. So should Up and Down.. Select with mouse by clicking.

1.5. Check Boxes
Clicking with the mouse on the box, or on the text should SET/UNSET the box. SPACE should do the same.

1.6. Command Buttons
If Command Button leads to another Screen, and if the user can enter or change details on the other screen then
the Text on the button should be followed by three dots.
All Buttons except for OK and Cancel should have a letter Access to them. This is indicated by a letter underlined
in the button text. The button should be activated by pressing ALT+Letter. Make sure there is no duplication.
Click each button once with the mouse - This should activate
Tab to each button - Press SPACE - This should activate
Tab to each button - Press RETURN - This should activate
The above are VERY IMPORTANT, and should be done for EVERY command Button.
Tab to another type of control (not a command button). One button on the screen should be default (indicated by
a thick black border). Pressing Return in ANY no command button control should activate it.
If there is a Cancel Button on the screen , then pressing should activate it.
If pressing the Command button results in uncorrectable data e.g. closing an action step, there should be a message
phrased positively with Yes/No answers where Yes results in the completion of the action.

1.7. Drop Down List Boxes
Pressing the Arrow should give list of options. This List may be scrollable. You should not be able to type text
in the box.
Pressing a letter should bring you to the first item in the list with that start with that letter. Pressing ‘Ctrl - F4’
should open/drop down the list box.
Spacing should be compatible with the existing windows spacing (word etc.). Items should be in alphabetical
order with the exception of blank/none which is at the top or the bottom of the list box.
Drop down with the item selected should be display the list with the selected item on the top.
Make sure only one space appears, shouldn't have a blank line at the bottom.

1.8. Combo Boxes
Should allow text to be entered. Clicking Arrow should allow user to choose from list

1.9. List Boxes
Should allow a single selection to be chosen, by clicking with the mouse, or using the Up and Down Arrow keys.
Pressing a letter should take you to the first item in the list starting with that letter.
If there is a 'View' or 'Open' button beside the list box then double clicking on a line in the List Box, should act in the same way as selecting and item in the list box, then clicking the command button.
Force the scroll bar to appear, make sure all the data can be seen in the box.

Section 2 - Screen Validation Checklist

2.1. Aesthetic Conditions:
Is the general screen background the correct colour?
Are the field prompts the correct colour?
Are the field backgrounds the correct colour?
In read-only mode, are the field prompts the correct colour?
In read-only mode, are the field backgrounds the correct colour?
Are all the screen prompts specified in the correct screen font?
Is the text in all fields specified in the correct screen font?
Are all the field prompts aligned perfectly on the screen?
Are all the field edit boxes aligned perfectly on the screen?
Are all groupboxes aligned correctly on the screen?
Should the screen be resizable?
Should the screen be minimisable?
Are all the field prompts spelt correctly?
Are all character or alpha-numeric fields left justified? This is the default unless otherwise specified.
Are all numeric fields right justified? This is the default unless otherwise specified.
Is all the microhelp text spelt correctly on this screen?
Is all the error message text spelt correctly on this screen?
Is all user input captured in UPPER case or lower case consistently?
Where the database requires a value (other than null) then this should be defaulted into fields. The

user must either enter an alternative valid value or leave the default value intact.
Assure that all windows have a consistent look and feel.
Assure that all dialog boxes have a consistent look and feel.

2.2. Validation Conditions:
Does a failure of validation on every field cause a sensible user error message?
Is the user required to fix entries which have failed validation tests?
Have any fields got multiple validation rules and if so are all rules being applied?
If the user enters an invalid value and clicks on the OK button (i.e. does not TAB off the field) is the invalid entry identified and highlighted correctly with an error message.?
Is validation consistently applied at screen level unless specifically required at field level?
For all numeric fields check whether negative numbers can and should be able to be entered.
For all numeric fields check the minimum and maximum values and also some mid-range values allowable?
For all character/alphanumeric fields check the field to ensure that there is a character limit specified and that this limit is exactly correct for the specified database size?
Do all mandatory fields require user input?
If any of the database columns don't allow null values then the corresponding screen fields must be mandatory. (If any field which initially was mandatory has become optional then check whether null values are allowed in this field.)

2.3. Navigation Conditions:
Can the screen be accessed correctly from the menu?
Can the screen be accessed correctly from the toolbar?
Can the screen be accessed correctly by double clicking on a list control on the previous screen?
Can all screens accessible via buttons on this screen be accessed correctly?
Can all screens accessible by double clicking on a list control be accessed correctly?
Is the screen modal. i.e. Is the user prevented from accessing other functions when this screen is active and is this correct?
Can a number of instances of this screen be opened at the same time and is this correct?

2.4. Usability Conditions:
Are all the dropdowns on this screen sorted correctly? Alphabetic sorting is the default unless otherwise specified.
Is all date entry required in the correct format?
Have all pushbuttons on the screen been given appropriate Shortcut keys?
Do the Shortcut keys work correctly?
Have the menu options which apply to your screen got fast keys associated and should they have?
Does the Tab Order specified on the screen go in sequence from Top Left to bottom right? This is the default unless otherwise specified.
Are all read-only fields avoided in the TAB sequence?
Are all disabled fields avoided in the TAB sequence?
Can the cursor be placed in the microhelp text box by clicking on the text box with the mouse?
Can the cursor be placed in read-only fields by clicking in the field with the mouse?
Is the cursor positioned in the first input field or control when the screen is opened?
Is there a default button specified on the screen?
Does the default button work correctly?
When an error message occurs does the focus return to the field in error when the user cancels it?
When the user Alt+Tab's to another application does this have any impact on the screen upon return to The application?
Do all the fields edit boxes indicate the number of characters they will hold by there length? e.g. a 30 character field should be a lot longer

2.5. Data Integrity Conditions:
Is the data saved when the window is closed by double clicking on the close box?
Check the maximum field lengths to ensure that there are no truncated characters?
Where the database requires a value (other than null) then this should be defaulted into fields. The user must either enter an alternative valid value or leave the default value intact.
Check maximum and minimum field values for numeric fields?
If numeric fields accept negative values can these be stored correctly on the database and does it make sense for the field to accept negative numbers?
If a set of radio buttons represent a fixed set of values such as A, B and C then what happens if a blank value is retrieved from the database? (In some situations rows can be created on the database by other functions which are not screen based and thus the required initial values can be incorrect.)
If a particular set of data is saved to the database check that each value gets saved fully to the database. i.e. Beware of truncation (of strings) and rounding of numeric values.

2.6. Modes (Editable Read-only) Conditions:
Are the screen and field colours adjusted correctly for read-only mode?
Should a read-only mode be provided for this screen?
Are all fields and controls disabled in read-only mode?
Can the screen be accessed from the previous screen/menu/toolbar in read-only mode?
Can all screens available from this screen be accessed in read-only mode?
Check that no validation is performed in read-only mode.

2.7. General Conditions:
Assure the existence of the "Help" menu.
Assure that the proper commands and options are in each menu.
Assure that all buttons on all tool bars have a corresponding key commands.
Assure that each menu command has an alternative(hot-key) key sequence which will invoke it where appropriate.
In drop down list boxes, ensure that the names are not abbreviations / cut short
In drop down list boxes, assure that the list and each entry in the list can be accessed via appropriate key / hot key combinations.
Ensure that duplicate hot keys do not exist on each screen
Ensure the proper usage of the escape key (which is to undo any changes that have been made) and generates a caution message "Changes will be lost - Continue yes/no"
Assure that the cancel button functions the same as the escape key.
Assure that the Cancel button operates as a Close button when changes have be made that cannot be undone.
Assure that only command buttons which are used by a particular window, or in a particular dialog box, are present. - i.e make sure they don't work on the screen behind the current screen.
When a command button is used sometimes and not at other times, assure that it is grayed out when it should not be used.
Assure that OK and Cancel buttons are grouped separately from other command buttons.
Assure that command button names are not abbreviations.
Assure that all field labels/names are not technical labels, but rather are names meaningful to system users.
Assure that command buttons are all of similar size and shape, and same font & font size.
Assure that each command button can be accessed via a hot key combination.
Assure that command buttons in the same window/dialog box do not have duplicate hot keys.
Assure that each window/dialog box has a clearly marked default value (command button, or other object) which is invoked when the Enter key is pressed - and NOT the Cancel or Close button
Assure that focus is set to an object/button which makes sense according to the function of the window/dialog box.
Assure that all option buttons (and radio buttons) names are not abbreviations.
Assure that option button names are not technical labels, but rather are names meaningful to system users.
If hot keys are used to access option buttons, assure that duplicate hot keys do not exist in the same window/dialog box.
Assure that option box names are not abbreviations.
Assure that option boxes, option buttons, and command buttons are logically grouped together in clearly demarcated areas "Group Box"
Assure that the Tab key sequence which traverses the screens does so in a logical way.
Assure consistency of mouse actions across windows.
Assure that the color red is not used to highlight active objects (many individuals are red-green color blind).
Assure that the user will have control of the desktop with respect to general color and highlighting (the application should not dictate the desktop background characteristics).
Assure that the screen/window does not have a cluttered appearance
Ctrl + F6 opens next tab within tabbed window
Shift + Ctrl + F6 opens previous tab within tabbed window
Tabbing will open next tab within tabbed window if on last field of current tab
Tabbing will go onto the 'Continue' button if on last field of last tab within tabbed window
Tabbing will go onto the next editable field in the window
Banner style & size & display exact same as existing windows
If 8 or less options in a list box, display all options on open of list box - should be no need to scroll
Errors on continue will cause user to be returned to the tab and the focus should be on the field causing the error. (i.e the tab is opened, highlighting the field with the error on it)
Pressing continue while on the first tab of a tabbed window (assuming all fields filled correctly) will not open all the tabs.
On open of tab focus will be on first editable field
All fonts to be the same
Alt+F4 will close the tabbed window and return you to main screen or previous screen (as appropriate), generating "changes will be lost" message if necessary.
Microhelp text for every enabled field & button
Ensure all fields are disabled in read-only mode
Progress messages on load of tabbed screens
Return operates continue
If retrieve on load of tabbed window fails window should not open

2.8. Specific Field Tests

2.8.1. Date Field Checks
Assure that leap years are validated correctly & do not cause errors/miscalculations
Assure that month code 00 and 13 are validated correctly & do not cause errors/miscalculations
Assure that 00 and 13 are reported as errors
Assure that day values 00 and 32 are validated correctly & do not cause errors/miscalculations
Assure that Feb. 28, 29, 30 are validated correctly & do not cause errors/ miscalculations
Assure that Feb. 30 is reported as an error
Assure that century change is validated correctly & does not cause errors/ miscalculations
Assure that out of cycle dates are validated correctly & do not cause errors/miscalculations

2.8.2. Numeric Fields
Assure that lowest and highest values are handled correctly
Assure that invalid values are logged and reported
Assure that valid values are handles by the correct procedure
Assure that numeric fields with a blank in position 1 are processed or reported as an error
Assure that fields with a blank in the last position are processed or reported as an error an error
Assure that both + and - values are correctly processed
Assure that division by zero does not occur
Include value zero in all calculations
Include at least one in-range value
Include maximum and minimum range values
Include out of range values above the maximum and below the minimum
Assure that upper and lower values in ranges are handled correctly

2.8.3. Alpha Field Checks
Use blank and non-blank data
Include lowest and highest values
Include invalid characters & symbols
Include valid characters
Include data items with first position blank
Include data items with last position blank

Section 3 - Validation Testing - Standard Actions
3.1. Examples of Standard Actions - Substitute your specific commands
Add
View
Change
Delete
Continue - (i.e. continue saving changes or additions)
Add
View
Change
Delete
Cancel - (i.e. abandon changes or additions)
Fill each field - Valid data
Fill each field - Invalid data
Different Check Box / Radio Box combinations
Scroll Lists / Drop Down List Boxes
Help
Fill Lists and Scroll
Tab
Tab Sequence
Shift Tab

3.2. Shortcut keys / Hot Keys
Note: The following keys are used in some windows applications, and are included as a guide.

Key No Modifier Shift CTRL ALT
F1 Help Enter Help Mode n\a n\a
F2 n\a n\a n\a n\a
F3 n\a n\a n\a n\a
F4 n\a n\a Close Document / Child window. Close Application.
F5 n\a n\a n\a n\a
F6 n\a n\a n\a n\a
F7 n\a n\a n\a n\a
F8 Toggle extend mode, if supported. Toggle Add mode, if supported. n\a n\a
F9 n\a n\a n\a n\a
F10 Toggle menu bar activation. n\a n\a n\a
F11, F12 n\a n\a n\a n\a
Tab Move to next active/editable field. Move to previous active/editable field. Move to next open Document or Child window. (Adding SHIFT reverses the order of movement). Switch to previously used application. (Holding down the ALT key displays all open applications).
Alt Puts focus on first menu command (e.g. 'File'). n\a n\a n\a

3.3. Control Shortcut Keys

Key Function
CTRL + Z Undo
CTRL + X Cut
CTRL + C Copy
CTRL + V Paste
CTRL + N New
CTRL + O Open
CTRL + P Print
CTRL + S Save
CTRL + B Bold*
CTRL + I Italic*
CTRL + U Underline*
* These shortcuts are suggested for text formatting applications, in the context for
which they make sense. Applications may use other modifiers for these operations.

Key	No Modifier	Shift	CTRL	ALT
F1	Help	Enter Help Mode	n\a	n\a
F2	n\a	n\a	n\a	n\a
F3	n\a	n\a	n\a	n\a
F4	n\a	n\a	Close Document / Child window.	Close Application.
F5	n\a	n\a	n\a	n\a
F6	n\a	n\a	n\a	n\a
F7	n\a	n\a	n\a	n\a
F8	Toggle extend mode, if supported.	Toggle Add mode, if supported.	n\a	n\a
F9	n\a	n\a	n\a	n\a
F10	Toggle menu bar activation.	n\a	n\a	n\a
F11, F12	n\a	n\a	n\a	n\a
Tab	Move to next active/editable field.	Move to previous active/editable field.	Move to next open Document or Child window. (Adding SHIFT reverses the order of movement).	Switch to previously used application. (Holding down the ALT key displays all open applications).
Alt	Puts focus on first menu command (e.g. 'File').	n\a	n\a	n\a

*Key*	*Function*
CTRL + Z	Undo
CTRL + X	Cut
CTRL + C	Copy
CTRL + V	Paste
CTRL + N	New
CTRL + O	Open
CTRL + P	Print
CTRL + S	Save
CTRL + B	Bold*
CTRL + I	Italic*
CTRL + U	Underline*

Art of Testing

Software Testing

Software Metrics

METRICS

Requirement Gathering Template

ASP.Net Tutorial Free Ebook

Defect Tracking Template

Test Data For Time Field

Test Data For Date Fields

Test Steps for Check Box Field

Test Steps for Radio Button Field

Test Steps for List Box

Test Input Data for an Integer Field

The First Bug Report

Test Data – For Unit validation

Test Data Country Codes

Test Data Countries List

Test Data For Credit Cards Validation

Test Data - Credit Card Numbers

Major Bugs with Most Notable Consequences

GUI Testing Checklist

GUI Testing Checklist

A checklist to help testers check GUI screens

CONTENTS:

Section 1 - Windows Compliance Standards

Section 2 - Tester's Screen Validation Checklist

Section 3 - Validation Testing - Standard Actions

Section 4 - Origin & Inspiration

Section 1 - Windows Compliance Testing

1.1. Application

1.3. Text Boxes

1.4. Option (Radio Buttons)

1.5. Check Boxes

1.6. Command Buttons

1.7. Drop Down List Boxes

1.8. Combo Boxes

1.9. List Boxes

Section 2 - Screen Validation Checklist

2.1. Aesthetic Conditions:

2.2. Validation Conditions:

2.3. Navigation Conditions:

2.4. Usability Conditions:

2.5. Data Integrity Conditions:

2.6. Modes (Editable Read-only) Conditions:

2.7. General Conditions:

2.8. Specific Field Tests

2.8.1. Date Field Checks

2.8.2. Numeric Fields

2.8.3. Alpha Field Checks

Section 3 - Validation Testing - Standard Actions

3.1. Examples of Standard Actions - Substitute your specific commands