Testing Theory:

Question Level
Which techniques of test design do you know? Junior
What is test plan Junior, Middle
What is the test strategy Junior
What testing types do you know Junior
What is static testing Junior
What is traceability matrix Junior, Middle
Main Attributes of TestCase. What is the good testcase? Junior
Main Attributes of Bugs Junior
What is regression testing, smoke, sanity Junior, Middle
What is the most common cause of software failing to meet the user Junior, Middle,
requirements? Senior

What do you understand about the cost implications of bug finding during the Junior, Middle,
project lifecycle?? Senior

How is testing in an Agile/SCRUM model different to testing in other models? Middle, Senior

Situations:

1. What if you have 2 days before release and you have regression tests for 4 days, what will you
do
2. What if you find critical bug 1 hour before release? You are about to release a product and have
found a potential issue that could impact the release, what would you do?
3. What if you find a bug but developer disagree that it’s a bug
4. What will you do when bug is fixed and new version is deployed? Alternative question: You’ve
been given a new piece of software to test. What would you do?
5. In an application currently in production, one module of code is being modified. Would you say
it is necessary to retest the whole application or is it enough to just test functionality associated
with that module?
6. How would you go about understanding your customers – i.e. the users of your product?
7. You are getting to the end of a Testing project. According to your test estimates your tests will
overrun past the deadline for the tests to be complete? What would you do in this scenario? For
regression do you use all of tests for feature?
8. Have you used any automated testing tools? If so, which ones and were they successful?
9. If not, what do you understand about automated testing?
10. Are there any tests you would consider not good to automate and why?
11. What would you suggest are good criteria for a well written automated UI or API test?
12. Do you have experience in testing microservices?
13. How to ensure that the whole system consisting of many services works. Is testing single
services enough?
Practical tasks:

1. This is the desktop application. You enter your age, click OK and program shows you below your
age. How would you test it?

2. Give 5 high-level areas or types of testing you would execute on a cash machine and, briefly,
why?
3. How would you test a cash machine?
4. How would you test an elevator in the business center?

SQL:

1. Which constraints do you know?

2. What is primary and foreign keys?
3. What’s the difference between Left Join and Inner Join?
4. What is the purpose of indexes?
5. Are NULL values same as that of zero or a blank space?
6. What is subquery in SQL?
Put a practice example here

API testing:

1. How to authenticate API Calls. What are the methods (tokens, oauth, private/public key signing
requests)
2. We expose a REST API. How do you test it
3. Do you know POSTMAN? You have a postman collection. Can you automate tests with it?
4. What does it mean if you receive an error starting from 4 ( or 5)?

Automation testing

1. What would you suggest are good criteria for a well written automated UI or API test?
2. Cucumber. Gherkin syntax. How does a scenario look like?
3. Selenium. How do you select a component (ex. A button to click). Why
Ex. Xpath id.
 Sometimes the frameworks create ids automatically at build time. In such case searching by id is
not a good way.
4. Do you write the underlaying code or just the scenarios. If yes in what language
5. We run automatic tests when merging code to master and before release. It starts to take long
time, what do you do?
6. What is the purpose of serialization and deserialization
Deserialization is changing the json / xml data into an object. What we do when we get the data
back from the api. Serialization is when we send the data from our objects. Turning the objects
into json and sending it to the api
7. What are the automation challenges that SQA(Software Quality Assurance) team faces while
testing? Automation questions
Mastering the automation tool
Reusability of Automation script
Adaptability of test case for automation
Automating complex test cases.
8. Can list out some disadvantages of manual and automated testing?
Manual Software Testing requires more time and more resources.
Inaccuracy
Executing same test case repeatedly is error prone and boring.
It is impractical to do manual testing on very large projects and time bounded projects.
9. On what basis you can map the success of automation testing?
By following criteria, the success of automation testing can be mapped
Defect Detection Ratio
Automation execution time and time savings to release the product
Reduction in Labour & other costs
10. What types of tests would you not automate?

Performance testing

1. Experience with performance tests (ex Jmeter). Do you know how to simulate 1000 requests a
second?
(You need a couple of machines for sending requests, one would usually not be enough for
sending big number of requests in small amount of time.)
2. What are the different types of performance testing (e.g. on the example of elevator)

Fit questions

1. Why do you want to change?

2. Tell us about a time you made a significant contribution to the team.- In your last job did you see
any opportunity of improvements
3. Tell us about how you collaborate with a team mate in a project -> did you use some kind of tool
for that? (spreadsheets..)
4. Tell us a disagreement you had with a person in your team and how you resolve it
5. How would you feel if a teammate gave you unasked advise or direction
6. How your teammates describe you?
7. What is the person that you would hate to work with like?
8. What is the person that you would love to work with like?
9. What is your approach to keeping your testing skills and knowledge up to date? Give examples
where possible?
10. Why QA at all? What do you like in the profession
11. Are you backend or UI person? What do you prefer - testing internal logic of the application or
user experience or design?