Testing Interview Questions

Test Automation job interview questions:

1. What automating testing tools are you familiar with?
2. How did you use automating testing tools in your job?
3. Describe some problem that you had with automating testing tool.
4. How do you plan test automation?
5. Can test automation improve test effectiveness?
6. What is data - driven automation?
7. What are the main attributes of test automation?
8. Does automation replace manual testing?
9. How will you choose a tool for test automation?
10. How you will evaluate the tool for test automation?
11. What are main benefits of test automation?
12. What could go wrong with test automation?
13. How you will describe testing activities?
14. What testing activities you may want to automate?
15. Describe common problems of test automation.
16. What types of scripting techniques for test automation do you know?
17. What are principles of good testing scripts for automation?
18. What tools are available for support of testing during software development life cycle?
19. Can the activities of test case design be automated?
20. What are the limitations of automating software testing?
21. What skills needed to be a good software test automator?
22. How to find that tools work well with your existing system?
23. Describe some problem that you had with automating testing tool.
24. What are the main attributes of test automation?
25. What testing activities you may want to automate in a project?
26. How to find that tools work well with your existing system?
27. What are some of the common misconceptions during implementation of an automated testing tools for the first time?

Basic SQA testing questions
1. What is the Difference between Project and Product testing? What difference you have observed while
testing the Clint/Server application and web server application
2. What are the differences between interface and integration testing? Are system specification and functional
specification the same? What are the differences between system and functional testing?
3. What is Multi Unit testing?
4. What are the different types, methodologies, approaches, methods in software testing
5. What is the difference between test techniques and test methodology?

Interview questions on WinRunner

1. How you used WinRunner in your project? - Yes, I have been using WinRunner for creating automated
scripts for GUI, functional and regression testing of the AUT.
2. Explain WinRunner testing process? - WinRunner testing process involves six main stages
o Create GUI Map File so that WinRunner can recognize the GUI objects in the application being
tested
o Create test scripts by recording, programming, or a combination of both. While recording tests,
insert checkpoints where you want to check the response of the application being tested.

WinRunner interview questions
1. Describe the process of planning a test in WinRunner?
2. How do you record a new script? Can you e-mail a WinRunner script? How can a person run a previously
saved WinRunner script?
3. How can you synchronize WinRunner scripts?
4. What is a GUI map? How does it work?
5. How can you verify application behavior?
Other
1. What programming language are you using?
2. What C++ libraries are you proficient with?
3. Which argorithm do you like the most? Why?
4. How do you debug SSH?
5. What is the QA process?
6. How do you train another QA engineer?
7. What bug tracking tools you have used? Have you used any free tools?
8. How do you start your QA if there are no system requirements?
9. Have you used MSVC? What do you think of it?
10. There are 3 lights (in one room) and 3 swtiches (in another room), one for each, if you only enter into the
light room once. How can you find out which switch corresponds to which light?
11. What is your weakness?
12. Why do you think you are suited for this job?
13. If there is a day, when you find yourself not fitting in our team, what will you do?
14. What makes you think you are qualified for this job?
15. Do you like music? Which composers are your favourite?
16. What kind of PC games you like most? Why?
17. Are you familiar with collboration tools? Which communication method do you prefer for talk, email and
chat?
18. When will you be available to start work?
19. What security tools have you used?
20. Tell me about yourself.
21. Tell me about your experience with this type of work
22. What do you like and dislike about our company?
23. Why do you want to work for us?
24. What should we hire you? What can you do for us? What can you do that others can not?
25. What is the job’s most attractive and least attractive factor?
26. What do you look for in a job?
27. Please give me your definition of software test engineer.
28. How long would it take you to make a meaningful contribution to our firm?
29. How long would you stay with us?
30. Are you thinking of going back to school or college?
31. What kind of programs/machines or equipment have you worked with?
32. You may be overqualified for this position we have to offer.
33. Give me an example of a project you handled from start to finish.
34. What was your last employer’s opinion of you?
35. Can you work under pressure, deadline etc?
36. Do you have any questions?
37. What is it you liked and disliked about your last job?

What is ideal developer/tester ratio?

While some companies manage with 1 tester per 10 or more developers other companies have 3 testers per developer. Does this mean the later companies come out with better quality products compared to former or is it just that the team is not properly organized. My dream team will have test developer ratio of 5:6, well why such a strange ratio. According to me the code developed by 2 developers can be reviewed (or inspected) by 1 testers and code developed by 3 developers can be tested by 1 black box tester. So for 6 developers we need 2 black box testers and 3 White box testers. The job of white box tester is the code review and automation, while black box testers job include creation of test cases, test execution. Many firms does not like to have white box tester (code reviewers), I found that independent code reviews done by non-developers help identifying large number of bugs early in development.

How to use Bug Tracking for Bugzilla?

1. What is Bugzilla?
Bugzilla is a powerful bug tracking system which can make the reporting of bugs and responses run smoothly with our view in making our products better and more accessible for a large number of users. Through the use of Bugzilla, users can report their bugs , and receive feedback from a developer or an engineer. Bugzilla is not only for the real problem, but also for new functionality or product updates.

2. Before you use Bugzilla
This Bugzilla handles all packages on Turbo Linux's FTP site (ftp.turbolinux.com) except followings.
packages with version being before their Beta.
packages of commercial products
packages included in companion CDs

Reported bugs will be closed when bug is fixed. However there are some cases that will be closed with the following reason.

3. Access to Bugzilla
You can access Bugzilla at http://dev.turbolinux.co.jp/bugzilla/

4.Getting your account
You need your own account in order to use Bugzilla. It is available from the web site described above. You'll receive your password by mail just after getting your accounts at that web site.
Bugzilla will permit you to login with your email address you registered when you got the account and password you received by mail.
Information of your accessing Bugzilla was saved as cookies so that you can use the Bugzilla without logging in when re-accessing Bugzilla as long as the cookies are remained available on disks.

5. Your mail addresses to the public
You can choose whether you will have your email address is visible to the public or not. The word "the public" means that anyone who has the right to look over your bug report will know your email address because your email address is on the bug report. The benefit you have for presenting the address to the public is that every time any information is added to Bugzilla, it will be automatically sent to the address. In other words, you will not receive mail from Bugzilla if you don't have your address be to the public.
Because the system will assign a unique ID ,and replace with your email address on the log field of the bug report if you don't have the address be to the public ,and no one can know your address from the bug report. In this case, you have to check the latest information manually.
You can change your address's publicity once after you reported the bug. Although information already described on the report will remain on the field, please take a note that the previous publicity setting will be remained in already reported bug.

6. Report / Search the bug
This section covers how to report new bugs and search those bugs.
Report a new bug
At the site http://dev.turbolinux.co.jp/bugzilla/ , click "Enter a new bug".
When asked to login , login the Bugzilla using your account (your email address) and
password you registered when you got the account.
Now you have the window for entering new bugs.
In the window you can see some fields to which you put some information.
○Product
○Product version
○Platform
○Package
○Version/Release
○Priority
○Severity
○Justification for P1
○Assigned to
○Cc:
○URL
○Summary
○Description
○Defect Type

Interview faced by one of my friend

1st Technical round questions:
1) About my self
2) Questions on my current project
3) asked my role in the project
4) testing process in my company
5) Asked about V-Model
6) Asked about use cases
7) Asked which comes first test strategy or test plan
Ans) Test strategy comes first

Asked test plan and its contents
9) Asked how do u do risk analysis
10) Asked about smoke, sanity and regression testing.
11) Asked where u connect URL of database connection for the application
ans) it depends upon the framework and web server using for J2EE applications, we are using struts framework and web server-tomcat, in tomcat folder, go to webapps folder, u can see ur application build, open ur application folder, open web-inf, u can see struts conf.xml file( file depends),
open with text pad, am pasting a sample one....
property="driverClassName"
value="oracle.jdbc.driver.OracleDriver" />
property="url"
value="jdbc:oracle:thin:@hostname:1521:servicename" />

here hostname=ur company's server name like IP address
Servicename= ur company's service name of oracle test database( if any questions on these feel free to contact me will explain in detail as am Oracle certified professional)

12) Asked URL for application to open on web browser
Ans) it depends on server that ur using....i said http://localhost:8080/applcationname.
This is for struts framework
13) asked difference between 8080 and 8081
14) Asked is test cases are necessary?
15) Diff between test cases and use cases
16) asked abt VSS--->configuration management tool-->version control-->control and documents the current changes in the life cycle of project.( if any queries on this please revert me back)

After one week he got call for 2nd tech round, the questions are like these:

1) Questions on my present project.
2) Test plan and it contents
3) what is 'i' in oracle 9i ----> i refers internet
4) current version of internet explorer that i am using---> now a days they r asking these questions, so job seekers please
have a look on the versions that we r using...okay
5) diff between web server and application server..
6) questions on sql...
. types of joins
. what is a join
. Primary key
. what is referential integrity
. second highest salary from employee tab
. what is normalization
. diff kinds of normalization
. top 5 salaries from emp table
7) Asked on HTTP error codes---404, 500 ( keep an eye..okay..these are very important)
8) what is acceptance testing???

Hiring Great Testers!!

Hiring great testers is biggest challenge that test managers face. Unfortunately, industry is facing the serious shortage of experienced testers, while the numbers of testers with weak skill sets are increasing. Industry and acedmia both are in a way responsible for this situation. Not many universities have separate software testing courses. During early stages, industry has ignored the testing profession and many people felt that software testing is an entry level job to move into software development later. Currently, good testers are in demand, hiring and retaining them is a challenge for test managers. It is also job of testing community to create great testers out of fresh graduates.

While hiring testers, a manager basically needs to look for two qualities which I call A&A, aptitude and attitude. By Aptitude, I mean good quantitative and logical reasoning and by Attitude, passion and desire for testing and curious to know new things. While hiring fresh college graduates, always look for people with good A&A so that they can later be mould into good testers. While hiring experienced candidates, apart from A&A, earlier toolset skills can be looked at based on requirements. Rather than looking for past toolset experience it would be better if you can judge how faster he can learn the new tools.