John & Anna's Website


Aptitude Test For Software Quality Assurance

Are you stuck in a dead-end job because you have no marketable skills? Would you rather ask questions than answer them? Are you tired of working for employers who demand results? Then YOU may be qualified for a promising career in Software Quality Assurance! Just answer these 10 questions and see if you have what it takes to be a successful Software Quality Assurance Engineer!

1) Which of the following is a white box testing technique?

a)       Path Testing.

b)       Validation.

c)       Code Review.

d)       The question is vague – please clarify.

2) Most software defects are introduced during:

a)       Requirements gathering.

b)       Design and architecture.

c)       Coding and unit testing.

d)       The question is vague – please clarify.

3) Which of the following is NOT an acceptable Quality tradeoff?

a)       Extending schedule to meet quality goals.

b)       Reducing feature set to meet a critical delivery date.

c)       Making a “Buy vs Build” decision to meet budget and quality goals.

d)       Expecting me to work overtime.

4) What is an Equivalence Class?

a)       The set of all input conditions that are expected to produce the same result.

b)       The range of inputs over which the system will respond in the same way.

c)       A method of determining the set of tests for regression testing.

d)       The class I took to get my G.E.D. equivalent after dropping out of high school.

 5) Which of the following is NOT a proper method for reviewing test plans?

a)       Rejection.

b)       Misplacing the document.

c)       Accidentally setting it on fire.

d)       I’m sorry, what was the question again?

6) A risk-based software test methodology includes which of the following:

a)       Software Hazard Analysis.

b)       Focus on reducing safety risk to customer.

c)       Assessment of anomalies found in testing.

d)       Open cubicles, so my boss can catch me sleeping.

7) When participating as a team member I should:

a)       Consider the needs of all project stakeholders.

b)       Remember that there is no “I” in “Team.”

c)       Provide constructive criticism.

d)       Be vague – don’t commit to anything that could get me in trouble later.

8) In a regulated industry, it is important to:

a)       Know the regulations that pertain to my job.

b)       Train others in how my job affects them.

c)       Be proactive and remember why the rules exist.

d)       Always have an excuse why other people are to blame.

9) The purpose of Quality Assurance is to:

a)       Provide training in QA methods.

b)       Perform QA tasks as an integral part of a team.

c)       Ensure quality processes.

d)       Ensure that no one blames me.

 10) When you discover that a critical project is late because of you, should you:

a)       Blame the voice-mail system?

b)       Blame a team member at random?

c)       Ask what they mean by “late” and demand to know why they want you to compromise quality?

d)       All of the above.

11) When you absolutely must produce results, should you:

a)       Plagiarize?

b)       Call in sick?

c)       Find another job?

d)       Refuse to answer this question because we said this was only a 10 question test? 

To score the test follow these steps:

1.        Tally up the number of times you answered a question with “D”.

2.        Subtract the number of times you answered “C”, “B”, or “A”.

3.        Take the square root and drop the last digit.

4.        Divide the result by 12 if you answered question 11.

5.        Multiply by the natural log of the number of times you answered “C”, or “A”.

If you stopped scoring the test after step 1, then you may have what it takes to be a Software Quality Assurance Engineer!


About Us | Contact Us | ©2004 John M. Wyatt