All about testing: 2012

Friday, December 28, 2012

Manual testing Interview Question

This Page contains links to the Questions asked by the Reader's and as well as Question's written by the Author.

1. Manual Testing: Question and Answer (Part 1)

Manual Testing Interview Question and Answer

1.) What is the difference between Sanity and Smoke testing

2) What is the difference between Load and Stress Testing?

What is the difference between Sanity and Smoke testing?

Sanity Testing: Sanity testing is also known as mini regression testing. Sanity testing is done when you get a release after your bug fixes and that bug has impact on other module as well then we perform sanity testing to make sure that other module is working fine.

Smoke Testing: Smoke testing is done in the beginning when you get the release for the first time then we perform smoke testing to verify that is the system is ready to go into testing phase or in other words we can say that it is done to verify that if the build is ready for testing.

What is the difference between Load and Stress Testing?

Load Testing: Load testing is done to find out the response of the application under heavy load.

Goal: Goal of load testing is to find out the response of the application under heavy loads.

Example: If your application can handle the load of 1000 user then, in load testing you will test that what will the response of your application when this load is increased. You can use different scenarios in that like observing the response when the load is static means all the user login at the same time, observe load when the load is increases. These are few scenarios whereas in actual we can use different scenarios for getting the response.

Stress Testing: Stress testing means observing the response of the application when the load is increased up to the limit when your application gets crashed.

Goal: Goal of load testing is to find out how your system will behave when it will fail. The purpose of this testing is to make sure that even if your application gets crashed then also it should not compromise on the security front.

Example: If your application can handle the load of 100 users then execute your test with more than 100 users until your application gets crashed and then see the how it fails, Does it fail smoothly and able to recover? These are the few things which we need to do while doing stress testing.

Domain Knowledge and Software Testing

Many times we have heard this sentence that Domain knowledge is important or not for a software Tester.

Recently one of my friend called me asked me that how important it is to have domain knowledge for testing?

This is what I told her:

Yes it is important to have domain knowledge but it does not mean that you need to be an expert of a particular domain. You can still test the Application if you have not worked earlier in a particular domain.

What I have experienced in my testing carrier is that it is important to have domain knowledge but it is just one skill out of other skills which are required for doing testing.

Skill Required for Software Testing:

There are many skills which are required in a candidate like:

Technical Skills (Testing)

Logical Thinking

Domain Knowledge

Programming knowledge (for automation)

Communication skill

Note: The list may include some other skill too

So if you are not expert in one of the skill then that is not a blocker; it’s just that you will have to work on that particular area. So if a candidate is having good technical testing skills then he/she can test the application with a little assistance.

How to Start Testing if you don’t have domain Knowledge:

I have worked in e-learning and payment domain and when I joined the organization I was not having any knowledge about these domains but I have done the good work; I learn about these domain after joining the organization; did lots of search and worked on the assigned project; So basically if you are new to particular domain then you will have to put the effort to learn that domain So it’s not something without which you can not do the testing.

Besides all these things when you get a project for testing then we get the Requirement document and from that document you can write you test cases for testing the functionality of the application and while you prepare your test cases you can learn the domain from different sources like document available in the company; search in Google; communication with the team members, business analyst etc.

Thanks Harish for reviewing the article

QTP

Here you can find the links to all the Blogs related to QTP:

1. QTP 11 Patch for IE 9

Wednesday, December 26, 2012

QTP 11 Patches for IE 9

QTP 11 Patches for IE 9:

I am trying to set up a QTP Framework in my current company and therefore we decided to start with using the trail version. We faced some issues while installing the QTP evaluation version. Just thought to share it, so that if anyone else has the same issue then it might help them as well.

Issue: After installing the QTP 11 evaluation pack we are not able to record the script for web application.

Environment: QTP 11, Windows 7, IE 9

Solution: For IE 9 we need to install 2 patches QTPWEB_00073, QTPWEB_00078 these patches are available in the QTP 11 Patches folder.

After installing these patches we were able to create the script for our web application. Bingo J

Software Testing is an easy job?

After a long time i am writing my new post. The reason was simple wasn't able to think of some interesting topic. Now got the one based on my experiences in one of my company.

Every tester will agree with me that Testing isn't an easy job but people outside the testing circle or people who have got very little knowledge of testing thinks that testing is an easy job.

So how you going to deal with such kind of people who just come to you with a deployment change and ask you that this is the change just test it and give me sign off. Will you just do what they say? I am not writing this after reading this in some article or book i am writing what i have gone through. Ok let's start it as short story to make the whole understandable and interesting.

We have got three character in this story:

1. Mr Head ( They always say that "Quality needs to be maintained". In our story will address them as B.)

2. Mr Manager (He is always worrying about Delivery. In our story will address them as M)

3. Tester (Tester's who are handling multiple jobs. In our story will address them as T)

So the story goes like this: Our Tester T has joined new company where no process exists in fact there is no Testing team and the responsibility of setting up a testing process has been given to T.

First Week:

M & B: Hello T welcome to the team. You know what expectations we have from you; we know setting up a process will take time and we do have many lined up projects so you keep on working on the projects as well as works out on the process implementation.

T: Yeah, I understand will take care if that but you have to give time. Testing cannot be done just like that.

M & B: Oh yes of course we understand that, you do the work your way.

T: Ok then will work on documentation first and will set up internal QA process and then we can propose it to rest of the team.

M & B: ok good. Go ahead as per you plan.

Second Week:

B: Ok T so now we need to have proper documents of all our applications which we don't have. Start working on that.

T: Ok will check out what i can do as i am also new to the applications; I have already started working on process documents but will start work on application document as well. Will go through whatever is available in the system

Third Week:

M: There is a new requirement go through it and plan your testing.

B: We have a organized KT session for you, attend those and raise your concern.

B: There is a request for enhancement you need to test those. Plan it.

T: ???????

What do am I going to start now….hmmmmmmmmmmmmmmmmm

The story goes on like this for rest of the weeks.

Will publish the next part about what Steps T has taken to organize the QA stuff. As it is live story so will have to wait for some time to get the part2 of this.

Till then Happy Testing :)

Friday, October 5, 2012

Tester vs Developer

I am dedicating this post to all my Tester and Developer friends. Reason behind writing this post is to analyze the sweet (not really ;) relation between tester and Developer and finding out some solution to make it better J.

It is very common everywhere developer thinks that tester’s are trouble makers and there is some bitterness at some point between these two roles.

For developer there code is like their baby and no one like to hear flaws in their baby and as a tester we just think about the quality and that’s why we find the bug. Well it’s natural if you are developing something then it will have bugs but whether to fix that bug or not is a different story and it depends on many factors like severity, priority, type and scope. But for a Tester a bug is bug and a tester will always try to point out the bugs after bugs in the testing phase because it is s their work

So; when we got lots of bugs to fix and count increase, developers get frustrated at the number of bugs and some time on the person as well and this is where the debate occurs about the valid bugs, invalid bugs. A Developer always tries to prove the bug is invalid or it is a feature; some of the common replies which we get in this situation are:

“That’s weird…”

"It works on my machine"
"No user would ever do that"
"That's not a bug, it's a feature"
"It's supposed to do that."

There is a long list available about the developers reply to testers but t I have just written which I have heard frequently.

Now the question arise that; is it all about the Developers?

Hmmm…..Answer for this is simply No. In this game these two players has different and opposite role and to make this relation better both need to work together as team.

A Developer needs to understand that when we raise bug then we are not criticizing a developer or not pointing the mistake in the person and on the other side a Tester should give the proper information about the bug you got and about the scenario in which it has occur and what impact it is going to have in business.

Developers and Testers can actually help each other in many ways; for example a Devloper can help in the following ways:

By sharing information;Since you have developed the product so you can share the information about the diffrent paths and the impact and vital informaiton which you think could help to make the product better.
Before you give any of the above given reply; please give it a thought that tester is not pointing out mistake in you; It’s just that he/she has raised the bug before client will raise; So spend some time in understanding the issue rather than just simply rejecting it.

There are many ways in which a tester can play a big role to make this relation better; tester's can help in the following ways:

Do not hide your scenarios thinking that towards the end of phase you will raise it as a bug; If you have got something in your mind share it with the team and this way we will not only build a good relation but also will have a better product because when both the parties shares the information they both can help each other in understanding features which they might have missed.
Talk frequently with the developers; don’t just talk with them when you have got some issue.
Raise a bug in a way so that it should not hurt the feelings means raise the issue in a positive way.
Before raising the issue do some research yourself; for example: if you are trying to open some folder in some directory and you are not able to open that then just blindly don’t drop the email; At least first check if you are in the proper directly if the path is proper or not.

There are many more things for developers and testers which i can write about but I am just keeping it short :).

So now all my developer friends please share your experience and write what kind of help you think a tester should provide and vice versa my tester friends what you think the developer should do or should not.

You can also share any quote which you might have heard from a Developer or from a Tester!!!!!!

Software Testing!!!!!!!!!

This Page contains links to the article related to Software Testing.

1. Software Testing is an easy job?
2. Tester Vs Developer
3. Domain knowledge and software Testing

Domain Knowledge and Software Testing: