I created this test to gauge the aptitude of potential QA Engineer applicants. The intent is to find out whether the applicant is more than just bright and creative and whether they have a knack for testing. I was looking for an innate curiousity about how things are built and what combinations of variables and configurations are interesting to test. I was also looking for a strong sense of how things should work and the ability to articulate it. The question: Come up with a list of input strings you would want to test.
- An actual word like "banana"
- "A" vs "a" - case shouldn't matter
- A simple legal case with no results "!@#@!$#@!#@"
- null
- "AA" vs "aa" - a case where the count is greater than 1 and all characters entered are the target character
- "b" - a non-blank, legal case with a negative result
- "aba" - target character at the beginning and end to look for an off-by-one loop
- "bab" - target character in the middle of a string
- spaces/tabs/etc - how are white spaces taken into account
- ABABABABABABABABABABABABABABABABABABABAB - enter in a long string with A's (is anything being truncated?)
- XNXNXNXNXXNXNXNXNXNXNXNXNXNXNXNXNXNXNXNX - enter in a long string without any A's
- What happens if the user enters in an A in a foreign language?
- Is this field susceptible to a SQL injection?
- will entering in HTML or Javascript cause the page not to render correctly?
Dave Boudreau
dboudreau@gmail.com
@xoxodave
This work is licensed under a Creative Commons Attribution 3.0 Unported License.