Testing Interview Questions

1.How do you maintain existing module?
2.What is the 'Software Quality Gap'?
3.Which functionality is most visible to the user?
4.Which functionality has the largest safety impact?
5.Which functionality has the largest financial impact on users?
6.Which aspects of the application are most important to the customer?
7.Which aspects of the application can be tested early in the development cycle? Which parts of the code are most complex, and thus most subject to errors?
8.What do the developers think are the highest-risk aspects of the application?
9.Which tests will have the best high-risk-coverage to time-required ratio?
10.Can you tell me the data flow in the module?
11.Can you differ data flow and control flow?
12.You said one more generic what do you mean by that?
13.What is CM Plan?
14.What are your day- by-day activities?
15.What is the current and expected Package?
16.Rate your self in WR?
17.Describe some problem that you had with automating testing tool.
18.Can test automation improve test effectiveness?
19.What are the main attributes of test automation?
20.How will you choose a tool for test automation?
21.How you will describe testing activities?
22.What testing activities you may want to automate?
23.describe common problems of test automation.
24.Can the activities of test case design be automated?
25.What skills needed to be a good test automator?
26.How to find that tools work well with your existing system?

[B]Question asked by visitor lokesh[/b]

A quality gap exists when a market offering does not meet the customer’s expectations. This means the presence of market or technical risk.

High quality leads to:
-> Low risk----Low risk means little deviation from the right market offering. The right market offering is one that meets customer expectations.
-> Right market offering
-> Customers will buy
-> Profit

[B][COLOR="black"][COLOR="Red"]18.Can test automation improve test effectiveness?[/COLOR][/COLOR][/B]

the answer is YES...
But only if you do it in a planned way and realise the impacts before starting the automation.
One should have a clear understanding of what can be automated and what can't
MOre over the main issue to address is the reusebility of the code the more reusable your code is the better.