Testing Circus Vol1 Issue2 October/November 2010

8/8/2019 Testing Circus Vol1 Issue2 October/November 2010

1/32

Testing CircusVolume 1 - Issue 2 October/November 2010

Your Monthly Magazine

on

Basics of Software Testing

TOP 100 Software Testing Blogs

Interview with Vipul Gupta

Test Case Practice

QTP Code Corner

Installation Testing

Acceptance Testing

29 Tips to Promote Testing

Software Testing News

Testers in Twitter


2/32

www.TestingCircus.com October/November 2010 - 2 -

Testing CircusVolume 1 - Issue 2 October/November 2010Help Chandrasekhar BN, a Software Tester,

beat Acute Lymphoblastic Leukemia.

Chandrasekhar B N is a 26 year old Software Tester working at

Bangalore. He was detected with Blood cancer (Acute Lymphoblastic

Leukemia - with Ph+ve) in October. Chandrashekar is the sole bread

earner in the family. His mother is a housewife and his 21 year old

brother is a student, too. Doctors have prescribed chemotherapy

and bone marrow transplant at a cost of Rs. 8 lacs for chemotherapy

+ Rs. 10 lacs for Bone Marrow Transplant. As he is now getting

treatment, with no additional income in the family, family members

and friends are trying to gather funds for his treatment and daily

expenses but are at the end of their resources.

We urge all readers ofTesting Circus to donate generously for this purpose. Lets help our fellow

software tester this Diwali season so that Chandrasekhar can have a Happy New Year.

Please note: Donations made to CANCER PATIENTS AID ASSOCIATION , CPAA are exempt from

Income Tax under Section 80G of the Income Tax Act INDIA (50% exemption). Your receipt and

tax exemption certificate will be sent to the address given in the CPAA form. Please enter your

full postal address where CPAA can mail your 80G Exemption Certificate carefully. Your address

will remain with CPAA and will not be shared with any other party.

No donation is small. You can do it online through your VISA/Matecard. (Donors from outside

India can do it online) https://donations.cpaaindia.org/

Alternately, you can also write a cheque or send demand draft in the name "CANCER PATIENTS

AID ASSOCIATION " and mail it to:Dr. Shubha Maudgal

Executive Director

Cancer Patients Aid Association

Smt. Panadevi Dalmia Cancer Management Centre

King George V Memorial, Dr. E. Moses Road,

Mahalakshmi, Mumbai - 400 011

Tel: +91 22 2492 4000 / 2492 8775 Fax: +91 22 2497 3599

Please Note: Write Chandrasekhar B N on the back of the cheque.


3/32


4/32


The first issue of Testing Circus was received with warmwelcome from the software testing community. The

effort of small Testing Circus team was appreciated by

many. The official subscription list has nearly tripled

since the first issue was published and the number is

increasing every day.

Many of the topics that we publish in this magazine are

already available in the internet in some form or other.

We wanted to give our readers selected content on

basics of software testing. We wish to make Testing Circus a magazine for masses,

not for pundits. No philosophical topics, no pedantic subjects we would like to giveyou something that is useful at the ground zero of software testing. We are targeting

those who test, not who speak on testing.

We are late in publishing our 2nd issue of Testing Circus. It is because we are still a

small passionate group of testing professionals committed to our day jobs in different

IT companies. The Testing Circus is an output of our combined effort that we spend

after our office hours. We do not have an office or a publication house. We are

connected by our passion for software testing. We are committed to give Testing

Circus free of cost to our readers.

Testing Circus needs more volunteers from software testing community. We need morewriters who can give us content suitable for basic levels of software testing. We also

need one representative from each IT organization where testing is practiced as an

independent activity different from development. These volunteers will help us in

bringing in more testers to Testing Circus; to read, contribute and to share knowledge.

We will publish a list of volunteers in this magazine.

We received lots of feedbacks on our first issue. We have tried to implement lots of

suggestions in this issue. Few readers did not like one or two sections in the magazine.

We have limited the content in those sections. It is your feedbacks that will help us

improve day by day, issue by issue. Please send us your suggestions what you like and

most importantly what you dont like.

One of our fellow testers, Chandrasekhar B N is suffering from Blood Cancer. Please

donate your half day salary for his treatment if possible. Testing Circus team wishes

him a speedy recovery. Meanwhile enjoy the 2nd issue of Testing Circus. Jai Ho Testing!

~Ajoy Kumar Singha

http://twitter.com/ajoysingha


5/32


First of all I would like to congratulate your efforts and the devotion that you haveshown for publishing this magazine. I really liked this magazine specially being asoftware tester I needed this kind of stuffs which not only help me in building a goodcareer but also useful for making relation with the testers from all around the world.My sincere wishes to all the testers who worked so hard to publish this magazine. As atester I also would like to contribute my knowledge and experience for Testing Circus.So if I can do anything then that will be my pleasure to get associated with TestingCircus. Though I have less experience in this industry still I feel I can be a part of thisfamily and will contribute till I remain associated and even further in future.~Rahul SrivastavaCalsoft Pvt. Ltd.

[Editor] Rahul, we would love to get your contribution for the magazine. We hopeyour knowledge in testing arena would be a great help to other fellow testers.

It is a wonderful start up. No words to say... Im loving it.~Pankaj Sharma

Thanks for sending the magazine. It's really helpful & knowledgeable. I am inspired by

the topic "Content Author" mentioned on the site. I will love to contribute to it.~Swastika Nandi

[Editor] Swastika, please go ahead and send us your article for the magazine.

I have started my testing career six months ago.This magazine is good for beginners. I really enjoyed a lot, especially Effective BugReporting & Agile Testing.~Anshu Jain

I have recently started learning Software Testing course. The e-magazine will be verygood if you collect some real information through your experience or any third partysites. I wish you all the best and I am sure the e-magazine will succeed within shortperiod of time.~Kumar.S.K


6/32


I really enjoyed reading your first edition of "Testing Circus." I work for Sogeti USA, aconsulting company in Cincinnati, OH, and have been involved with software testingfor about three years. If you are in need of articles or ideas for articles, I would love

to contribute. I enjoy writing, especially about testing processes and concepts. Letme know if I can help, and keep up the good work!~Matt RileySogeti USA

[Editor] Thank you Matt for willing to contribute. We look forward to your article.

I read your September issue and it is very good. I want to learn about testing - manualand automation tool like QTP and Bugzilla through your magazine.

~Karunakar Reddy

[Editor] Dear Karunakar, we will try to publish some hands on tutorial for Bugzilla.There is already a regular feature QTP Code Corner. You can get benefitted from thatarticle.

I have taken a deep dive into the Testing Circus magazine and it gives me immensepleasure to see such intelligent initiative by Indian Testers. I have been regular readerof Software Testing Club Magazine (STC) and am really impressed to see our Indianfellows giving brilliant output on same lines and in much better way.

Would definitely like and love to contribute and grow more by working with you all.~Lalitkumar BhamareTCS Mumbai

[Editor] Lalit, this magazine is published from India but the people associated are from all over the world. Please contribute to this magazine. Testing communityrequires knowledge from testers like you.

Congratulations to Shyam Sundar Mahalingam, PaulOakes and Prashant Tewari for correctly answering thepuzzle published in our September Issue.


7/32


By PramodKumar

Installation testing is an area of software testing that focuses on to ensure

successful/proper installation and un-installation of any software application.

Installation work can be divided into four general areas -

1. Type of Installation

2. Mode of installation

3. Testing During Installation

4. Post Installation Testing

Types of Installation -

1. Fresh Installation of software: The word Fresh refer to the fresh platform(OS) on which software needs to install. An OS will be consider as fresh if no

other/same version of that software is install ever, other software may be

present.

2. Upgrade of existing software with new version: In this scenario, an older

version of same software is already installed on Platform (OS) and we need to

upgrade to latest version. We should always test, if installing same version ofsoftware which is present in OS. The result depends on the requirement, if

requirement says software

can be upgraded by same

version then it should

allow. Otherwise it should

prompt message that same

version of software is

already installed.

Sometime it happens that

when trying to runinstallation of same

version the software gives

option to uninstall, we

should test this scenario

too.


8/32

M

w.

3

4

d

1

2

3

4

5

Tes

.

s

.I

s

i

o

. I

. I

. I

.

. I

(

ing

p

o

pg

of

a

eexp

n-

n

re

ho

nst

in

nst

D/

nst

ile

nst

et

ile

nst

on

et

ee

Cir

ra

es

ra

wa

ke

d tec

Ins

hi

te

rtc

all

st

all

DV

all

s k

all

o

nt

all

lin

d

ds

us.

in

in

e

re

t a

oed

tal

s

d

ut

ati

lla

ati

D

ati

pt

ati

rk

in

P

a

pi

or

is

in

th

wi

a

h

pr

O

wi

wisy

ati

):

w

to

co

g

to

fro

is

d

es. If

lat

ce

n

re

n

tio

on

on

in

on

n

tal

shi

mi

ec

se

sta

is

za

d

pp

e-s

th

zaste

on

Th

lo

be

f

pi

m

in

cli

thno

ion

ari

he

at

sys

n -

fr

fr

HD

fr

in

lat

ng

nis

o

lec

lla

i

d

en

el

ca

ut

dm.

es

ad

tes

la

tu

pr

tal

nt

att,

o

o

sy

d

te

m

m

D i

m

sta

ion

s

tra

f s

te

all

io

st

do

ct

G

fr

fro

d

d

te

fo

e

evi

le

sy

afhe

S

we

ste

ur

is

CD

Du

n t

ne

llin

:

ft

tor

ft

s

ed

lla

s

i

ith

d

be

I i

m

m

ys

o

.

m

wh

ous

o

te

ern

ft

t

m

ing

cl

/D

m

he

w

g f

ar

a

st

ec

tio

ot

ns

de

et

i

ns

th

, l

e

(O

en

O

n i

m

OSe

a

st

go

in

an

D:

s

sa

rk

ro

e i

e

m.

aus

n

a

all

fa

tin

nst

all

e

e

ts

p

S)

a

S

t.

ee

isil

e:

th

r

tal

ed

w

to

e

:

r

in

pu

o

T

ile

e

G

pe

ati

lt

s.

all

ati

sa

bsi

of

ra

on

ne

ver

No

d t

upl n

Th

at

m

lat

/fr

en

ed

m

he

m

ne

sh

ll

is

nt

in

UI

ar

n

or

d

n

e

te

sof

y f

Oc

w

sio

w

o u

graed

is i

af

ve

ion

esh

in

in

ch

n s

ot

w

tw

old

ob

ic

OS

n.

ne

pg

deto

s a

er

d o

is

or

sta

h

ine

ft

lo

rk

re

er

r/

s

is

Su

ad

tpr

lso

un

r n

re

n

llin

rd

a

cat

th

du

an

ov

oft

la

p

er

e f

Vovi

i

-in

ot;

o

t.

g s

dr

e

ion

ro

mp

is

m

wa

nc

se

sio

ro

istde

po

sta

re

ed

oft

iv

u

gh

s a

in

er

re

he

, c

X

,pa

rta

lla

gis

or

wa

:

ps

S

re

sta

201

is

i

lie

f

P t

hech

nt

tio

try

n

re

wh

is

S;

av

lle

0

ins

nt

S

o V

soto

pa

en

t;

fro

en

ke

in

ila

r

tal

ar

is

(Vi

ist

ftfix

t

ll

tr

in

ins

t

t

bl

n

led

ke

usi

st

. I

arth

f i

th

a

th

D/

tal

t

his

o

tim

:

h

ng

) i

n t

ise s

nst

f

e

er

DV

lin

iff

sc

lin

e.

his

avi

O

s

his

stam

all

ile

e

o

D

g s

er

en

e.

Th

is

ng

S

el

sc

ille.

ti

w

ov

ds

ri

oft

nt

ri

Th

is

ra

op

s

as

na

run

n

hic

ed

, a

e

a

sys

s

pti

-

re

tio

P

d

rio

ni

es

h

or

te

y

e

te

et

ft

on

8 -

on

n

an

in

,

g

tin

e

no

u

si

fro

o

a

al

;

o

d

o

e

s

.

e

t;

-

g

m

n

k

e

o


9/32


Testing during installation:

During installation we need to verify everything from double clicking on setup exe;

installation wizard; content of wizard; any SLA agreement; all buttons like next,

Back, cancel etc on all page of wizard; any link on wizard like installation guide or

anything which will be fetched from dumps/CD/DVD; all software installation optionlike default, custom, standard etc. While installing from CD drive, check if the

installer is on auto run or not.

If software requires any other software as pre-

requisite then those need to be verified. The

absence of pre-requisite software should be

detected by software installer, if not present on

system.

Testing during Post installation:

After installation tester should verify followingpoints:

1. Entry of installer in Add and remove program with current version

2. Folder structure in installation drive

3. Files created in folder structure

4. Component installed as per installation option like default or standard etc

5. Any shortcut created

6. Registry entry and flags in registry

7. Listing in Start Program menu

8. File type association, if any

9. Smoke testing of software

Un-installation of software:

1. Generally on windows platform un-installation of software is done from

add/remove program.

2. Sometimes uninstaller.exe is an option to uninstall software.

3. Software can be removed from system by deleting files from installed folder

and from registry entry, but this type of removal is not proper and may lead to

unclean system.

Apart from all these, we can test license key validation, trial version date expiry,

installing add on features, repairing of software by reinstalling the software.

Here is a Generic Installation Testing CheckList compiled by Devankur Thakur in his

Blog (http://geekswithblogs.net/dthakur/Default.aspx)

1. Support of the different platforms and configurations needed?


10/32


2. Does Installation in clean state working?

3. Does the installer is able to calculate needed disk space?

4. Does the installer capturing the baseline free space before launching the

installer?

5. Does the amount of space the installer claims it needs for the various type of

installation is actually taken up or is there any discrepancy?6. How much disk space is used by the installer if the installation is quit midway

(this would help gathering information on temp files thats deleted on

quitting).

7. Does the installation recover in case an error is met during the installation?

8. Does the installer able to Repair any corrupt installation?

9. If the application installed properly for each type of installation (for typical,

custom and complete)?

10.Does Installation over network working?

11.If any file association is made during installation, upon un-installation, does the

association is removed and the base file association is returned to the files?

12.Does running the installer, followed by launching the program to run some

tests, and then running the uninstaller, also return your machine to the base

state?

13.Does un-installation leave any registry entry, data files in the system?

14.If there exists a version of the app to be installed already on the machine, does

the installer identify that?

15.Does the installer identify if some needed components (such as, MSDE etc.) are

already installed on the system?

16.Does running two instances of the installer should prompt a message to the user

that an installation setup is already running?

17.If the user logged in, doesnt have write permission for the machine, howinstallation reacts to this?

18.What happens if the installer tries to install to a directory where there is no

write access?

19.Is the installation path configurable/non configurable?

20.Check to ensure that when installing the product, it should provide a browse

button which enables the user to install at any folder, and it should provide by

default folder (For ex: C:\program files)

21.Is the registering and un-registering the components (dlls) on installation and

un-installation is occurring properly?

22.Are all the files installed in the respective folders and path?23.Whether all the files/registry values/services are installed properly.

24.Check whether the shortcuts are installed properly and also the PATH (any

other ENV variables) is updated properly. (It can be CURRENT USERS profile or

All Users profile based on your requirements).

25.Does the installation support, 'UnInstall', 'Modify', 'ReInstall' options?? If

yes, does it work?


11/32


26.If the installer is supporting upgrade feature, does it preserve all the necessary

settings (mostly user preferences)?

27.Check for the user privileges before

starting installation. (In most of the cases,

installer requires ADMIN privileges).

28.Check the uninstaller entry in add-remove programs. (Check for display string,

Display icon and Support information etc.).

29.Does running the installer, and then

running the uninstaller, return the machine

to the base state?

30.Reinstallation should, apart from

identifying previous versions, also should

give an option to Remove and Repair.

31.Check to ensure that license key is

properly stored in Windows Registry library.

32.Check to ensure that if an evaluation

version is installed, then a proper message

should be displayed when the date of period

is expired for evaluation version with proper

error message.

33.Check to ensure that, if Windows

Services are installed then it should install

in the Services folder of windows directory.

34.Check to ensure that if any product

is installed and it is dependent on some

other product, then it should give propermessage as "The Product is not installed and

it should exit". Check for dependencies.

35.If the product to be installed uses

any third party dll and if it is already

installed by some other product confirm

that the current installation doesnt un-

register/tamper it and uses the existing one.

36.If the dll is already there in the system how does the installation work?

37.And also while uninstalling, check should be made as to whether that the

shared dll is left without affecting other product.38. Usability consideration of the installer.

Pramod Kumar has over 4

years of experience inProduct Testing which

includes two and half years

in automation testing with

IBM RFT and QTP. He is

currently employed with

HCL Technologies, Noida.

Apart from work he likes

to play football.

Pramod can be reached athttps://twitter.com/pramodkrnitdgp


12/32


Acceptance Testing

In engineering and its various sub-disciplines, acceptance testing is black-box testingperformed on a system (e.g. software, lots of manufactured mechanical parts, orbatches of chemical products) prior to its delivery. It is also known as functionaltesting, black-box testing, release acceptance, QA testing, application testing,confidence testing, final testing, validation testing, or factory acceptance testing.

In software development, acceptance testing by the system provider is oftendistinguished from acceptance testing by the customer (the user or client) prior toaccepting transfer of ownership. In such environments, acceptance testing performedby the customer is known as user acceptance testing (UAT). This is also known as end-user testing, site (acceptance) testing, or field (acceptance) testing.

A smoke test is used as an acceptance test prior to introducing a build to the maintesting process.

Overview

Acceptance testing generally involves running a suite of tests on the completedsystem. Each individual test, known as a case, exercises a particular operatingcondition of the user's environment or feature of the system, and will result in a passor fail, or Boolean, outcome. There is generally no degree of success or failure. Thetest environment is usually designed to be identical, or as close as possible, to theanticipated user's environment, including extremes of such. These test cases musteach be accompanied by test case input data or a formal description of theoperational activities (or both) to be performedintended to thoroughly exercise thespecific caseand a formal description of the expected results.

Acceptance Tests/Criteria (in Agile Software Development) are usually created bybusiness customers and expressed in a business domain language. These are high level

tests to test the completeness of a user story or stories 'played' during anysprint/iteration. These tests are created ideally through collaboration betweenbusiness customers, business analysts, testers and developers; however the businesscustomers (product owners) are the primary owners of these tests. As the user storiespass their acceptance criteria, the business owners can be sure of the fact that thedevelopers are progressing in the right direction about how the application wasenvisaged to work and so it's essential that these tests include both business logic testsas well as UI validation elements (if need be).


13/32


Acceptance test cards are ideally created during sprint planning or iteration planningmeeting, before development begins so that the developers have a clear idea of whatto develop. Sometimes (due to bad planning!) acceptance tests may span multiplestories (that are not implemented in the same sprint) and there are different ways totest them out during actual sprints. One popular technique is to mock externalinterfaces or data to mimic other stories which might not be played out during an

iteration (as those stories may have been relatively lower business priority). A userstory is not considered complete until the acceptance tests have passed.

Process

The acceptance test suite is run against the supplied input data or using an acceptancetest script to direct the testers. Then the results obtained are compared with theexpected results. If there is a correct match for every case, the test suite is said topass. If not, the system may either be rejected or accepted on conditions previouslyagreed between the sponsor and the manufacturer.

The objective is to provide confidence that the delivered system meets the businessrequirements of both sponsors and users. The acceptance phase may also act as thefinal quality gateway, where any quality defects not previously detected may beuncovered.

A principal purpose of acceptance testing is that, once completed successfully, andprovided certain additional (contractually agreed) acceptance criteria are met, thesponsors will then sign off on the system as satisfying the contract (previously agreedbetween sponsor and manufacturer), and deliver final payment.

User acceptance testing

User Acceptance Testing (UAT) is a process to obtain confirmation by a SubjectMatter Expert (SME), preferably the owner or client of the object under test, throughtrial or review, that a system meets mutually agreed-upon requirements. In softwaredevelopment, UAT is one of the final stages of a project and often occurs before aclient or customer accepts the new system.

Users of the system perform these tests, which developers derive from the client'scontract or the user requirements specification.

Test designers draw up formal tests and devise a range of severity levels. It ispreferable that the designer of the user acceptance tests not be the creator of the

formal integration and system test cases for the same system, however there are somesituations where this may not be avoided. The UAT acts as a final verification of therequired business function and proper functioning of the system, emulating real-worldusage conditions on behalf of the paying client or a specific large customer. If thesoftware works as intended and without issues during normal use, one can reasonablyinfer the same level of stability in production. These tests, which are usuallyperformed by clients or end-users, are not usually focused on identifying simpleproblems such as spelling errors and cosmetic problems, nor show stopper defects,


14/32


such as software crashes; testers and developers previously identify and fix theseissues during earlier unit testing, integration testing, and system testing phases.

The results of these tests give confidence to the clients as to how the system willperform in production. There may also be legal or contractual requirement foracceptance of the system.

Q-UAT - Quantified User Acceptance Testing

Quantified User Acceptance Testing (Q-UAT or, more simply, the QuantifiedApproach) is a revised Business Acceptance Testing process which aims to provide asmarter and faster alternative to the traditional UAT phase. Depth-testing is carriedout against Business Requirement only at specific planned points in the application orservice under test. A reliance on better quality code delivery from Development/Buildphase is assumed and a complete understanding of the appropriate Business Process isa pre-requisite. This methodology if carried out correctly results in a quick turnaroundagainst plan, a decreased number of test scenarios which are more complex and wider

in breadth than traditional UAT and ultimately the equivalent confidence levelattained via a shorter delivery window, allowing products/changes to be brought tomarket quicker.

The Approach is based on a 'gated' 3-dimensional model the key concepts of which are:

Linear Testing (LT, the 1st dimension) Recursive Testing (RT, the 2nd dimension) Adaptive Testing (AT, the 3rd dimension).

The four 'gates' which conjoin and support the 3-dimensional model act as qualitysafeguards and include contemporary testing concepts such as:

Internal Consistency Checks (ICS) Major Systems/Services Checks (MSC) Realtime/Reactive Regression (RTR)

The Quantified Approach was shaped by the former "guerilla" method of AcceptanceTesting which was itself a response to testing phases which proved too costly to besustainable for many small/medium-scale projects.

Acceptance testing in Extreme Programming

Acceptance testing is a term used in agile software development methodologies,particularly Extreme Programming, referring to the functional testing of a user storyby the software development team during the implementation phase.

The customer specifies scenarios to test when a user story has been correctlyimplemented. A story can have one or many acceptance tests, whatever it takes toensure the functionality works. Acceptance tests are black box system tests. Eachacceptance test represents some expected result from the system. Customers areresponsible for verifying the correctness of the acceptance tests and reviewing test


15/32


scores to decide which failed tests are of highest priority. Acceptance tests are alsoused as regression tests prior to a production release. A user story is not consideredcomplete until it has passed its acceptance tests. This means that new acceptancetests must be created for each iteration or the development team will report zeroprogress.

Types of acceptance testing

Typical types of acceptance testing include the following

User acceptance testingThis may include factory acceptance testing, i.e. the testing done by factoryusers before the factory is moved to its own site, after which site acceptancetesting may be performed by the users at the site.

Operational Acceptance Testing (OAT)Also known as operational readiness testing, this refers to the checking done toa system to ensure that processes and procedures are in place to allow the

system to be used and maintained. This may include checks done to back-upfacilities, procedures for disaster recovery, training for end users, maintenanceprocedures, and security procedures.

Contract and regulation acceptance testingIn contract acceptance testing, a system is tested against acceptance criteriaas documented in a contract, before the system is accepted. In regulationacceptance testing, a system is tested to ensure it meets governmental, legaland safety standards.

Alpha and beta testingAlpha testing takes place at developers' sites, and involves testing of theoperational system by internal staff, before it is released to externalcustomers. Beta testing takes place at customers' sites, and involves testing by

a group of customers who use the system at their own locations and providefeedback, before the system is released to other customers. The latter is oftencalled field testing.

List of development to production (testing) environments

DEV, Development Environment [1] DTE, Development Testing Environment QA, Quality Assurance (Testing Environment) [2] DIT, Development Integration Testing DST, Development System Testing

SIT, System Integration Testing UAT, User Acceptance Testing [3] PROD, Production Environment [4]

[1-4] Usual development environment stages in medium-sized development projects.

Content Sourcehttp://en.wikipedia.org/wiki/Acceptance_testing


16/32


By Steven Machtelinckx

# Site Author URL

1 James Bach's Blog James Bach http://www.satisfice.com/blog

2 Testing at the Edge ofChaos

Matt Heusser http://blogs.stpcollaborative.com/matt

3 Agile Testing Grig Gheorghiu http://agiletesting.blogspot.com/

4 Martinfowler.com Martin Fowler http://martinfowler.com/

5 Tester Tested! Pradeep Soundararajan http://testertested.blogspot.com/

6 Testing Blog Google Testing http://googletesting.blogspot.com/

7 Cem Kaners Blog Cem Kaner http://www.satisfice.com/kaner

8 Miko Hevery Miko Hevery http://misko.hevery.com/

9 DevelopSense Michael Bolton http://www.developsense.com/blog.html

10 Sara Ford's Weblog Sara Ford http://blogs.msdn.com/saraford/default.aspx

11 Steve Rowe's Blog Steve Rowe http://blogs.msdn.com/steverowe

12 Test Obsessed Elisabeth Hendrickson http://www.testobsessed.com/

13 Software Quality Insights ( various ) http://itknowledgeexchange.techtarget.com/software-quality

14 Exploration ThroughExample

Brian Marick http://www.exampler.com/blog

15 Gojko Adzic Gojko Adzic http://gojko.net/

16 Thinking Tester Shrini Kulkarni http://shrinik.blogspot.com/

17 Chris McMahon's Blog Chris McMahon http://chrismcmahonsblog.blogspot.com/

18 JW on Test James Whittaker http://blogs.msdn.com/b/james_whittaker/

19 Software testing help Vijay http://www.softwaretestinghelp.com/

20 Corey Goldberg Corey Goldberg http://coreygoldberg.blogspot.com/

21 Quality Frog Ben Simo http://www.questioningsoftware.com/

22 Testing Hotlist Update Bret Pettichord http://www.io.com/%7Ewazmo/blog

23 Abakas Catherine Powell http://blog.abakas.com/

24 Collaborative SoftwareTesting

Jonathan Kohl http://www.kohl.ca/blog

25 Sbarber's blog Scott Barber http://www.testingreflections.com/blog/74

26 Adam goucher Adam goucher http://adam.goucher.ca/

27 Eric Jarvi Eric Jarvi http://blogs.msdn.com/ejarvi

28 Karen N. Johnson's blog Karen N. Johnson http://www.testingreflections.com/blog/3804

29 Test Guide Michael Hunter http://blogs.msdn.com/micahel

30 Curious Tester Parimala Shankaraiah http://curioustester.blogspot.com/

31 Testy Redhead Lanette Creamer http://blog.testyredhead.com/

32 Antony Marcano's blog Antony Marcano http://www.testingreflections.com/blog/2

33 All Things Quality Joe Strazzere http://www.sqablogs.com/jstrazzere


17/32


34 I. M. Testy Bj Rollinson http://testingmentor.com/imtesty

35 Software testing zone Debasis Pradhan http://software-testing-zone.blogspot.com/

36 PractiTest QA Blog Joel Montvelisky http://qablog.practitest.com/

37 Practical QA Linda Wilkinson http://www.practicalqa.com/

38 Marlenas Blog Marlena Compton http://marlenacompton.com/

39 Software Testing andmore

Ewald Roodenrijs,Andras Prins

http://www.testingthefuture.net/

40 patrickwilsonwelsh.com Patrick Wilson-Welsh http://patrickwilsonwelsh.com/

41 Quality Assurance andSoftware Testing

( various ) http://quality-assurance-software-testing.blogspot.com/

42 Testing Testing 1,2,3 Chan Chaiyochlarb http://blogs.msdn.com/testing123

43 Mike Kelly's blog Mike Kelly http://www.michaeldkelly.com/blog

44 Test this Blog Eric Jacobson http://www.testthisblog.com/

45 Enjoy testing Ajay Balamurugadas http://enjoytesting.blogspot.com/

46 Evil Tester Alan Richardson http://www.eviltester.com/

47 Tooth of the Weasel Alan Page http://angryweasel.com/blog48 Charlie Audritsh's blog Charlie Audritsh http://www.testingreflections.com/blog/329

49 Maverick Tester Anne-Marie Charrett http://mavericktester.com/

50 Paul Gerrard's blog Paul Gerrard http://gerrardconsulting.com/

51 shino.de Markus Gaertner http://blog.shino.de/

52 Cartoon Tester Andy Glover http://cartoontester.blogspot.com/

53 cLabs Blogki Chris Morris http://www.clabs.org/blogki

54 Jeff Fry on Testing Jeff Fry http://testingjeff.wordpress.com/

55 Venkat's Blog Venkat ReddyChintalapudi

http://venkatreddy.in/

56 Agile Testing and ProcessThoughts Janet Gregory http://janetgregory.blogspot.com/

57 Software Testing Stuff ( various ) http://www.softwaretestingstuff.com/

58 selenadelesie.com Selena Delesie http://selenadelesie.com/

59 Software Sleuthing Josh Poley http://blogs.msdn.com/joshpoley

60 The Software Quality Blog Vijay Bhaskar http://softwarequalityonline.blogspot.com/

61 Expected Results Phil Kirkham http://expectedresults.blogspot.com/

62 One of the wolves Tim Coulter http://www.oneofthewolves.com/

63 Musing about SoftwareTesting

Keith Stobie http://testmuse.spaces.live.com/

64 Jon Bach's blog Jonathan Bach http://jonbox.wordpress.com/

65 Quardev ( various ) http://www.quardev.com/blog

66 Software Testing ClubBlog

( various ) http://blog.softwaretestingclub.com/

67 TestToTester Sharath Byregowda http://testtotester.blogspot.com/

68 Agile Testing with LisaCrispin

Lisa Crispin http://lisacrispin.com/wordpress/

69 Confessions of aPassionate Tester

Dawn Cannan http://www.passionatetester.com/


18/32


70 I am filled with solutions Dustin Andrews http://blogs.msdn.com/dustin_andrews

71 Software Tasting Geordie Keitt http://tester.geordiekeitt.com/

72 Rosie Land Rosie Sherry http://www.rosiesherry.com/blog

73 Still Life Steve Swanson http://steveswanson.wordpress.com/

74 Brian Osman Brian Osman http://bjosman.wordpress.com/

75 Dhanasekar Ss Blog Dhanasekar S http://testingideas.wordpress.com/

76 The Social Tester Rob Lambert http://thesocialtester.posterous.com/

77 QA Insight Brent Strange http://www1.qainsight.net:8080/

78 The Testing Blog ( various ) http://thetestingblog.com/

79 Testingminded Steven Machtelinckx http://www.testingminded.com/

80 John McConda's blog John McConda http://www.testingreflections.com/blog/3467

81 Software Testing Len DiMaggio http://swqetesting.blogspot.com/

82 Jeroen's world ofSoftware Testing

Jeroen Rosink http://testconsultant.blogspot.com/

83 TestingPerspective Rahul Verma http://www.testingperspective.com/blog

84 Adam White Adam White http://www.adamkwhite.com/

85 Purple Box Testing Trish Khoo http://ubertest.hogfish.net/

86 Lessons Learned by aSoftware Tester

Paul Carvalho http://swtester.blogspot.com/

87 Pliant Alliance Tim Beck http://pliantalliance.org/

88 Testjutsu Ben Kelly http://www.testjutsu.com/

89 Illiteration Jared Quinert http://www.quinert.com/blog

90 Tester Testifies Raj Kamal http://geektester.blogspot.com/

91 Santhosh Tuppad's Blog Santhosh Tuppad http://tuppad.com/blog/

92 Teknologika Bruce McLeod http://www.teknologika.com/blog

93 Creative Tester Anuj Magazine http://anujmagazine.blogspot.com/

94 Tester Troubles Ray Claridge http://www.testertroubles.com/

95 Thoughts on QA andEngineering

John Overbaugh http://thoughtsonqa.blogspot.com/

96 Quick Testing Tips ( various ) http://www.quicktestingtips.com/

97 Cruisin QA Brett Leonard http://cruisinqa.blogspot.com/

98 QA Hates You The Director http://qahatesyou.com/wordpress

99 Tester Lost Focus Michelle Smith http://testerlostfocus.blogspot.com/

100 James McCaffrey's blog James McCaffrey http://jamesmccaffrey.spaces.live.com/blog

This list is compiled by Steven Machtelinckx who is a test analyst and regularly blogsat http://www.testingminded.comTo know more about how Steven has compiled theabove list and ordered them from 1 to 100 and newer addition to the list, please visithis blogs post Top 100 Software Testing Blogs. The list is republished in TestingCircus with his written permission. Enjoy and Happy Reading. Editor


19/32

ht

d

w.

tp:

v

Tes

/g

el

ing

ek

to

Cir

es

ee

us.

er.

ti

co

blo

rn

gsp

sh

ot.

we

o

/2

nr

10

Ui

/0

Fg

/s

,

Oc

ft

la e

ob

ar

ta

r/

-te

nik

ov

sti

gd

m

g-

t,h

er

ta

i

201

e-a

ht

0

ct-

eo

un

re

ny.

ep

t

to

l

olu

d t!

-

is

19 -

t

-


20/32


By Rob van Steenbergen

Although we testers all feel testing is a real profession, the knowledge of testing in

other disciplines is often very limited to pushing some buttons or so.

What is testing? When do you start? How you work through a test process? What is a

tester doing exactly? This is something you want to know if you require a test team for

your project to start testing. It's time to go out to everyone and explain about testing

and get some understanding.

So here are my 29 tips to promote testing in an organization where testing is still at a

very initial stage or people in the organization do not understand what testing is.

1. If someone asks you to give a presentation on testing: always do!

2. Place posters about testing to a wall.

3. Place articles about testing from IT magazines to a wall (the test wall?)

4. Understand the developer and other test disciplines well and know how to deal

with them.

5. Did no one test yet at a department at your organization? Just start testing and

communicate your defects and test results.

6. Dont have a bugs database yet? Create it yourself; start with an Excel sheet if

necessary. A central list of product issues convinces many people of the

usefulness of such a tool.7. Stay positive about testing in your conversation and communication. Radiate

passion for the testing profession.

8. Tell people about the benefits of starting early with testing in a project and

finding those defects as early as possible.

9. Talk through the exit criteria of a test with all stakeholders.

10.Discuss Test planning step-by-step with project managers and team leaders.

11.Do regular product risk analysis sessions.

12.Publish in the organizations magazine about the testing organization.

13.Have a KISS (Keep it Simple Stupid) talk ready about testing that you can

always use when talking about testing. (Elevator pitch)14.Create a recognizable logo for your test team and use it on all your documents

15.Put a developer in the test team

16.Put a tester on the development team

17.Not an independent test team but dependent teams. Needing each other

works great to create a good product.


21/32


18.For managers: put the focus on the process not the product, we need someone

to watch the process, including the testing process.

19.For managers: Each step of the

process should have a test, not only at

the end of a project.

20.Ensure management commit-ment. This is needed to make to testing

visible in the organization.

21.If you communicate about

testing, do not constantly repeat the

same words. Each repetition makes you

less credible, after a while people will

not listen anymore (oh no, not again the

same story).

22.Tap into the feelings of others in

conveying the message, what

emotionally touches your stakeholder

(mostly money and loosing time for

managers I guess).

23.Spread articles about testing,

magazines, make copies, create a test

library for interested people.

24.Go to test events, bring your

colleagues along.

25.As software goes wrong in

production, analyze and discuss with

management how those mistakes couldbe found early in the development

phase, before going in to production.

26.Ensure that managers at various

levels have understanding of the risks of

not testing, the testing process and the

specific problems that arise daily in the

workplace.

27.In this process: Patience,

patience, patience

28.Tell what you did; do marketingfor your own work. What and how many

defects have you found on time?

29.Create a roadmap how to get test consciousness into your organization

(communication planning).

Add your own tips to make this list longer and better.

Rob van Steenbergen from theNetherlands is an independentsoftware test consultant and has14 years of experience as asoftware tester in miscellaneousareas.

In the last 4 years he has beeninvolved in infrastructureprojects and is working now on adesktop virtualization projectwhere he is testing and

coordinating the tests.

In his leisure time he reads,listens to lots of music andwatches even more movies. Histwitter account, weblog andother links can be found athis website

www.chickenwings.nl


22/32


@

Gerald Weinberg

BIO: Writer, Consultant, Teacher

16 following

2,171followers

248 listed

http://twitter.com/JerryWeinberg

Michel Kraaij

BIO: With lots of professionalism and even more creativism I test, coach, inform and

support. Why? To make someone else's work easier! I test, therefore, I am.

101 following

172 followers16 listed

http://twitter.com/MichelKraaij

Shrini Kulkarni

BIO: Software Testing Generalist, Systems thinker, Skeptic75 following

511 followers

51 listed

http://twitter.com/shrinik


23/32


Rahul Verma

BIO: Software Tester, Blogger, Python Enthusiast with special interest in performance

testing, security testing and design of test automation frameworks

132 following

109 followers

11 listed

http://twitter.com/rahul_verma

Daily Testing Tip

BIO: Daily Testing Tips

5 following

611 followers

69 listed

http://twitter.com/dailytestingtip

..... more testers in next issue.

TestingCircus

Bio: Testing Circus is a free e-magazine on Software Testing.175 following

238 followers

16 listed

http://twitter.com/testingcircus


24/32


By Naresh Bisht

Requirement A Stapler

To generate and write test cases to test a Stapler.

Size 176.28 mm wide

Weight .5 lbs and/or 230 grams

Color Blue

Sr.

No.

Steps to Execute Expected Result Actual

Result*

Remarks

1 Examine for size of stapler It should be 176.28 mm wide

2 Examine the weight of stapler Stapler should weigh .5 lbsand/or 230 grams

3 Examine the color of stapler It should Blue in color

4 How easily can you hold it inhands? Is it compatible withyour fingers?

Proper grip to hand andsmooth to fingers

5 Staples should fit in the stapler. Space for staples should beproper not large or small

6 Verify that it can staple

perfectly?

It should staple perfectly on all

kinds of paper7 Verify that the spring is pushing

the staples freely as desired?Spring should not be very tightto the stapler pins

8 Verify that the last pin canstaple without any problem?

Last pin should not create anyproblem to staple

9 Does the stapler indicate whenthe staples are empty?

It should indicate that the pinsare empty.

10 Verify that the stapler canstaple a bunch of papers(ranging from 5-10)?

It should staple perfectly forbunch of papers

11 Verify that the stapler can

staple card boards?

It should not fail to staple card

boards12 Put 2 bunch of stapler pins to

check the spring is able to takethe load

It should able to take the loadfor two or three bunch ofstapler pin

13 It is working fine with astandard bunch of pins.

Maximum limit should easilytake load of three bunch ofpins

14 Size of the pins required Standard size should taken bystapler


25/32

*A

1

1

1

1

1

2

2

2

w.

tu

ar

xpes

m

ec

arttp

Tes

l R

Chpr

Chshpl

StthfinDodepiAtpltecepiTr

inDocefrChcost

es

eriin

lo

hn

esh://

ing

sul

ecp

eculce

plte.esgrs?wstip

asott

laresasmecunpl

B

n.

ed

lo

catwi

Cir

ts a

rl

d aof

aill

thes

atc cerato

, ein

gethto

1stt

ryr

sh

e ie

wi

ie

ntte

us.

re

he

heutpr

ll tlas

stfo

teovtufuc)?se

sistworeof

t h

n Sis c

th

,

er.c

co

rit

he

hem

evi

het p

aplin

prenc

t s

e?aplrk

2ndra

ma

s

oftur

HC

ur

eam

ten

r t

r tti

ous

pinin i

erser

rael

oeio

ta

erafflndnu

y

waen

L

ga

chNa

wh

e

eallpi

s at s

optin

turt?s t(s

les

brerornaac

ar

retly

n.

dres

en

spr

ney ln

ndo

ng/r

ete

pri

w

akdr

eur

s

th_B

ou

ing

tad

chld

18em

oeh

stangs

ic

anp

ane o

ish

get

ru

inin

ecsta

ovi

s tt

ple, r

h a

din

df t

t

to

ns

pl

ng

eolrar

re

it

e

tes

Inc

ebcvi

Oc

th

tseehagiseewEdi

Itco

Naube

ItanafIt

Tebe

St

Itsh

Brmenst

ob

ac

iss ooustne

s.s otor

shondi

xttoab

shod ser

sho

mpas

pl

shooul

annugrapl

r/

tua

sev

otiversRen t

aS

o

oo

ultio

pinat

le

ultapthul

erpe

s

uld

nfaver

ov

l st

ctiaricl. Ionde

n,rmw

ple

pns

shicato

wlerlao

tur r

ho

nor

mtuo

m

pl

nusim

t ih

rstes

Fa

rih

Moissis

asd

op

oulllyta

orkshsten

requ

uld

tp

ae sn t

er

r.

witth

s jwart c

ce

eswmYt

ew

erl

d lanple

fioulpinin

esire

n

rerop

dhohe

201

matustto

ease

B

ohanus

urns

oad u

eds18

istm

t

kerl

couldbo

0

ill,testancs.

o

Svd Ia le

nai

or

ser

illotsed

ncnt.

e i

ny.

ntby

pbjt c

gprou

A

on yaot.yo

ffs

f

sh

lasja.eg

e s

ns

it

ry

f

acct

asiveacag

d

'suf

u.

yoor

r a

oul

t pb

ee

ho

rt

f

ics asi

hed

ct

abein

urDi

ll

d

in

ld

d.

tndrieaforto

o

len.

Pnn

oaptes tws

.?

aer.

ripli

horitiar

d

-

teatieresnge

25

teona

tertehe

25 -

sts.es,stir


26/32


Microsoft to open R&D center in Russia's Hi-Tech Hub

U.S. software giant Microsoft Corp. will establish a research and development center

in the Skolkovo innovation hub near Moscow, Microsoft CEO Steve Ballmer and

Skolkovo president Viktor Vekselberg said on Monday.

Ballmer said the R&D center would focus on the cloud computing technologies both for

Russia and the rest of the world. Cloud computing providers deliver business

applications on-line that come from other web servers.

Along with the R&D center, Microsoft is set to establish an information technologytesting center that would help IT specialists test their software products in various

conditions. The U.S. IT giant will also participate in creating Skolkovo University of

Technology which would work in tight cooperation with Microsoft's divisions in

Cambridge and Redmond.

Microsoft also plans to support one hundred Russian startups investing from $50,000 to

$500,000 on each of them, the head of Microsoft Russia, Nikolai Pryanishnikov, said.

Skolkovo, dubbed Russia's Silicon Valley, is being built from scratch 20 kilometers west

of Moscow. The center will focus on research in five priority spheres: energy,

information technologies, communication, biomedical research and nucleartechnologies.

Russian President Dmitry Medvedev has called on foreign companies to participate in

the Skolkovo project. In October, California Governor Arnold Schwarzenegger, during

his visit to Russia, brought to Moscow a delegation of the U.S. investors interested in

cooperation with Russia's innovation hub.

The delegation included representatives of venture capital funds and innovation

companies from the U.S. Silicon Valley.

NIST releases a tutorial on automated testing of multiple variables

The National Institute of Standards and Technology has developed algorithms for

automated testing of the multiple variables in software that can cause security faults,

and has released a tutorial for using the tools.

The improper or unexpected interaction of two or more parameters in a piece of

software, such as inputs or configuration settings, is a significant cause of security


27/32


bugs. But testing for these problems has been limited by the cost and complexity of

testing the huge number of possible combinations. NIST in 2003 reported that such

problems cost the U.S. economy more than $59 billion a year despite the fact that

more than half of most software development budgets went toward testing.

Research has shown that in many cases the large majority of such faults, from 89 to100 percent, are caused by combinations of no more than four variables, and virtually

all are caused by no more than six, NIST has reported.

Read More - http://csrc.nist.gov/groups/SNS/acts/index.html

Software Test Professionals Conference & Expo, 2010

Software Test Professionals Conference & Expo 2010, the leading conference for

software test management and quality practitioners, concluded last week in Las

Vegas, Nevada. The conference, produced and managed by Software Test

Professionals Association, offered five keynote presentations, six pre-conferenceworkshops and concluded with 40 high-level breakout sessions. Session tracks included

hands-on testing; test leadership; test strategy & process; Agile testing; performance

testing; and test automation. Conference attendees and presenters were excited

about the quality content, networking opportunities and energy experienced at the

conference. The association leveraged the input of their strategic advisory board and

conference program board selected from the software testing community to help

define the overall direction of the conference and ultimately develop the conference

program.

In addition, the association presented its first annual luminary award to Mr. Gerald M.

Weinberg for lifetime achievement and excellence in software testing. Mr. Weinberg

is a programmer who has authored or co-authored several hundred articles and more

than 30 books. His works have addressed operating systems and programming

languages, as well as all phases of the software life-cycle, including defining problems

and requirements, analysis and design, testing and measurement, as well as

management. Mr. Weinberg was chosen as the award recipient by the software testing

community.

Peggy Libbey, Software Test Professionals President and CEO, stated, "I am pleased

with the positive feedback I have received from conference attendees and presenters.

The software testing community came together to share their knowledge andexperiences with an ultimate goal of improving the effectiveness and efficiency of the

methodologies of the industry thereby escalating the overall perception of the quality

professional. Community input will continue to drive the program content of our

conferences." The association announced that Software Test Professionals Conference

& Expo 2011 will be held March 22-24 at the Gaylord Opryland Resort in Nashville,

Tennessee.

Sources Google News and various internet news portals.


28/32


Problem:

How to create customized date function in QTP?

Solution:User can create new date formats as per their requirement.

You just need a bit modification in existing function.

Single function to get the date in different format

dformat("a",b)

Where

parameter a denotes the date

parameter b denotes the type of format from the below list

1. November 3, 2010

2. 3 November, 2010

3. 3 Nov, 2010

4. 3-Nov-2010

5. 11/3/2010

6. 3-11-2010

msgbox dformat(date(),4)

'The above code will display the current date as "30-Oct-2010"

Function dformat(dat,index)

If index=1 Then

dformat=Monthname(month(dat))&" "&day(dat)&", "&year(dat)

else

If index=2 Then

dformat=day(dat)&" "&Monthname(month(dat))&", "&year(dat)

else

If index=3 Then

dformat=day(dat)&" "&Monthname(month(dat),true)&", "&year(dat)

else

If index=4 Then

dformat=day(dat)&"-"&Monthname(month(dat),true)&"-"&year(dat)

else

If index=5 Then

dformat=month(dat)&"/"&day(dat)&"/"&year(dat)

else

dformat=day(dat)&"-"&month(dat)&"-"&year(dat)

End If

End If

End If

End If

End If

End Function

Jaijeet Pandey has over 5

years of experience in

Application Development,Maintenance and Testing.

From more than last 3 years

he is involved in automation

testing with QTP and Load

Runner tools. He also teaches

QTP on weekends. He is

currently employed with

Birlasoft, Noida. He can be

reached athttp://twitter.com/jaijeetpandey


29/32


Interview with Vipul Gupta

In this section, we will publish interview withSoftware Testing professionals in every issue. In thisissue Vipul Gupta has shared his ideas about softwaretesting and how he sees future of software testing. Editor

Q: How long have you been associated withsoftware testing?A: Twelve years

Q: How did you become a software tester?A: Since the beginning I have taught myself:Testing is tough, if it was easy developerswould do it. In the initial days I was asked tobe a developer, but I remained steadfast onbecoming a tester. So, it was more of a choicethan circumstances.

Q: By any means, do you regret being associatedwith software testing?A: No way. It is the only stream that enablesdelivery of better and reliable software,irrespective of underlying technology.

Q: Do you think software testing is lessrespected than other departments in ITindustry?A: It is actually incorrect to blame others forthe state of testing/tester in any organisation.If a tester or testing team is bringing value tothe organisation in terms of their businessneeds, no one would ever dare to underplaysoftware testing. Till date, I have been lucky tobe associated with companies that value theirtesters.

Q: What will you suggest to people who want tojoin IT industry as software testers?A: Testers play a very important role in any product team. My suggestion for aspiringsoftware testers is to imbibe the right mix ofbehavioural and technical skills. The technicalskills (viz. OS, programming languages,

Name Vipul GuptaOrganization Impetus

(www.impetus.com)

Role/Designation Sr. Test

Architect

Location NOIDA, India

Vipul Gupta leads the Test

Engineering R&D at Impetus

Labs.Vipul is an activecontributor to various online

testing forums and a regular

speaker at testing conferences in

India and the US. He loves to

spend time with his four- year-

old son and learn from him.

Email ID [email protected]

Blog/Site

https://vipulgupta1.wordpress.com

Twitter URL

http://twitter.com/vipsgupta


30/32


architecture) will help them understand, design and execute the right set of testcases for the system under test and the behavioural skills (viz. attitude,communication and compassion) will earn them respect in the team.

Q: Where do you see software testing in next five years?A: Software testing is here to stay but will be more challenging in the days to come.

Continuous integration, Mobile platform and Cloud have already started demandingchange in existing testing solutions. Companies need more comprehensive solutionsthat can take care of their end-to-end testing needs. Open source will play a pivotalrole in supplying the tools to meet these demands. Apart from it, developers andtesters will also need to collaborate more effectively so as to ensure the right areasare getting tested.

Q: What qualities will you look for in a candidate when you want to recruit someonefor software testing job?A: With technical skills I also look for passion towards testing, Ideas developedthrough practical thinking and eagerness to learn more.

Q: Your weekend routine?A: My weekends are mostly lazy from work perspective and are driven by my familyswishes. Be it Cinema at a nearby mall, cartoons at home or a long drive to some niceplace near NCR, it helps me recharge myself for the upcoming week.

Q: Movie you would like to watch again?A:Avatar

Q: I am a social networking site geek Or I hate facebook /orkut / twitter?A: I think it will be incorrect to call me geek over here. I useTwitter/facebook/linkedin in my leisure time to connect with my friends and to keepmyself abreast with the latest changes in the world around me.

We are inviting at least one representative from each IT

organization where testing is practiced as an independent activity

different from development. These TCRs will help us in bringing inmore testers to Testing Circus; to read, contribute and to share

knowledge on software testing. We will publish a list of TCRs in this

magazine. Write to us ([email protected]) with your

organization name and location. Our team will contact you to work further in this

area. Independent test consultants and freelance testers are also encouraged to apply.


31/32


"Testing Circus" is being published with help from number of professionals who are

working in Software Testing field. We got overwhelming responses to our initial

campaign and the first edition of this magazine. However, we need more support to

continue to publish this magazine. Here is how you can associate with this mission. We

need people in four categories.

Content Author - You can contribute original article written on software testing.

A group of testing professionals will review the content and approve for

publishing in the e-magazine.

Campaign Champion - You can also become a campaign champion by informing

about this e-magazine to the testing community.

Tech Team - You can help us managing the technical aspects of creating the e-

magazine, maintaining subscriber base and helping on us on websites etc.

TCR You will represent your organization to Testing Circus. You will help us

bring in more testers to Testing Circus to share their experience.

Simply write a mail to [email protected] mentioning your willingness to work

with us. For TCR, write to us at [email protected]

We would like to thank Jaijeet Pandey, Naresh Bisht and C. Nellai Sankar who

continued to help with by contributing regular feature in this magazine. We arealso thankful to Anjali Gupta for helping us in campaign activities and for

providing page fillers. Other article writers Rob van Steenbergen, Pramod Kumar

Thank you for your valuable contents. We would also like to thank Steven

Machtelinckx for allowing us to republish the list of 100 Software Testing blogs.

Lots of people viz. Kumar Gaurav, Ish Tripathi, Ravi Chauhan, Anuj Batta, Shivani

Sharma, Vivek Joglekar who helped us to publish this magazine by some means

or other. We are thankful to all of them.

Our special thanks to Vipul Gupta, Sr. Test Architect Impetus for allowing us to

publish his interview in this issue. Thanks to Vipul Kocher and Pradeep

Soundararajan for their encouraging words. Your opinion and guidance are

important to us.

Last but not the least. Ajoy Kumar Singha Founder and Editor of this magazine

would like to thank his wife and son who sacrificed their personal time and

attention and helped him work on this magazine.


32/32

Send in your articles for our next issue to the [email protected]

www.TestingCircus.com

http://www.Twitter.com/TestingCircus

http://TestingCircus.blogspot.com

Volume 1 - Issue 2 October/November 2010

The contents published in this magazine are copyright material of respective authors. Testing Circus does not hold any

right on the material. To republish any part of the magazine permission need to be obtained from respective authors.

Documents

Testing Circus Vol1 Issue2 October/November 2010