I'm not saying that these are just questions that are asked, but some samples for examination. These are the questions I used when interviewing others:
1. How many test scripts can be written in a day?
I'm looking for here in the capacity to evaluate. Although in reality the issue is impractical, because it depends on many different factors, I'd like to see the interviewee to come up with some kind of answer. When evaluated, it is necessary to make assumptions and to hit the figure allows someone to write estimates faster.
2. How many test scripts can you do in a day?
This is a repeat of the first question. I usually ask directly one after the other. Resources with less seniority tend to discuss the issue first, then the second also. The best way to learn the first question and answer in a more positive one. Now I'm not just watching ability to evaluate, but also the ability to learn and an indication of how likely seniority in the future.
3. Do you see the test as a service or a discipline?
Personally, I am very passionate about it. I love to see testing as a discipline and part of the software life cycle is also important that the analysis, design and development. What I'm trying to understand why each person came from. Councils may require reflection and a person coming from either background can adapt, but I would say it is easier to return to the service discipline than the reverse.
4. What is more interesting than the defect found?
It is a matter of passion. I can not wait to see if a person can be said of the case and to what extent the details. This is starting to tell me if they are career as a test driver or someone who makes it work.
5. What are the main components of a test script?
Someone posed scripts every day should be able to define what information should be recorded. Different organizations have different rules, but there are key aspects of the response. The requirement referred to or potentially included to show understanding that the scripts must always meet their point of origin. The script must be measured through each of them defines the action to take, data to be used and if the step correctly or not. This is the most basic and fundamental freedoms to all testers so the inability to provide this information is probably not the candidate.
6. Can you define Black, White and glass box testing?
This question is used to determine whether individuals have a basic knowledge of the jargon of the evidence and assist the Foundation in Software Testing ISEB, black and white are covered. The inclusion of the glass box throws people completely, while others reflect and try to define the response, immediately set some glass box as the same as the white box.
Scenario based questions
You are responsible for testing in a project. The code will be delivered late and you have to complete four weeks of trial in two. How will you deal with it?
I am looking for management thinking and understanding. There are many ways to solve this problem, additional staff, overtime, weekend work, shift work, risk-based test, poor performance. The question is, how many can come up and make them understand how they can achieve and related problems.
Risk Based Test - How they go? Evidence and are grouped by the risk? Requirements and grouped by the risk or risks identified against each.
Add a stress test - although still a test aimed at a more simple way at the same time, you should be aware that other departments will also be applied to similar resource allocation, which covers the outside working hours , to address increasing defect fixing.
