Software Tester Job Interview: Case studies on Test Design



  • Case Studies during job interview is a great technique which allows to find out how the candidate would behave in different situation. For instance, the following case: Given a developer implemented a small new feature which adds the ability to show the latest earned badge on sqa.stackexchange.com. There are no written documentation/requirements for this feature, but you can gain an access to developers environment and ask any questions. When would you plan to finish testing this enhancement? How are you going to test? I am looking for examples for such cases. Could the SQA community help with examples? For instance, some cases may require the answer “I would use a boundary analysts”. Then the candidate should prove he/she understands this technique by defining the boundaries for particular case. Or the candidate may select another technique and prove he can complete the task (case) with this decision. During my research, I've found this great answer from Justin on topic Techniques for test selection, give a large suite of test cases, which I am going to convert to a case study. Also, I've got some insights from topic: How should you interview for QA positions?



  • Checking black-box and white-box skills You've been given a task to test the isPalindrom(String text) : boolean function. What are test cases you would propose and why? Now implement the function under test yourself. Are you seeing some more test cases to verify? We used that question at our interviews, inspired by What are the test cases or test scenarios for palindrome. Another case we used. You have a function that takes coordinates of two rectangles and tells whether they are overlapping. What test cases can you think of? How would you group them? Those are pretty abstract questions, say math-related, though the first one can reveal practical problems as well, e.g., related to character encoding with multiple bytes (UTF-8 vs UTF-16). We still wanted to have something more like your original case, but related more to the backend testing and verifying ability to test on different levels/tiers of the system. A tool that migrates data from database A to B has been developed. The tool will be used to migrate all production data from version 1.0 of our app (operating on A) to version 2.0, currently being developed (operating on B). The schema may differ between each other. How are you going to make sure the application is working after migration? Provide your test strategy and sample test cases. I took the idea for this question from my own experience: I gathered requirements, developed and tested such a tool, and even asked how other would test it: How to test data migration procedure?.



Suggested Topics

  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2
  • 2