Testing Circus Vol5 Edition03 March 2014

8/12/2019 Testing Circus Vol5 Edition03 March 2014

1/56

TestingCircusVolume 5 - Edition 3 - March 2014

Your Monthly Magazineon

Software Testing

with

Smita Mishra

www TestingCircus com


2/56

ArticleSubmissionGuidelines

Do you have something to share with the

testing world? We can make your voice

heard to testers.

http://www.testingcircus.com/article-submission-guidelines

Article submission guidelines Subject of article can be based on any area of Software Testing. If you want to publish your article on

theme based subject please read our announcement of monthly theme published in our site. Articlecan be submitted without any theme based subject.

There is no minimum and maximum length of article. If you feel the article is lengthy, please dividethe article into logically separated parts so that we can print them in a monthly series.

Give a meaningful title to the article. If you want a sub-title as well , then add that in a different line.Add images/pictures if necessary. If you are using any image/picture which is not yours own work,

please include the source. Take care of copyrighted materials. Images need to sent separately with thearticle.

Send us the article in MS word (doc/docx) format only. Pdf files are not accepted.Write a short write up on the author(s). Usually 7/8 liners in 3rd person descriptive language.Include photograph of author(s). Preferred in high resolution .jpeg/.png format. Ideal size would be

50mmX 50mm.You can send your article any time. Since we publish every month, your article can be included in any

month. There is no such thing called as a dead line.Send in your article to [email protected] with a subject line Article for Testing Circus

Author Name Title of the articleIf you think you can write a column in Testing Circus for at least 6 months, please submit 3 articles in

advance. We are open to any idea that may improve the user experience of Testing Circus.We will publish the articles in our website a week after the pdf magazine is published.

www.TestingCircus.com March 2014 - 02 -


3/56

is

w

?

Testing Circus Volume 5 - Edition 3 - March 2014Topic

Interview with Smita Mishra

Examples of Testable Requirements

Taking Testing to the Cloud

A Common Pitfall of Test Cases

Mobile Testing on the Cloud

How Quicker can mean Slower

7 Types of Testers - What is your identity

Book Review - Dont Hire the Best

A Fake Testers Diary, Part - 39

Testers to Follow

Test Environment for Security Testing

Running Webdriver Script on a VM

Test Automation: New Venues, New Challenges

TestComplete Support For Automated Mobile Testing

Author

Jay Philips

Ulrika Park

Vipin Jain & Anubha Jain

Raj Subramanian

Gagneet Singh

Peter Morgan

Arslan Ali

WoBo

Fake Software Tester

Editorial Team

Santhosh Tuppad

Mihai Sarlea

ToolsJournal.com

ToolsJournal.com

Page #

5

10

14

22

23

25

27

31

33

35

37

39

48

50

Squish Coco Supports Code Coverage Of C# & Tcl Code ToolsJournal.com 52

Testing Events Around the World TestEvents.com 53

Testing Circus Team

Founder & EditorAjoy Kumar Singha

Team-

Srinivas KadiyalaJaijeet Pandey

Pankaj Sharma

Bharati Singha

Chanderkant Saini

Dwarika Dhish Mishra

Editorial Enquiries:[email protected]

Ads and Promotions:[email protected]

Testing Circus India

Chaturbhuj Niwas, 1stFloor,

Sector 17C, Shukrali,

Gurgaon - 122001

India.

Copyright 2010-2014. ALL RIGHTS RESERVED. Any

unauthorized reprint or use of articles from this magazine

is prohibited. No part of this magazine may be reproduced

or transmitted in any form or by any means, electronic or

mechanical, including photocopying, recording, or by any

information storage and retrieval system without express

written permission from the author / publisher.

Edition Number : 42(since September 2010)

*On the Cover Page - Smita Mishra www.TestingCircus.com March 2014 - 03 -


4/56

From the Keyboard ofEditor

esting Circus is three and half years old. This magazine has been running on

olunteer effort, assisted by few passionate testers from time to time. It has been an

mazing journey so far. But, like all other good things in life, it is coming to an end.

We are announcing discontinuation of Testing Circus after this edition.

is a sad moment for all of us. Running a regular magazine purely based on

olunteer effort is hard task, specially when all volunteers including me have full

me jobs to look after. We were always supported by many testers by contributing

ome awesome articles but let me also admit that it is always a challenge to gather

ood articles when you dont pay the writers and busy testers do not reply to your

mails and direct messages. There was too much effort for our volunteers.

esting Circus site will remain as it is. We will continue to publish our old articles

n the site. We will continue to promote good testing stuffs in Facebook/Twitter. But

ur regular monthly magazine will stop.

would like to thank all you of you who supported us in this wonderful journey. We

ill cross the roads again.

ill then, stay hungry, stay foolish and test passionately.

-Ajoy Kumar Singha@TestingCircus// @AjoySingha

Write to us at [email protected]

www.TestingCircus.com March 2014 - 04
https://twitter.com/ajoysinghahttps://twitter.com/ajoysinghahttps://twitter.com/ajoysingha


5/56

SMITAMISHRAInterview with Teste

Organization: QAZone Infosystems Pvt Ltd

Current Role/Designation: Chief Test Consultant & CEO

Location: New Delhi, India

Smita Mishra is the founder and chief consultant at QAzoneInfosystems, which is a pure-play software testing organization. She is

a first generation Entrepreneur and is a Test professional who has

spent over 12 years practicing testing and leading test efforts of

varying sizes, cutting across all key domains and technologies. In the

past, she has worked with multiple organizations, likes of - HCL

Technologies Ltd, Fidelity Investments, Nucleus Software Exports Ltd,

Churchill Insurance (Now RBS).

In her current role, she is involved in creating test teams, managing

testing for software companies, leading the overall test strategy for

them. She is also engaging constantly with different forums to assistgrowth for women in her field and women in general too.

* Interviewed byJay Philips

1. Tell us about your journey to becoming a software 2. When did you realize your passion was software

tester. How did it start and how this has been so far? testing?

Was it planned or by accident? I would be wrong if I said that it was love at first

My journey to become a good tester still continues. sight. It was not. But as they say good music grows

However, it began in 2001, with my first job at on you even if you dont like it much in the first go.

Nucleus Software Exports Limited, where I was It was similar in my case. I realized I enjoyed testing

campus placed after my engineering. A batch of early in my work life. But it wasnt until 2006 that I about 20 engineers were picked from across the began to love it. I attended the first conference in my

nation and put together as the founding life it was a QAI conference where I was presenting

(independent) test team. Honestly, I had no a practice paper on estimations. Met many testers

introduction to Testing until then other than the there and I loved the feeling of belonging to a

few chapters I read on SDLC, Verification and community too. Then in 2007 I went to work in GE

validation in a book of software engineering by Healthcare account under the most dynamic

Roger Pressman. It was planned by my employers technology leader and sharp as razor Gazanfar

not me but wasnt really an accident. Once in testing, Hakeem and an excellent Test Manager Smita Sethi

I quickly began to learn it and found it interesting. (who also happens to be a very sharp professional). I

I will agree that though I really enjoyed my work, got exposed to very technical testing in DW-BI (ETLthe initial years were nothing exciting. But over the Testing) and performance testing of these ETLs and

years, I realized that I enjoy testing more than implementing lean methodology. I would term that

anything else. There have been tremendous learning as the turning point in my career on how I began to

through the 13 yrs spent in the field. The more I look at my testing career. I realized I was cut out to

learn the more I see I have yet to learn. do this.

Hence, I can easily say that the journey so far has

been terrific. 2014 seems to be extraordinarily good3. Do you regret being associated with software

year for me and I am loving every moment of it, as atesting today? Given a chance would you move from

test professional. testing to any other field in IT?



6/56

SMITAMISHRA

No, clearly no. Quietly no. Loudly no. Simply no.I am proud to be a part of an ever evolving field and

that has a huge legacy of achievers. I can easily say I

never had second thoughts about my work. Also, I

would find it very difficult to work on a single

technology or domain all my life and to look

conversely at it - which other field can give me so

much exposure in understanding what really

matters in IT field, while keeping me hands on with

We had planned for a conference ThinkTest 2013,which would have been the first of our initiative in

this direction. We were very keen to bring James

Bach to this part of India (and we still want this to

happen). Unfortunately, due to unforeseen

circumstances at my personal end and not having

suitable alternatives, we couldnt take this forward.

We will keep the test community updated of future

plans related to this.

all latest technology.

6. In February 2014 you held the first meetup for Test4. What does QAZone do? How are its services

different from the services offered by other similar

organizations?

QAZone is a pure play software testing organization

that offers Testing solutions and services, Test

consulting, Test training and test support services

(Test data management, test environment setup). We

offer Business as usual testing as well as specialized

testing. We have built a client base of over 20 clients

in last 3+ years.

Our business focus is our key differentiator. Our

testing solutions are designed to work for your

business. We look at technology as a platform to

make business happen. All our testing has a

component of domain focus which becomes a very

serious need of our clients when we are dealing with

regulated environments like Aerospace and

Healthcare.

Our next differentiator is that against the trend - we

believe in hiring locally, even if it means training

potential resources at our expense. For example anytime we need a resource in US, our first approach

is to find a resource locally. This has so far proven to

be a very fruitful approach.

Practitioners Club. What made you want to create

this meetup?

It always feels easier to work with people whom you

have met and can relate to them as a face and as the

vibes you share with them. All leading test

conferences are still physical conferences not

webinars. Thats because learning happens in many

forms today and one of them is networking post

conferences. With the thought of building a network

of co-learners, we created a LinkedIn group Test

Practitioners Club and planned for its meet-ups that

would help local testers to learn more from each

other and get introduced to global platforms too. If

we could we would have such test meetups all

over the country. We are planning to do one meet

every month at the very least. We will keep posting

the updates from our meets at my blog, for all to

read.

7. I noticed that you are certified in ISTQB and QAI

(CSTE). What made you decide to go for bothcertifications?

Yes, thats true I have indeed done both the

certifications. I went for ISTQB (in 2005) because

until then I had no certifications. And under our

5. Last year you organized a conference calledtraining and development program, my organization

ThinkTest in India. Was that the first year of thepaid for this certification. However, later on I went

conference? What were some key sessions andfor QAI (CSTE), as it was not widely done so far due

feedback? to its cost and students failing in it and this made it



7/56

SMITAMISHRA

appear more respected and challenging. I paid for10. What qualities will you look for in a candidatethis one myself. when you want to recruit someone for software

testing job?

8. Do you recommend that all testers get bothI like to work with enthusiastic people who enjoy

certifications? Are there any other certifications youlearning new things and working on new areas. This

would recommend to other testers? is true not just for software testers but front office

I would let testers decide this for themselves. But I executive, accountant, HR and Admin folks - all of

can say it with reasonable confidence that these them.

certifications do not prepare testers to handle serious Many today do not feel the need to look at the past

testing problems. I enjoy being part of miagi-do and experience and hire only for attitude. However,

discussing actual test issues with real testers there when I am hiring testers particularly I like to seeand how to resolve them. I have heard very good the kind of work they have done before and like to

things about BBST and most of the leaders I follow hear their stories of projects on exactly what was that

are associated with it. I would suggest all testers to they were testing and what were the key defects

atleast go through the content and format and decide found. What was their approach and the key

for themselves. challenges faced and how did they bring up the

If learning is the objective and certification is not challenges to the notice of relevant stakeholders and

really the goal, I would suggest testers to go through how did they do the contingency or mitigation as

James Bachs site for RST classes and RTI (online) applicable.

classes. Formally speaking, we have 2 set of patterns one

for freshers and other for lateral hiring.

9. According to you, what is lacking in todays For laterals particularly - We have a process that

commercialized training industry, especially inhelps us map the required technical skills with the

testing? available resumes. So, anytime we have a need we

With all due respect to the 2 certifications I did, I look into our database of testers who have applied

believe an ideal test certification would be one which with us in past and from the matching resumes, we

would have more practical problems to deal with, as shortlist based on availability / joining time and

tests for their students and would involve real life expected compensation. Post this, we share certain

situations of testing than focusing on glossary of project links with these potential candidates and

testing and terminologies. Also, I would invest in expect them to submit us their Bug Reports in a

domain led testing certifications for my team. So far, given time frame. Finally, after a candidate is found

there are no such certifications available which technically suitable, we setup face to facewould certify testers for regulated environments like interactions to evaluate more HR aspects and general

those of aerospace and healthcare. I have heard of a communication.

new certification that Cem Kaner has come up with. I For freshers, its really about what they have to offer

need to look into that one too, if it has domain based beyond their formal education. No firm expectations,

testing certifications. as long as they are able to convince us of them being

fast learners and having aspirational attitude, they

might.



8/56

SMITAMISHRA

11. What will you suggest to people who want to joinIT industry as software testers?

I am very happy to be part of the software testing

community. And I can only suggest the new folks

that learn what is testing and then get into it. I find

people to be doing testing for all the wrong reasons

like its easier that Development, it doesnt need

coding, timelines are easier and hence the work

pressure, etc. None of this is true. Testing is

becoming as challenging as any other part is with the

ever evolving IT andWhen I look back, I think the biggest gap that I see

during my initial work tenure was how closed and

we were in our approach to testing. working in silos

as a closed group and not being exposed to the

whole world full of knowledge and awesome

teachers and trainers willing to invest time in you.

12. Name few people you would like to thank,people who helped you directly or indirectly in your

career as a software testing professional.

I would like to thank my family for always standing

by me ALWAYS. But a special mention of my son

At work front there are too many names and I wouldlike to thank each good and bad interaction, because

it has helped me grow in one way or other.

Everyone I know Thanks for being part of my life.

13. One last question Do you read Testing Circus

Magazine? If yes, what is your feedback to improve

this magazine?

Yes, I do read Testing Circus Magazine. I first heard

about it in 2010 I guess when my manager Akash

had been invited to be interviewed in it. But I neverfollowed it then. I began to read Testing Circus since

sometime in 2013 onwards.

I liked the original format of the magazine. But the

new format is truly amazing. I really enjoyed the

editions coming out in 2014. And I think they are

doing all the right things to get noticed and to put in

right content. My only words will be continue the

good work.

And maybe you can cover small meetups and group

test events happening across the globe as a regular

column. This could help other meetups to learn what

more can be done and how to be effective.

here for being the worlds most loving and caring

son and being very understanding when his mommyBlog/Site: http://smitamishrablog.wordpress.com

needs to work. Twitter ID: @smita_qazone



9/56

http://www.testmilem


10/56

Requirements People Need

Your Help!

Examples of Testable Requirements

- Ulrika Park

The simple thing is this - write your requirement as a date format etc but good developers generally can

test. With defined inputs and outputs. Expected results make some good micro-requirements decisions.and expected (and unexpected) data.

For the everything in between requirements, we hav

If you do this, your life will become bright, shiny, and a lot of work to do to make them testable. From what I

you will live happily ever after. Or at least your soft- know it seems as there are mainly 3 ways of communi-

ware will become much much, much more reliable. cating requirements today.

And youll probably find out a lot of things about your

ideas before youve invested in building unnecessary Either youre agile and have a loosely defined prod-

features and details. uct backlog, filled with short user stories and then not

so much more information.

You can do this with high level requirements, such as

business goals and overall objectives, as well as with Or you have a heavy regulated requirements process,

low level isolated features, and everything in between. with hundreds of pages of use cases or shall-require-

ments. Often with abstract statements such as (from

I think that the everything in between part is where real example): Purchase has generated a receipt

we (software industry people) lacks the most care and

insight about the importance of concrete, testable re- Or the ad-hoc requirements: Lets send an email to the

quirements. developer telling what I need to have. Example: We

need to update the purchasing order receipt page. Rig

When it comes to high level requirements, we may have now it doesnt show the total. The total need to be ther

business people who do follow up business cases & When can this be done?.

objectives, i.e. test the results of the investment, at leastI have seen it done once or twice. As a requirements analysts / project manager I have

seen and practiced a way out of these three abstract,

When it comes to very low level requirements, or mi- ambiguous, non-informative ways of communicating

cro-requirement as my friend@spindelmannecall requirements. Much thanks to developers who serious-

them, TDD do take care of it to some extent. Such as ly cared about taking TDD to the next level, and by

When renaming item x the list will keep the same sort having the chance to work with testers close by who

order. Its hard to separate micro-requirements from taught me how to express what I want as test scenarios.

real business requirements sometimes. What is really

a valid input string here? How should we present the Ill share some examples from a previous project.



11/56

interpreted the target since we dont knowand then

A testable business requirement

I was asked by the business owner to implement a fea-

ture: Cardholders should be able to edit the rights for a

whole household to use the money on their bonus card

Since money and banking was involved, it was a bit

show for those stakeholders I do have access to. Often

do get some feedback on my hypothetical business goa

statement. Even Youre totally wrong in your assump

tion!! is good to know before developing anything. A

you have a reason to ask for answers.

complicated to implement.

Before testing or developing any feature, we have to

My first question to the business owner was: why? and know or make a clear defined assumption about the how will you know it works?

After quite a lengthy conversation, he said that what he

really cared about was that the money on the bonus

account was spent. He didnt want the money to stay on

their bonus cards.

expected result for business.

A testable middle level, user requirement

So now we knew the business goal of the feature. The

feature could be implemented in many ways, with op-

tions from everything from printing and scanning pap

forms to digital authorization functionality.

How can we verify that this target is achieved? I asked.

Well.. he said. If the money is spent, then the feature

works.So.. when in time is realistic that we can check this..?

Well.. within 6 months we should have a better rate of

spending the bonus money than now he said.

Ok. So what do you mean by better?

Hm


12/56

Scenario 1:Give authorization to other cardholder in a

household with only 2 cardholders.

Given that:

Household has 2 and only 2 cardholders

The 2nd cardholder doesnt currently have the right to

use bonus money

Main cardholder has actively selected the 2nd cardholder

The 2nd cardholder is >= 12 years old

Expected result:Information is shown: You have now given authoriza-

tion to with SSN: .

The 2nd cardholder now has authority to use bonus.

The point here is not to give the full picture. For that I

need to write a book :-) The point is to show that by

defining tests while working with the requirement, the

requirement got much more explicit. We saved time fo

our tester, who could focus on exploratory testing whe

time came. We saved a lot of time for developers who

actually got the information ahead development on wh

would be tested, and what rules should be applied, so

they saved a lot of rework.

Also when having conversation with developers about

the examples we modified them a bit, and removed

unnecessary ones, or added missing. Some of the scena

ios could even be quite easily automated while develo

Scenario 3:Authorization process is actively canceled by ing, which also saved us a lot of time.

cardholder

Given that:

Household has 2 and only 2 cardholders

So, what to do as a tester then? If youre just not involv

in creating the requirement definitions? Maybe the re-

The 2nd cardholder doesnt currently have the right to quirements are just handed off to you in one way oruse bonus money another, and when you get them theyrenot testable at

Main cardholder has actively selected the 2nd cardholder all?

and

has entered external digital identification application to One thing you can do as a tester, is to make an effort to

authorize

and

shuts down the digital identification application

Expected results:

be included when other people are working with re-

quirements. Offer your help!

Only once I have been approached by a tester with this

offer!

The 2nd cardholder doesnt have authority to use bonus

Message to main cardholder: The change has been can- Its always me whove approached testers to help me

celed.

These were just two examples. Doing this I had now:

1. A specification that can be used for testing

2. Got forced to find out the exact business rules regard-

ing who actually could be authorized. The age limit, for

instance, was discovered by defining the tests. By defin-

ing test scenarios, I got a foundation to ask the right

questions to domain experts. Can anyone be autho-

rized?

3. A way to at any time go back and show for who itmight concern (developers, stakeholders, customer ser-

vice) what exact requirements and rules we built for.

with making testable requirements.

Have you ever as a tester tried to offer your help and

seriouslytried? To the guys working with requirement

And there are much more efficient ways than to say I

you need me you know where I am.

A tester could say something like this: I know Im

going to work on testing for this project a couple of

months from now. Is it possible for me to see some of t

requirements already now? It will help me get rampedup quicker when Im in the project. Im in another proj

right now, but still I should be able to take one or two

hours to look at what you have. And yeah, incomplete

These are just small examples from a big domain, so I use cases or draft user stories will work fine too!

expect you have a lot of critique Where are scenario x??

And those examples could for sure cover much more! When you do get hold of some kind of requirements

And arent that statement a bit vague? What does ac- early in the process, take a quick look. Try to define some

tively mean really..? simple test cases or scenarios, and maybe you will get

opportunity to discuss these with the requirement ana



13/56

lysts (or whatever role who works with the require-

ments).. Then why not inviting her for a lunch or a

virtual coffee break (or other social excuse) over Skype in

case of distributed teams?

Requirements people need your help! They just dont know it yet. Who, if not you, will seriously invite to

make their work testable?

Ulrika Park is arequirements geek with

a passion for testing,

methods, learning & the

development of prod-

ucts & services within

organizations and

teams.With 15 years of

experience in software

development, management & business

she now works at SmartBear. She believes in the

synergy of people, software and quality thinking

to change the world.



14/56

Taking Testing to

The Cloud- Vipin Jain- Anubha Jain

Look around in various IT companies, flip pages of some IT magazine, read blogs, see forums and you will be

sure to find the todays buzz word, the Cloud. You cannot find a word that has created so much of ripples than

the Cloud. Very dramatically, the thinking process on providing computing resources has been shifted to Cloud

computing. With this shift of focus, a lot of confusion has accumulated along the way in peoples mind.

Companies are taking this concept very seriously. Many have moved to cloud, and those who are still on the

ground are planning to move to cloud in next couple of years.

People are still confused. They still are not comfortable with the Cloud thought. You ask anyone what a cloud

service is and you still wont get a very confident answer. Even ifyou get an answer, ask what benefits they offe

and what are the disadvantages at stake, and you can see the person will be uncomfortable answering this. Mak

him skip the discussion by asking how secure they are, and it will be end of discussion. When it comes to testin

applications, we are not fully sure whether to adopt the cloud approach of testing or not. What are the benefits

we get and what are the hurdles on the way?

Lets take a closer look at the Cloud and how it can benefit out day today testi ng activities.

So what is a Cloud?

Cloud computing is a business and economic model. This model has been successfully deployed and executed

for various material commodities since its inception, but in the recent years it has been formalized for IT produc

and services.

Let me try and explain the basic difference between a Cloud service and a Non-Cloud service.

Consider that you have to move from one place to another. You can use your car OR use the services of a Taxi.Both of these vehicles have several similarities

Both are automobiles, having very similar structure and machinery.

Both provide basic functionality of transferring people / goods from one place to other.

So where lies the difference?

The difference is in the business model for the service provided by them.

When the car is owners, the owner has to pay for the fuel, regular maintenance and even possibly a

garage. In turn, the car provides the service solely to the owner - you.



15/56

When the car is a Taxi, the service provided by the taxi cab can be described as Travel as a service. Who

owns the car and who pays the maintenance is not your concern. As a customer, you just have to pay to

travel from your place to another desired place. No maintenance fees and no parking fees need to be paid

by you. This responsibility lies with the cab driver.

The Cloud is synonymous with

the phrase On Demand. You

pay only on demand (when yo

require it.)

Cloud gained momentum whe

IT industry got associated with

it. Today, we find that there is

huge range of products and ser

ices available on demand. All a

As a service e.g. Games as a

service, Java as a service, Sto

age as a service and the list is

endless.

Fig 1: TaaS or Travel as a service A Metro Cab service

How Testing and Cloud work together?

Cloud-based testing offers a remarkable combination of low costs, pay-per use model and elimination of initial

capital expenditures. The benefits, however, are more than just cost effectiveness. The non-cost factors include

on-demand flexibility, a respite from holding various infrastructure assets, enhanced collaboration, higher levels

efficiency and, most importantly, reduced time to-market for key business applications. Economically the vendor

and end user gets huge benefits from the Cloud. This comes directly from reduced subscription prices of any

product or service.

Other benefits are:

Cloud Apps are scalable : The elastic business model, as it is popularly known as, can be customized

on the requirement

Auto-Provisioning : Depending on needs of end users, various Cloud vendors provide and withe

offerings in a manner which is in an automatic and self-serving format.

Unlimited resources : At least the end user thinks and feels this. Theservices / products are availabl

andwhen they are demanded and in the required quantity

The Cloud computing model should be coined as Green Model as it maximizes usage of resources and minimiz

wastage making it environment friendly.

Current state of testing in cloud

Many companies are still taking a cautious approach with cloud computing. This is not the case with testing

however. They are largely ready for testing in cloud and following reasons will account for that readiness:

As we all know, testing is not a one time, but a periodic exercise and each project will require a new

environment to be set up. If a company creates a Test lab, it typically sit unused for longer periods, result

in a waste of cost, electricity and space. Lots of published reports indicate that more than 50% of the


16/56



17/56

technical infrastructure for testing remains underutilized.

Since testing still being considered as a must but non-critical activity for business, taking testing in cloud

premises is pretty safe as it doesnt include important company data and has minimum impact on the

organizational business activities.

Todays applications are increasingly getting dynamic, more complex, distributed across continents and

more component-based. Testing them is getting more challenging. For instance, with mobile and Web

applications testing, testing needs to be done for multiple operating systems and regular critical updates,

various browsers and their versions, variety of hardware and a large pool of concurrent users to understa

real time performance. It is pretty difficult to follow the age-old approach of creating so many in-house

testing environments. These will become very complex and will need huge capital and resources.

Fujitsu in a 2010 research suggested that testing ranked second (57%) as the most likely workload to be put into t

cloud after Web sites (61%). The on-demand provisioning by Cloud addresses all the above explained issues wit

one click. On top of it, the effort and resources saved by using cloud can be redeployed for core business function

The Cost Factor

Economic benefits are the main factor influencing companies to take testing to cloud. Another 2010 survey by ID

hinted the same. As the global economy recesses, companies continue to find ways to regulate costs and improve

ROIs. Cloud testing reduces the unit cost of computing.



18/56

Small and medium-size businesses that cannot afford high costs find cloud-based testing as a new lifeline. The

companies no longer need to invest in infrastructure and software licenses. They also do not need to worry abouvarious configuration issues and maintenance of test environments, and pay only for what they use.

Beyond cost Benefits?

Cloud is not all about cost saving. There are lot more benefits companies can extract using it.

-

-

-

-

A standard infrastructure and pre-configured software is available, reducing efforts in getting servers and

licenses.

On-demand provisioning helps companies to think forward instead of spending time to set up test labs. A

testing resources required for testing exist within the system and can be called upon instantaneously.

Better analysis and control are offered to test teams to build and execute their tests and identify the

bottlenecks. This helps in identifying possible runtime bugs a lot before they are actually found.

Its a great concept in motionbetween geographical distributed teams. Once a tester logs in and runs a te

the results are available over the cloud. The developer can then assess it and fix over the cloud itself. This

eliminates back-and-forth communication between teams.

Limitations-

-

-

Lack of standards: Absence of universal/ standard solutions to real world problems is a big issue. Each

cloud provider can have its own hardware, operating models and prices and may or may not offer any

interoperability. This poses a huge challenge for companies when they plan to switch to a new vendors

Security issues: Security in the public cloud is still a huge concern because the data may be stored in a

location which is outside a companyslegal and functioning jurisdiction.

Usage: The everyday usage costs increases very rapidly if testing is done without a proper usage of

cloud-based test. Though pay-as-you-go clouds are used, it can be expensive if the testing is out of sync w

requirements.

www.TestingCircus.com March 2014 - 17-


19/56

- Performance: It is always an issue since publicBibliography

clouds are used by many users in parallel. Situa-

tions got created a company had to wait for the

required bandwidth to execute their tests.

Conclusion

This paper tries to explain the benefits and limitations

associated with taking testing to Cloud. We have tried to

explain that why companies should start small and gain

confidence slowly to capture maximum benefits of

cloud-based testing. Once they believe that it has led

them in speeding time to market, lowering of costs and

ensuring standards compliance, they can go big. Using

of pay-as-you-go or on-demand services intelligently

and efficiently, companies can reduce cost of operation

and ownership. Companies should pilot cloud-based

testing as early as they feel comfortable before going to

-

-

-

-

-

-

-

-

Determine if a Cloud is Usable,blog post,

Bloomberg Businessweek, Jan. 31, 2011.

Solving the Challenges of Enterprise Mobile Appl

cation Development With Cloud-Based Testing,

blog post,

CIO, Feb. 17, 2011.

Rajagopal Sattaluri, Testing Considerations for Application Migration to Cloud Computing,

Cloud Computing Journal, Feb. 8, 2011.

Cloud Computing: The Good, Bad and the Ugly,

blog post, Dynamic Data Inc., Feb. 1, 2011.

Cloud Testing, A Growing Trend, blog post, So-

nata Software, April 4, 2010.

Nivedan Prakash, Cloud Testing: Attracting De-

mand, Express Computer, Feb. 1, 2010.

mainstream testing.

Vipinhas dedicated last 10 years of his professional career to the software

quality and testing. Currently working with Metacube Software, India, he

developed his key skills in developing automation frameworks and automat-

ing applications. With a proven record of implementing and refining test

processes for various clients across the globe. he is the author of several articles

and seven well sold books in India. He is pretty active within the software

testing community by speaking at International and national conferences,

writing articles and contributing to various blogs and forums.

Anubhais working as Associate Professor & Head, IT department, Internation

al College for Girls (ICG), located in Jaipur, India. An academician for last 11

years, she has been involved in teaching and mentoring several students in the

field of Computer Science. Knowing that teaching is the best form of giving

knowledge back to society, she worked as a lecturer in Subodh college, Jaipur

before settling in her current role at ICG. She is currently pursuing her PhD, in

field of Information architecture. Anubha is the author of 9 books and a regulacontributor in various forums.



20/56

Still relying onreading

Testing Circusfrom tweets& facebook

updates?Subscribe

To Subscribe

Click Here

Testing Circuswww.testingcircus.com

just with youremail id and

get themagazine

delivered to

your emailevery month,

free!

http://www.testingcircus.com/subscribe-to-testing-circus-magazinehttp://www.testingcircus.com/subscribe-to-testing-circus-magazine


21/56

A Common Pitfall

Of

Test Cases- Raj Subramanian

I recently gave a talk at a conference. I learnt many

things from my interactions with the attendees at my

session. One specific thing that stood out for me was

What if another system influences the system under

test in a different way than expected?

What if the system behaves differently under differ-how testers no matter how intelligent, smart, critical

thinking they are, still fall into the common pitfall

ofusing test cases for communicating testing progress and

ent situations and our test cases did not cover this?

.and so on. There are so many What if questions to

ask ourselves. Its an endless list.

test coverage.

So the point is, NO; we cannot possibility write every

If anyone reading this article, is still under this mindset,

I would ask the following questions-

possible test case to cover each and every scenario of a

system. This is where as testers, we think about testing

Do the test cases cover each and every scenario, each

and every part of the system under test?

Can you give accurate information of testing effort interms of test cases? Does it really make sense?

Are we trying to hide from reality and give some sort

of number to make us and our project managers feel

good when we report the number of test cases covered

to communicate testing progress?

What do you actually mean by test coverage? Can

approaches complementary to just executing test cases

like exploratory testing, automated testing, combinato

rial testing and other approaches based on the contextand scope of what we intend to cover. This may help t

uncover other weird scenarios or trigger unexpected

outcomes. With this being the case, it may not be valid

to say, I have 100% test coverage because I executed a

the test cases.

any other information about the system influenceSecondly, you may then ask,how should I give up-

this? dates on testing progress to my stakeholders?In my

experience, I usually do not have a problem in explain

Here is the common pitfall of completely relying on test ing testing progress to my stakeholders even if they are

cases. old school and believe test cases are the solution to al

Firstly,100% test coverage of the system is impossible. the problems. I would of course have some test cases

Exhaustive Testing is a misnomer. This being said, if that I execute, but also do lot of complementary testing

anyone says I have 10000 test cases, I executed all of to test case execution. Finally, I give the approximate

them and thus all my testing is completed, it is flawed percentage of modules covered/tested in the system as

because it is impossible to cover every scenario of a my testing progress.

system by just executing all the test cases

What if there are some hidden scenarios that theSo for example- If there is a system A, I generally split

tester still hasnt uncovered? it into different modules M1, M2


22/56

and give an update in terms of the percentage of mod-

ules I have covered in the system. (This is a general

approximation as there is always a possibility that I

havent thought about some other module in thesystem

which may cause problems. To err is human.)

So, say if I had covered M1, M2 out of the 5 modules Ihave identified i.e M1, M2


23/56

moolya sucks

we test fast and dont know to

make

more money from our custome

we are like this only

[email protected]


24/56

Mobile Application Testing

Using the Cloud Infrastructure

- Gagneet Singh

You have been asked to test the latest Mobile basedapplication, created painstakingly by your organization

over the last few months. All you have with you is your

exclusive Smartphone, which you saved for, andbought, over the last few months / years. The choices

are now with you, either beg/borrow/steal from col-

leagues or do the right thing. Fire up that web browser

on your Smartphone, open up Google and have a go

at searching for Mobile Test Partners on the Cloud. I

would generally as a rule go for the second option and

not put my precious phone to the test on un-tested

applications.

(WP8 devices and Windows RT devices and desktopswith Windows 7 & 8 included) and Chrome OS (mainl

low end laptops & devices). This vast array of devices

also brings up with them an equally confusing array obrowsers along with them (at the last count it was

something like 9 browsers and growing).

Faced with a similar dilemma, we take refuge in the

well-trodden path of checking on the search engines fo

a Web Accessible Mobile Testing Tool (applications an

browser based systems), that would be able to serve ou

purpose and not cause the management to jump from

their warm seats when they finally receive the bill for

What you achieve when you go through the search, is a the services used to test their precious new mobile

wide variety of web sites and commercial vendors of- application or website.

fering this facility to you, at a fraction of the cost that

you would spend in setting up your own facilities and To get through all this, I listed down a few of the up and

test lab. You need to now make an informed decision by coming offerings which provide a good cross-section o

researching and figuring out which one of these would the devices and are reasonable in costs. Although these

serve your purpose the best and also give you value for cloud platforms do provide a service which is extreme-

the money spent. ly useful, keep in mind, you might need to make use o

physically handling the device to run certain tests,

Mobile testing has come a long way. From the initial which cannot be checked with automation (but there

fragmented scenario of having to check on each kind of are ways and means to handle this, so dont be disheart

screen resolution and phone type and screen size, add ened). A hybrid cloud installation in these situationsto that the variety of mobile browsers being offered by can be one of the simpler solutions which come handy.

the various vendors, to the current situation of having A hybrid cloud provides a small subset of devices at

apps created using HTML5 versus native apps. Adding your physical location and the wider variety at a remot

to the general confusion is the non-app area, where location. Of the Could Mobile Test providers, the most

companies wish to check the overall responsiveness of important thing to look into is if they provide you with

their web pages across the same wide variety of storage for your tests and a way to run the automated

devices, which includes [and not restricted to] iOS tests that you have so painstakingly created for your

(iPhones and iPads), Android (Tablets and Phones application from within the cloud infrastructure. This is

low end and high end), and recently the Windows 8 along with the use of making sure that these tests run



25/56

over a wide variety of network speeds simulated to Testing their web sites and mobile based applications

provide the 2G, 3G, 4G and Wireless speeds prevalent in across various low end and high end devices to be usefu

the World Wide Networks around the world.

Sites like pCloudy.com, appurify.com, etc. are making

Practically a Cloud Based system should be able to cater easier and faster to send out mobile products into the

for most of the requirements outlined above; and the market by providing the required platform at a fraction

good news is that most of them do exactly that. A few of of the cost of actually acquiring a complete mobile test

the prominent ones which I have used recently and the lab. That said, you would still need to work out a small

ones which come to my mind are: pCloudy.com, subset of your tests at a physical location, but I am sureappurify.com, perfectomobile.com, HP mobile testing that this would also become possible over the cloud.

lab, to name just a few of the upcoming entrants in this With the advances these start-ups are making with tech-

field, where by Gartner estimates, there are 5.6 billion nology and improvements on their own feature sets. I

handsets present. pCloudy.com has stood out as an ex- certainly would be looking forward to features which

cellent upcoming product, being run by engineers who provide a friendly interface and let me run across multi-

have previously worked with Nokia and other top mo- ple devices; and for that the Mobile Test on Cloud pro-

bile hardware development companies. They have built viders are definitely a better option than trying to keep

the framework for testing on mobile devices from the up with the influx of the hardware been thrown into the

ground up and have got some really cool features which market by all the top end and low end hardware manu-

go with it. (Disclaimer: I know one of the Co-Founders as facturers around the world.a colleague from my previous companies). I loved the

way they have handled the storage of tests and results on

the site itself, along with providing features such as

mock location maps, allowing the users to experience the

different states of the application in separate geographi-

cal locations. They have recently launched a feature of

having multiple browsers and simplified their launching

from within the cloud interface, making things easier for

users again. And have launched the latest Android

KitKatversion with the Nexus5. All in all, an excellent

package to go for, with reasonable rates.

All said, the main purpose of having a cloud based

mobile test experience is important for any company

wanting to launch its web presence these days. With the

advent of HTML5 and other technologies like Founda-

tion (more on this later), the web has become a place

where people love a responsive site (or application

across iOS, Chrome OS and Windows [Phone] 8) that

caters for whatever device they are working on, and does

not have the staid look and feel when they change froma Desktop -> Laptop -> Handheld Tablet -> Smartphone.

They want to get the feel that the web site developer /

organization has done their homework and provided

them with a site where they do not have to pinch-in and

out, just to read content. With the expansion of Smart-

phone markets in the developing nations and organiza-

tions wanting to tap into the billions of people there to

advance their products, it has become imperative for

these organizations to go through the process of Mobile

Gagneet Singhhas been

working in the Quality

Assurance/Test field for

the past 8 years (with an

additional 4 years in Sys-

tem Tools development)

and has been involvedwith companies such as

Toshiba, Adobe (Macro-

media) , McAfee, Oracle, Yahoo! and recently Mi-

crosoft.

He likes to blog and to write about the experience

he faced in the various organizations and situa-

tions. His work has mostly been with Automation

Testing, along with Performance QA. Also, Secu-

rity testing over the much hyped Cloud Comput

ing (using Hadoop and Azure) has figured in hiswork area.

Currently working out of this place they call the

Down Under, where he lives in Sydney, New

South Wales!



26/56

Better to Implement Late

Than EarlyHow Quicker can mean Slower

- Peter MorganI want to define what I mean by late and early and

then go on to give some context from a firm I once

worked for lets give them the fictitious name Lin-

man Manufacturing for convenience. If I dont define

my terms, we will all get lost. I will use early and late

in an almost intuitive way, although perhaps not as

date for the edition that follows. This is another

deadline that has significant consequences if it is

missed. Some software projects have hard-wired dead

lines that cannot be missed. Perhaps there are legisla-

tion changes that need to be complied with. The

introduction of the Euro is a good example. However,everyone uses them. They are not of the Humpty even when there is a hard (i.e. cannot be moved) dead-

Dumptyvariety (Alice Through the Looking Glass by

Lewis Carroll: 'When I use a word, Humpty Dumpty

said in rather a scornful tone, it means just what I

choose it to mean neither more nor less.).

So, for me early is before we were ready, and late is

after the planned date. These are pragmatic terms lets

not get argue about them now. My hope is that you will

see the usefulness for yourself. To start with, I need to

say something about project deadlines. First of all, it is

not testers (or test managers) who determine when a

work product is implemented (into PROD, obviously).

Test resources can speak into, or provide information,

that helps others make that kind of decision, but the

final decision lies outside testing. Secondly, we per-

haps all recognize that if the decision were left to tes-

ters, work products would not get implemented. We

testers are a pessimistic breed, and tend to focus on

things that dont work. It is not always the 390 require-

ments that work that get our attention, but the 1 thatdoes not. We concentrate on that.

line, there is sometimes wriggle-room around the edg-

es. Some parts of company accounting in Euro-zone

countries needed immediate changes when the Euro

was introduced. Other parts did not activities around

the end of the company financial year may not have

been needed to be correct on Euro day-1 only at the

end of the company financial year. So even where ther

is a hard deadline, some parts may not need to be read

on the first day, whilst other parts must be available,and be seen to be working.

Right. The pre-amble is over. I want to tell you about

my time at Linman Manufacturing. In my many

months working for them, there were 8 major imple-

mentations, where significant new functionality was

introduced. Although each implementation was sepa-

rate, there were both implicit and explicit points of

interaction; data was loaded into and extracted from

the same database, with some common database table

used. As time progressed, later functionality relied up-on the data that had been introduced in earlier phases,

and was loaded month-on-month. I want to concentrat

Lastly on deadlines, some deadlines are more impor- on the last 4 major deliverables, giving the targeted

tant than others. Take the day I am writing this article. delivery date into PROD and the actual date.Tomorrow I am preaching at a local church, and some-time before standing up, I need to have prepared what

I am going to say. That is an immoveable deadline.

Similarly, the deadline to post this article is midnight

tomorrow. If the editor gets it by then, it will be consid-

ered for the next edition. Otherwise, it will be a candi-



27/56

involved in the ICT indus-

try for more than 30 years,

and worked in the free-

lance marketplace for

much of that time. His time

I mentioned that there 8 major implementations. Of

course, there were other times that software was promot-

ed into the PROD environment. User-requested changes,

software platform upgrades, and system tweaking oc-

curred throughout this time frame. But if the project

team as a whole had been asked before each phase tabled

above, for phases F and G the answer would have been

yes, and for phases E and H no. In the time that was

given, the best testing, based upon risk, had been carriedout. But there were huge swathes where the answer at

best was we dont know, and some parts were clearly

not working. The architecture was basically to take mul-

tiple-format files on a regular basis (daily / weekly /

monthly) and to load this into a standard star schema

data warehouse, and then extract the summary informa-

tion. For phase H, data had been successfully loaded

many times, but the reporting layer only developed in

outline. Now it is not until data is outputthat it is possi-

ble to tell whether it wasloadedsuccessfully (i.e. it is fitfor purpose). And so it proved to be.

For phase E, there were immediately amendments re-

quired, both to data loading routines and to the report-

ing layer. Seven weeks later (and after seven

month-by-month basis. March 2010 (when data for Feb

ruary 2010 was loaded) was the first month-end with

stability.

There are business reasons for ensuring that somethin

is delivered, and that progress is seen to be made.

However, for Linman Manufacturing the informatio

loaded into the Data Warehouse was for long-term stra

tegic planning, not for the day-to-day business opera-tion. There were, in one sense, no unmovable project

deadlines.

If you have a choice, never implement a software solu-

tion early. Doing so makes for a frenetic period of

activity just after the implementation date, and some-

times aborted product launches. If you takelonger, it c

mean that the software is availableearlier. When that

happens, staff can be truly released to go onto the next

project without constant drag-back from activities that

should have been put to bed!

To do otherwise means thatquickerisslower.

Peter Morgan is a testingprofessional who has been

implementations), the solution was stabilizing. Let me

tell you, those seven weeks were interesting. Some of the

input processes could not be run for part of that time,

meaning that reported information was only partially

correct, and it was not until nine weeks after the date that

users could gain any confidence in the output. January2009 was the first time that month-end reconciliation (forhas sometimes moved from testing to develop-December 2008) could be attempted. That is quite a longment, but he would add always using the mind-time after the actual implementation date.

If anything, the situation was worse with phase H, and

interestingly enough from the table above, this phase

was both late(after the targeted delivery date) and

early (implemented before it was ready). The first

weeks were spent loading a backlog of data, with 10

months of data to load immediately. The reporting layer

quickly highlighted problems with 7 of the 16 data

feeds problems that could only be rectified by remov-

ing any data loaded to date, and either re-engineering

the data creation process (before it was made available to

load), or changing the data load procedures. There were

times that it seemed data was being backed out faster

than it was loaded even though once a data feed was

identified as wrong, nothing else was loaded for that

feed until the problem was resolved. A big score-board

showed what data had been loaded for which feeds on a

set of a tester. He is passionate about testing and

a firm advocate of testing qualifications. An en-

thusiastic speaker and author, Peter tries to base

his output on hands-on experience, attempting to

relate fine sounding ideas back to how it will

affect Joe or Jane Tester in their everyday working

lives in the war of attrition that we call software

testing. He is a regular at EuroSTAR conferences,

and is speaking at Belgium Testing Days in 2014

the forth year in a row. At this time of life, Peter

offers experience, and can sometimes say when

offered a tricky problem: Been there, done that,

and here are 2 or 3 options that may, just may,

work in this situation. He continues to learn,

adding technical skills to his impressive range or

hardware / software / business sector portfolio.



28/56

7 Types of TestersWhat is Your Identity?

- Arslan Ali

I dont know if anyone has noticed but the world we

live in now is different from the world we used to live

in just 5 years ago. For me, the change that occurred is

far rapid than anticipated, because if we refer this to a

20 or even 10 year past leap then most of the skeptics

would say Why not!, it should have changed! but the shortness and the speed of this period leaves no room

for being skeptic or nave We simply need to

understand and adapt!

How people are getting aware of the communication

and sharing bounds and exploits over social networks

Where to say and share what is now dependent on

where and how you are registered as a user; Twitter

Facebook, LinkedIn, Instagram, Four Square, Google,

pint it, flicker and so on. We are not structured anymowe are living multiple lives under multiple scenarios.

Somewhat, this is not based entirely on our choices, th

is how the environment around is turning out to be

and we have to live it!

Mobility has broken free from just being a device to

communicate into an instinct. We are now thinking! Or in other more adaptable

senses we are now becoming Context Driven!

We are using our hand held devices in so many different

dimensions other than it was meant to be that it is

changing the complete concept of computing and

networking. Hand held devices are now our nodes to

the clouds; we are now the new form of terminals; The

Human Terminals; the value to the word Touch has

enhanced itself from Touch screen, and then within a

very short time it again reboots itself to Human

Senses!It feels like a history in making where the

systems which are categorized as something purely

mechanical and electrical combination of components

with mix of complex logics and design are re-emerging

to sapiens, like an event in space and time; As I see it,

the systems are reaching to our senses, our beliefs, dailylives and simply becoming an extension to our self

being, like an implanted new body part. Gadgets are

now not need to be held in hands; they are wearable,

and soon they will represent a mere extension to its

users.

These factors are effecting what we used to know as th

solutions and systems; these factors are now playing a

major role in provisions of the right solutions to the co

requirements and needs of the users. And< the same

factors are affecting how we Test these systems;

In a way, we are now moving to an age where due to

the magnitude of the contextual effect on any scenario

generic approaches will simply fall apart and fail! In

so many words, we need specialists! We need

empowered human beings and their expertise to

address the right issues at the right time; we need to

identify the right coverage to find the important bugs,

and mind you We need to identify ALL OF THEM!Under several scenarios and contextual situations and

due to certain trendy and cultural bonds we have not

yet succeeded in creating our own identities as Testers

We are still based on the Types and Approaches

scenario. Where, Testers when tend to define what the

do, start explaining the testing types and the approach

The human mind is now adapting these effects; see for they follow. They tend to list down several technical

example our children; how they have adapted the use tools and programming languages as skills, and not as

of touch screen, games and the use of smart phones. Tools to support testing. In this stream of self-



29/56

discovery they forget the very scarlet thread they cross

from being a Tester to being a Coder.

Well dont worry we have worked that out as well;

usability testers in my entire career, but I have

seen more of them from a distance. A usability

tester specializes in studying how users feel

about using and learning a product.

James Bach has already published twice about the types of

testers there are after receiving several queries regarding the

latter; in his recent blog post, he mentioned the following as

the testerstypes:

(I am quoting him here, rather putting in my own words

it is better that way)

(SEVEN KINDS OF TESTERS)

Security Tester. Security testers also often dont

think of themselves as testers. Security is an

exciting, specialized form of testing that requir

the mastery of a great many facts about a greatmany technologies.

Testing Toolsmith. A testing Toolsmith is a

programmer dedicated to writing and

maintaining tools that help testers. This is wha

a lot of people would call an automated tester

but you better not use that term around me.

Automated? Manual? There is no such thing as

manual or automated testing. Its all just testing.

Testing is often supported by tools that attempt

SDETSoftware Development Engineer in

Test. This means a full on programmer who do

testing using his programming skills.

to simulate user interaction with the system.This is what people call test automation even

though it is only automating a crude

approximation of one aspect of testing. If you

have the ambition to be a one-man test team, it

is extremely valuable to learn how to make your

own tools.

Exploratory? Scripted? There is no such thing as

an exploratory or scripted tester. All good

testing is exploratory to some degree and

scripted to some degree.

Tester. This is a testing generalist who can

contribute to any test team. Sometimes called a

QA analyst, QA engineer, or test engineer. I

prefer the simplicity of tester.

Omega Tester. The omega tester (which I

sometimes call a test jumper, after the analogy

of a paratrooper) is one who can do anything.

An omega tester is equipped to be the only tester

in a project team, if necessary. Omega testers can

lead testing, or work with a team of other testers.

I am an omega tester. I aspire to be a good one.Performance Tester. The performance tester

understands the mathematics and dynamics of

the performance of large-scale systems. They use

tools that create high loads and measure the

performance envelope of systems as they scale

up. Performance testers often dont think of

themselves as testers.

Usability Tester. The usability tester is a bit

mythical. I have met only two dedicated

On the other hand there are several characteristics as a

tester which can stood up and create an exclusive teste

identity; For example, boundary Testing heuristics; no

I know that several of us have used this term in our CV

and have somehow read or taken part in forums to talk

about this type testing; but how many of us have

actually bifurcated this into Galumphing, or

Steeplechase or even Leap and Creep - I dont thin

any of us!

OR

While discussing about product coverage we have use

the term San Francisco depot instead of discussing

the missing out requirements, and blaming the

developers of not providing the right specs or cursing

the Implementation team of not discussing the right

requirements; that is what common professional does!

Why not stand out and use your own language?

I have seen professional testers asking questions and

worrying about Testing without Requirements orFinding the right bugs within a short period of time,

but I have not seen any of them discussing about using

or creating their own Heuristics? Why not?

There is also no denial in discussing Quality and its

criteria, but have we ever tried to use and educate

ourselves with the use of the Quality Criteria Heurist

called FEW-HICCUPPS? Try and do that!



30/56

Let us understand now.

Why cant we move beyond being a technological freak

to a Tester in a meaningful term; Does the mention of

the very word Heuristic is not a mention of Tool in

your sense. Technology is a wonderful thing, being

technical is in the very genes of a computer professional;

but as testers we need to identify ourselves as someonewith a niche of being a tester and being technical at the

same time; Being technical comes with the package; So

why not mention who you really are? A Tester!

Empower yourself, your language, attitude and

reputation as tester. Learn Un-Learn and the re-learn!

Try and improve your language as testers, differentiate

yourself from the peers of Developers and

Implementers. Yet sewed in and work for their support

Or I can only say this then; you are in the wrong game

baby!

Arslan Ali has more than14 years of Experience

related to IT, Industry and

Training Institutions with

exclusive experience of 5

years in teaching various

disciplines and projects inIT Institution. He has worked in various roles in

capacity of Software Engineering, Software

Tester, Trainer and Quality Assurance Roles. The

Major focus of his expertise lies in Coordination,

Implementation and Testing of ERPs and

Customized Applications. He is also a trainer for

Context Driven Testing for various companies

and individuals.

Arslan is currently working at Sidat Hyder

Morshed Associates (www.sidathyder.com.pk)

as a Sr. Consultant Information Solutions; but

beside that he is also an active founding member

of TestersTestified (www.testerstestified.com)

(@testtified), Outtabox! (www.outtabox.co)

(@OuttaBoxPk) and OISOL Open Integrated

Solutions (www.oisol.com) as a training

consultant for Software Testing and Context

Driven Testing Workshops.

You can follow him on twitter @arslan0644 andon LinkedIn at

pk.linkedin.com/in/thegoodchanges/



31/56

Asia Pacifics Largest

Software Testing Conference

11t hI nternat i onal S of t wa re Testing Confere nce

STeP-IN

SUMMIT 2014

TestingNOW

InteractionInsightsOpportunitiesJUNE 25-27, 2014 AT BANGALORE &

JUNE 18 & 19, 2014 AT PUNE & HYDERA

Most Popular Conference among Start-Ups to Fortune 1000 Companies

Todays tester is a unique being, driven, not by deadlines and mundane tasks, but by a relentless curiosity an

a fascination with possibilities. Awaken the tester in you. This is where you want to be; this is NOW. Walk a

with exciting ideas and quality insights from other industries. Make your mark by challenging the existing

paradigm.

CONFERENCE PROGRAM

18, 19, 25June, 2014

26 - 27June, 2014

Pre-conference tutorial workshops (two parallel tracks) @ Pune, Hyderabad and BangalTarget Audience: Test Leads, Test Architects, Test Managers, Test Analysists and Consultants

Conference @ BangaloreTarget Audience: CXOs, Vice Presidents, Directors, Business Heads; Customers and end-users of IT products and sTest Management professionals Managers, Test Leads, Software, Test Engineers; Quality / SEPGManagement

ProfessionalsManagers, QA Leads, Software QA Engineers; Product Development Managers; Chang

Agents

Over 900+ delegates from India and abroad

attended in STeP-IN SUMMIT in 2013

View Past Conferences View Past SpeakersGallery

Excited to participate as a SPEAKER / DELEGATE / SPONSORwrite to nazreen@stepinforum org
http://stepinforum.org/index.php/2012-03-27-11-28-34/stepin-summitshttp://stepinforum.org/index.php/2012-03-27-11-28-34/stepin-summitshttp://www.pinterest.com/stepinforum/past-speakers-gallery/http://www.pinterest.com/stepinforum/past-speakers-gallery/http://www.pinterest.com/stepinforum/past-speakers-gallery/http://www.pinterest.com/stepinforum/past-speakers-gallery/http://www.pinterest.com/stepinforum/past-speakers-gallery/http://www.pinterest.com/stepinforum/past-speakers-gallery/http://www.pinterest.com/stepinforum/past-speakers-gallery/http://www.pinterest.com/stepinforum/past-speakers-gallery/http://stepinforum.org/index.php/2012-03-27-11-28-34/stepin-summitshttp://stepinforum.org/index.php/2012-03-27-11-28-34/stepin-summitshttp://stepinforum.org/index.php/2012-03-27-11-28-34/stepin-summits


32/56

ww.stepinsummit.st

nforum.org

Hosted by:

www.qsitglobal.com


33/56

BOOK

WORMSCORNERMarch is the beginning of the appraisal season; thats why 50% of t

organization actually wonder if they should be continuing in the o

ganization or not. Thats why I decided to crawl through Dont H

the Best.This book is written by Abhijit Bhaduri. In case you are wondering

it is a misguide to hiring the right team, then you are partially inco

rect. This book preaches and lets you come to your own conclusion

The book tries to sell itself by lecturing about good hires and how

make good hires, however, it tries to draw the right line between

hiring right and hiring the best. Unlike many other interviewi

books that are filled with choc-a-bloc aptitude and problem solvin

questions, this book also tries to examine the organization culture

why culture fitment is important for the company. The case studie

with the standard disclaimer of having been altered to protect iden

ty is very useful and causes the reader to ponder as to how he coul

have done things better. Reasons as to why it is important to create

fitment between the interviewee personality and the management

pectations, individual traits that need measurement, why making

wrong hire call can result in financial losses are stories talked abou

depth in this book.

What did it teach me?After reading the book, I ensure that I pass

a set of good and bad candidates to my interviewing team; that va

tion causes them to be on their toes and interview without bias. If I

send only good candidates their way, a form of bias sets in over the time which would result in all of us overlookinhe most obvious reason for not hiring the candidate.

Why should you buy this book?Because its not free; in addition to that, you will learn valuable lessons on how tcreate a team, why the culture fitment is important for your teams and why you need to ask questions beyond the

role competencies while forming teams. When is it important to look into a resume to know what hes capable of a

when should you look beyond the resume? You will ask yourselves these questions if you were to read this book.

hope, after reading the book, you dont hire the best anymore; you will hire better than the best.

Love,

WoBowww.TestingCircus.com March 2014 - 31 -


34/56

Become our fan -

https://twitter.com/_sahi

http://www.facebook.com/sahi.software

Request a free demo by sending us an email at [email protected]

http://www.sahi.co.inwww.TestingCircus.com March 2014 - 32 -


35/56


36/56

smartness, they record and replay some of the testing

and quote savings in the name of automation. The

clients cannot back out due to the legal agreements

signed at the beginning. An impact of this is that the

test results for periodic testing that's being sent to

clients cease to matter; and regardless of the frequency

of app usage by customers, testing companies continue

this trend. 1 look at the testing economy would tell youthat 2.5 Billion Dollars was the money given to off-

shoring companies for testing alone in the 3rd quarter

of 2013. With new testing companies sprouting all

over, this is set double in the next few years. And the

testing companies have also started to exploit this.

With substandard test cases and haphazard testing,

they make hefty profits without providing any value

by testing.

An indicator of the lack of quality can be seen by the

most unimportant projects being handed to the

off-shoring testing companies; this can be seen by the

very fact that in most of the offshore company cases,

not much of business revenue would be lost if the

offshore projects are closed down. Secondly, according

to the reports of our special correspondent, in the last 5

months, there has been ZERO new product launches innon-Asian markets due to testing done from here.

I am unsure if others realize this, but looks like India's

testing industry has started to face its worst crisis; my

personal thought is that the rest of this year will be

gone in people realizing their mistakes and the indus-

try auto-correcting itself. What do you think will hap-

pen? As I mentioned last month, only time will tell.



37/56

#Testers2Follow

Joris MeertsPublishing the latest news from the software testing weblogs.

Keeper of lists. Testing historian, critic, thinker, member of

#DEWT. #Capgemini

https://twitter.com/testingref

Mike LylesInternational speaker, writer & Sr QA Manager in PerformanceTesting, Test Automation & Service Virtualization (20+ yrs IT).

https://twitter.com/mikelyles

Anna Royzman

Context-Driven Scholar

https://twitter.com/QA_nna

Sharath Byregowda

A passionate software test professional, Principal Consultant atSQS, London in their agile group.

https://twitter.com/sharathb

http://Twitter.com/TestingCircus



38/56

ngT e

and

low

h

ingd

em

ge fo

eers

Us

#

gC

er.c

http

https://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profilehttps://twitter.com/signup?follow=TestingCircus&context=profile


39/56

Security Testing Tips Part 15

- Santhosh Tuppad

DIY: Test Environment for Security TestingOne of the challenges in security testing is, setting up

the test environment. If you are a small scale organiza-

tion and there are no lots of processes, then it could be

easy for you to go ahead and setup a test environment

like you want, but in the bigger organizations when it

has lots of processes it could be hard. There could be

network related blockers that you may want to clear(Example: You want to download a software which

you want to use for security testing purpose, and that

source of download is blocked by the network of the

organization). If your test environment is a blocker for

you, then I would better recommend to not performing

security testing and thereby, you can at least save costs.

Isolated network of computers

Administrator rights for computers & other devices

In my experience, I have faced lot of blocke

Documents

Testing Circus Vol5 Edition03 March 2014