[Hỗ trợ – Phỏng vấn] Testing Interview Questions and Answers – 2
- What are CMM and CMMI? What is the difference?
- Do you have a favorite QA book? Why?
- When should testing be stopped?
- When do you start developing your automation tests?
- What are positive scenarios?
- What are negative scenarios?
- What is quality assurance?
- What is the purpose of the testing?
- What is the difference between QA and testing?
- Describe some problems that you had with automation testing tools
- Can test automation improver test effectiveness?
- What are the main use of test automation?
- Does automation replace manual testing?
- How will you choose a tool for test automation?
How we decide which automation tool we are going to use for the regression testing?
- What could wrong with automation testing?
- How will you describe testing activities?
- What type of scripting techniques for test automation do you know?
- What are good principles for test scripts?
- What type of document do you need for QA, QC and testing?
- What are the properties of a good requirement?
- What kinds of testing have you done?
- Have you ever written test cases or did you just execute those written by others?
- How do you determine what to test?
- How do you decide when you have ‘tested enough?’
Realising you won’t be able to test everything-how do you decide what to test first? OR
What if there isn’t enough time for thorough testing? Use risk analysis to determine where testing should be focused. Since it’s rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgment skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include:
· Which functionality is most important to the project’s intended purpose?
· Which functionality is most visible to the user?
· Which functionality has the largest safety impact?
· Which functionality has the largest financial impact on users?
· Which aspects of the application are most important to the customer?
· Which aspects of the application can be tested early in the development cycle?
· Which parts of the code are most complex, and thus most subject to errors?
· Which parts of the application were developed in rush or panic mode?
· Which aspects of similar/related previous projects caused problems?
· Which aspects of similar/related previous projects had large maintenance expenses?
· Which parts of the requirements and design are unclear or poorly thought out?
· What do the developers think are the highest-risk aspects of the application?
· What kinds of problems would cause the worst publicity?
· What kinds of problems would cause the most customer service complaints?
· What kinds of tests could easily cover multiple functionalities?
· Which tests will have the best high-risk-coverage to time-required ratio?