Testing Circus

Volume 1 - Issue 2 – October/November 2010

 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

Your Monthly Magazine

on
Basics of Software Testing
 Testing Circus
Volume 1 - Issue 2 – October/November 2010

Help 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 of Testing Circus to donate generously for this purpose. Let’s 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.

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

 Installation

4 Editorial
5 Emails to
the Editor 7 Testing -
why &
how?

Top 100

12 Acceptance
Testing 16 Software
Testing
Blogs
19 In Lighter
Moods

29 Tips to
20 Promote
Testing
22 Testers
@Twitter 24 Test Case
Practice

Software Know Your

26 Testing
News
28 QTP Code
Corner 29 Testing
Guru

Testing
Testing
30 Circus
Reps
(TCRs)
31 Circus
Champions 32 Next Issue

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

The first issue of Testing Circus was received with warm
welcome 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 give
you 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 more
writers 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 don’t 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

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

First of all I would like to congratulate your efforts and the devotion that you have
shown for publishing this magazine. I really liked this magazine specially being a
software tester I needed this kind of stuffs which not only help me in building a good
career 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 a
tester 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 Testing
Circus. Though I have less experience in this industry still I feel I can be a part of this
family and will contribute till I remain associated and even further in future.
~Rahul Srivastava
Calsoft Pvt. Ltd.

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

It is a wonderful start up. No words to say... I’m 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 Bug
Reporting & Agile Testing.
~Anshu Jain

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

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

I really enjoyed reading your first edition of "Testing Circus." I work for Sogeti USA, a
consulting company in Cincinnati, OH, and have been involved with software testing
for 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. Let
me know if I can help, and keep up the good work!
~Matt Riley
Sogeti 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 - manual
and 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 that
article.

I have taken a deep dive into the Testing Circus magazine and it gives me immense
pleasure to see such intelligent initiative by Indian Testers. I have been regular reader
of Software Testing Club Magazine (STC) and am really impressed to see our Indian
fellows 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 Bhamare
TCS – 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 community
requires knowledge from testers like you.

Congratulations to Shyam Sundar Mahalingam, Paul

Oakes and Prashant Tewari for correctly answering the
puzzle published in our September Issue.

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

 By Pramod Kumar

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 of
software 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 run
installation of same
version the software gives
option to uninstall, we
should test this scenario
too.

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

 3. Upgrading of platform (OS) on which software is iinstalled
nstalled
nstalled:: This is rare one;
comes into picture when a new OS is launched in market having option to
upgrade from previous OS version. Suppose, client is using OS as XP and
software is installed on it. Now new version of OS (Vista) is released into
market a
and
nd client system need to upgrade from XP to Vista. In this scenario, we
need to test that after OS is upgraded to Vista, the software is still running as
expected. If not, then we will need to provide patch to fix the same.

4. Un
Un--Installation
Installation of Software: This
his is also important part of installation testing.
In this scenario we test that after un un-installation
installation all the file which were
created on the system got removed or not; registry entry are removed or not;
shortcut created during installation is removed or not; in other words, after unun-
installation system is cleaned/fresh or not.

Mode of installation -

1. Installation from CD/DVD: when installing software from CD/DVD drive by using
CD/DVD
2. Installation from Dumps stored in hard drive: when installing software from
files kept in HDD in the same machine
3. Installation from network: when software dumps is kept at different system on
network and installing from remote location
4. Silent installation:
 Pushing software in network through SMS; in this scenario network
administrator
administrator push
piece of software to all
or selected system. This
is called silent
installation because in
this installation GUI
wizard does not appear
and installation
happens with default or
pre selected settings.
pre-selected
 Or can be installed
without GUI install
installation
ation
wizard from the same
system.
5. Installation from website
(online): These days, lots of software dumps are available online. The software
gets downloaded to temporary folder and is installed run time. This option also
needs to be tested.

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

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 option
like 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 following

points:

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?

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

 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 that’s 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, doesn’t have write permission for the machine, how
installation 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?

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

 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.
Pramod Kumar has over 4 31. Check to ensure that license key is
properly stored in Windows Registry library.
years of experience in
32. Check to ensure that if an evaluation
Product Testing which
version is installed, then a proper message
includes two and half years
should be displayed when the date of period
in automation testing with is expired for evaluation version with proper
IBM RFT and QTP. He is error message.
currently employed with 33. Check to ensure that, if Windows
HCL Technologies, Noida. Services are installed then it should install
Apart from work he likes in the Services folder of windows directory.
to play football. 34. Check to ensure that if any product
is installed and it is dependent on some
other product, then it should give proper
Pramod can be reached at message as "The Product is not installed and
https://twitter.com/pramodkrnitdgp 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 doesn’t 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.

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

Acceptance Testing
In engineering and its various sub-disciplines, acceptance testing is black-box testing
performed on a system (e.g. software, lots of manufactured mechanical parts, or
batches of chemical products) prior to its delivery. It is also known as functional
testing, 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 often

distinguished from acceptance testing by the customer (the user or client) prior to
accepting transfer of ownership. In such environments, acceptance testing performed
by 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 main
testing process.

Overview
Acceptance testing generally involves running a suite of tests on the completed
system. Each individual test, known as a case, exercises a particular operating
condition of the user's environment or feature of the system, and will result in a pass
or fail, or Boolean, outcome. There is generally no degree of success or failure. The
test environment is usually designed to be identical, or as close as possible, to the
anticipated user's environment, including extremes of such. These test cases must
each be accompanied by test case input data or a formal description of the
operational activities (or both) to be performed—intended to thoroughly exercise the
specific case—and a formal description of the expected results.

Acceptance Tests/Criteria (in Agile Software Development) are usually created by

business 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 any
sprint/iteration. These tests are created ideally through collaboration between
business customers, business analysts, testers and developers; however the business
customers (product owners) are the primary owners of these tests. As the user stories
pass their acceptance criteria, the business owners can be sure of the fact that the
developers are progressing in the right direction about how the application was
envisaged to work and so it's essential that these tests include both business logic tests
as well as UI validation elements (if need be).

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

Acceptance test cards are ideally created during sprint planning or iteration planning
meeting, before development begins so that the developers have a clear idea of what
to develop. Sometimes (due to bad planning!) acceptance tests may span multiple
stories (that are not implemented in the same sprint) and there are different ways to
test them out during actual sprints. One popular technique is to mock external
interfaces 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 user
story 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 acceptance
test script to direct the testers. Then the results obtained are compared with the
expected results. If there is a correct match for every case, the test suite is said to
pass. If not, the system may either be rejected or accepted on conditions previously
agreed between the sponsor and the manufacturer.

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

A principal purpose of acceptance testing is that, once completed successfully, and

provided certain additional (contractually agreed) acceptance criteria are met, the
sponsors will then sign off on the system as satisfying the contract (previously agreed
between sponsor and manufacturer), and deliver final payment.

User acceptance testing

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

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

Test designers draw up formal tests and devise a range of severity levels. It is
preferable 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 some
situations where this may not be avoided. The UAT acts as a final verification of the
required business function and proper functioning of the system, emulating real-world
usage conditions on behalf of the paying client or a specific large customer. If the
software works as intended and without issues during normal use, one can reasonably
infer the same level of stability in production. These tests, which are usually
performed by clients or end-users, are not usually focused on identifying simple
problems such as spelling errors and cosmetic problems, nor show stopper defects,

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

such as software crashes; testers and developers previously identify and fix these
issues 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 will
perform in production. There may also be legal or contractual requirement for
acceptance of the system.

Q-UAT - Quantified User Acceptance Testing

Quantified User Acceptance Testing (Q-UAT or, more simply, the Quantified
Approach) is a revised Business Acceptance Testing process which aims to provide a
smarter and faster alternative to the traditional UAT phase. Depth-testing is carried
out against Business Requirement only at specific planned points in the application or
service under test. A reliance on better quality code delivery from Development/Build
phase is assumed and a complete understanding of the appropriate Business Process is
a pre-requisite. This methodology if carried out correctly results in a quick turnaround
against plan, a decreased number of test scenarios which are more complex and wider
in breadth than traditional UAT and ultimately the equivalent confidence level
attained via a shorter delivery window, allowing products/changes to be brought to
market 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 quality
safeguards 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 Acceptance
Testing which was itself a response to testing phases which proved too costly to be
sustainable 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 story
by the software development team during the implementation phase.

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

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

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

Types of acceptance testing

Typical types of acceptance testing include the following

User acceptance testing

This may include factory acceptance testing, i.e. the testing done by factory
users before the factory is moved to its own site, after which site acceptance
testing 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 to
a 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-up
facilities, procedures for disaster recovery, training for end users, maintenance
procedures, and security procedures.
Contract and regulation acceptance testing
In contract acceptance testing, a system is tested against acceptance criteria
as documented in a contract, before the system is accepted. In regulation
acceptance testing, a system is tested to ensure it meets governmental, legal
and safety standards.
Alpha and beta testing
Alpha testing takes place at developers' sites, and involves testing of the
operational system by internal staff, before it is released to external
customers. Beta testing takes place at customers' sites, and involves testing by
a group of customers who use the system at their own locations and provide
feedback, before the system is released to other customers. The latter is often
called “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 Source http://en.wikipedia.org/wiki/Acceptance_testing

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

 By Steven Machtelinckx

# Site Author URL

1 James Bach's Blog James Bach http://www.satisfice.com/blog
2 Testing at the Edge of Matt Heusser http://blogs.stpcollaborative.com/matt
Chaos
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 Kaner’s Blog Cem Kaner http://www.satisfice.com/kaner
8 Miško Hevery Miško 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 Through Brian Marick http://www.exampler.com/blog
Example
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 Software Jonathan Kohl http://www.kohl.ca/blog
Testing
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

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

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 Marlena’s Blog Marlena Compton http://marlenacompton.com/
39 Software Testing and Ewald Roodenrijs, http://www.testingthefuture.net/
more Andréas Prins
40 patrickwilsonwelsh.com Patrick Wilson-Welsh http://patrickwilsonwelsh.com/
41 Quality Assurance and ( various ) http://quality-assurance-software-testing.blogspot.com/
Software Testing
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/blog
48 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 Reddy http://venkatreddy.in/
Chintalapudi
56 Agile Testing and Process Janet Gregory http://janetgregory.blogspot.com/
Thoughts
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 Software Keith Stobie http://testmuse.spaces.live.com/
Testing
64 Jon Bach's blog Jonathan Bach http://jonbox.wordpress.com/
65 Quardev ( various ) http://www.quardev.com/blog
66 Software Testing Club ( various ) http://blog.softwaretestingclub.com/
Blog
67 TestToTester Sharath Byregowda http://testtotester.blogspot.com/
68 Agile Testing with Lisa Lisa Crispin http://lisacrispin.com/wordpress/
Crispin
69 Confessions of a Dawn Cannan http://www.passionatetester.com/
Passionate Tester

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

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 S’s 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 of Jeroen Rosink http://testconsultant.blogspot.com/
Software Testing
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 a Paul Carvalho http://swtester.blogspot.com/
Software Tester
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 and John Overbaugh http://thoughtsonqa.blogspot.com/
Engineering
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 blogs
at http://www.testingminded.com To know more about how Steven has compiled the
above list and ordered them from 1 to 100 and newer addition to the list, please visit
his blog’s post ‘Top 100 Software Testing Blogs’. The list is republished in Testing
Circus with his written permission. Enjoy and Happy Reading. – Editor

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

http://geektester.blogspot.com/2010/07/software
http://geektester.blogspot.com/2010/07/software-testing
testing
testing-stage
stage
stage-act
act-funny.html
funny.html

A tester saw an UFO last night, when he told this to

developer in the morning, he asked him to reproduce!

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

 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. Don’t have a bug’s 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 organization’s 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.

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

 18. For managers: put the focus on the process not the product, we need someone
to watch the process, including the testing process.
Rob van Steenbergen from the
Netherlands is an independent
software test consultant and has
14 years of experience as a
software tester in miscellaneous
areas.
In the last 4 years he has been
involved in infrastructure
projects and is working now on a
desktop virtualization project
where he is testing and
coordinating the tests.
In his leisure time he reads,
listens to lots of music and
watches even more movies. His
twitter account, weblog and
other links can be found at
his website
www.chickenwings.nl
defects have you found on time?
29. Create a roadmap how to get test consciousness into your organization
(communication planning).
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 could
be 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 marketing
for your own work. What and how many

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

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

 @

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 followers
16 listed
http://twitter.com/MichelKraaij

Shrini Kulkarni
BIO: Software Testing Generalist, Systems thinker, Skeptic
75 following
511 followers
51 listed
http://twitter.com/shrinik

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

 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

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


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. Steps to Execute
No.
1 Examine for size of stapler
2 Examine the weight of stapler
3 Examine the color of stapler
4 How easily can you hold it in
hands? Is it compatible with
your fingers?
5 Staples should fit in the stapler.
6 Verify that it can staple
perfectly?
7 Verify that the spring is pushing
the staples freely as desired?
8 Verify that the last pin can
staple without any problem?
9 Does the stapler indicate when
the staples are empty?
10 Verify that the stapler can
staple a bunch of papers
(ranging from 5-10)?
11 Verify that the stapler can
staple card boards?
12 Put 2 bunch of stapler pins to
check the spring is able to take
the load
13 It is working fine with a
standard bunch of pins.
14 Size of the pins required
www.TestingCircus.com
By Naresh Bisht
Expected Result Actual Remarks
Result*
It should be 176.28 mm wide
Stapler should weigh .5 lbs
and/or 230 grams
It should Blue in color
Proper grip to hand and
smooth to fingers
Space for staples should be
proper not large or small
It should staple perfectly on all
kinds of paper
Spring should not be very tight
to the stapler pins
Last pin should not create any
problem to staple
It should indicate that the pins
are empty.
It should staple perfectly for
bunch of papers
It should not fail to staple card
boards
It should able to take the load
for two or three bunch of
stapler pin
Maximum limit should easily
take load of three bunch of
pins
Standard size should taken by
stapler
October/November 2010 - 24 -
15 Check whether the spring runs It should properly work for all
properly conditions
16 Check whether the next pin Next pin should load
should aut
automatically
omatically load in automatically and user should
place of previous pin be able to staple
17 Staple all the pins and check It should work fine till last pin
that till last pin it should staple and stapler should not jamb
fine. after the last pin’s use.
after
18 Does the stapler open 180 It should open in 180 degree
degrees for inserting/removing
pins?
19 At what temperature does the Temperature resistance should
plastic cover melt? At what cold be as per requirement.
temperature does the stapler
cease to function (springs, rear
pivot,
vot, etc)?
20 Try to insert staples which are Staples should not be inserted.
in larger size?
21 Does the stapler break and It should not break and it
cease to work after dropping it should work properly.
from 1st or 2nd floor?
22 Check the brand name and Brand name and country of
country of manufacture of the manufacture should be
stapler engraved on the body of
stapler
*Actual Results are written when you get to test the actual sta
aple
er.

In this section we will practice to write test

cases on various items, objects and applications.
We do not claim that test cases written here are
exhaustive. It is just to give ideas to testers,
beginners on how to approach for writing test
cases. Re
Readers
aders are encouraged to share their
views on the test cases.
– Editor

Face Book Addiction

Naresh Bisht has 3 years
experience in Software Dad writes on Son's wall….
Testing. He is currently “
“Son,
Son, how have you been?
employed with HCL Your Mom and I am fine.
Technologies, Gurgaon. We miss You a lot.
We wish to see you.
Naresh can be reached at
http://twitter.com/Naresh_Bisht
So please turn off your PC and
Come downstai
downstairs
rs for Dinner
Dinner.”
.”

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

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 technology
testing 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 nuclear
technologies.

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

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

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 to
100 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-conference
workshops 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 and
experiences 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.

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

 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.
Jaijeet Pandey has over 5
years of experience in Single function to get the date in different format
Application Development, dformat("a",b)
Maintenance and Testing. Where
From more than last 3 years parameter a denotes the date
he is involved in automation parameter b denotes the type of format from the below list
testing with QTP and Load 1. November 3, 2010
Runner tools. He also teaches 2. 3 November, 2010
QTP on weekends. He is 3. 3 Nov, 2010
currently employed with 4. 3-Nov-2010
Birlasoft, Noida. He can be 5. 11/3/2010
6. 3-11-2010
reached at
http://twitter.com/jaijeetpandey 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

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


Name – Vipul Gupta
Organization – 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 active
contributor 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 – vips001@gmail.com
Blog/Site –
https://vipulgupta1.wordpress.com
Twitter URL –
http://twitter.com/vipsgupta
www.TestingCircus.com
Interview with Vipul Gupta
In this section, we will publish interview with
Software Testing professionals in every issue. In this
issue Vipul Gupta has shared his ideas about software
testing and how he sees future of software testing. –
Editor
Q: How long have you been associated with
software 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 developers
would do it”. In the initial days I was asked to
be a developer, but I remained steadfast on
becoming a tester. So, it was more of a choice
than circumstances.
Q: By any means, do you regret being associated
with software testing?
A: No way. It is the only stream that enables
delivery of better and reliable software,
irrespective of underlying technology.
Q: Do you think software testing is less
respected than other departments in IT
industry?
A: It is actually incorrect to blame others for
the state of testing/tester in any organisation.
If a tester or testing team is bringing value to
the organisation in terms of their business
needs, no one would ever dare to underplay
software testing. Till date, I have been lucky to
be associated with companies that value their
testers.
Q: What will you suggest to people who want to
join IT industry as software testers?
A: Testers play a very important role in any
product team. My suggestion for aspiring
software testers is to imbibe the right mix of
behavioural and technical skills. The technical
skills (viz. OS, programming languages,
October/November 2010 - 29 -
architecture) will help them understand, design and execute the right set of test
cases 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 demanding
change in existing testing solutions. Companies need more comprehensive solutions
that can take care of their end-to-end testing needs. Open source will play a pivotal
role in supplying the tools to meet these demands. Apart from it, developers and
testers will also need to collaborate more effectively so as to ensure the right areas
are getting tested.

Q: What qualities will you look for in a candidate when you want to recruit someone
for software testing job?
A: With technical skills I also look for passion towards testing, Ideas developed
through 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 family’s
wishes. Be it Cinema at a nearby mall, cartoons at home or a long drive to some nice
place 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 use
Twitter/facebook/linkedin in my leisure time to connect with my friends and to keep
myself 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 in
more 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 (tcr@testingcircus.com) 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.

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

"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 editor@testingcircus.com mentioning your willingness to work

with us. For TCR, write to us at tcr@testingcircus.com

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 are
also 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.

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

Send in your articles for our next issue to the editor@testingcircus.com

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.

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