These manual testing interview questions are based on my personal interview experience and feedback from other interviewees. Keep following this post for regular updates.
Q1. What is the difference between Regression and Retesting ?
- Regression Testing is performed to check unexpected side-effects even any code change has not unfavorably disturbed current features & functions of an Application.
- Retesting is a process to check specific test cases that are found with bug/s in the final execution.
Q2. What will be your approach if you are not clear about the requirement?
- I will look for specification documents if available and try to understand the requirement on my own.
- In case of any issue, I will approach BA for clarification. If BAs are also not clear, request them to confirm the requirement from business users.
- I will also take help from my peers if they have a clear understanding of the requirement.
Q3. Are you familiar with Agile and Scrum Methodologies? How they are different from others?
Agile is a continuous iteration of development and testing in the software development process which allows changed in project development requirement with an increment approach.
Q4. What are the Scrum Ceremonies?
Scrum is executed inside what are called Sprints and every Sprint is a short iterations of work which is usually of two weeks or lesser. A sprint has four different scrum ceremonies to ensure proper execution:
- Sprint Planning Meeting -
What are we going to work on, and how are we going to do it?
- Daily Stand-up Meeting -
What’s done on the prior day, what needs to be done today, identify any impediments, and creates visibility around the work that everyone is doing in the Sprint.
- Sprint Review Meeting -
Based on stack holders feedback, items will be looped back into the Product Backlog, where it can be added in the future Sprint.
- Scrum Retrospective Meeting -
What went well, what did not and what can be improved.
Q4. What are SDLC and STLC?
- SDLC stands for Software Development Life Cycle, which is a sequence of different activities performed during the software development process.
- STLC stands for Software Testing Life Cycle, which is a sequence of different activities performed during software testing process.
Q5. What is Defect Life Cycle?
A defect life cycle represents the flow of bug from newly open to until it closes. Simpler implementations of the bug life cycle may not include all the states, The defect life cycle can vary from organization to organization and also from project to project based on several factors like organization policy, software development model.
It has different states as mentioned below -
New Assigned Open Fixed Pending Retest Retest Verified Reopen Closed Duplicate Rejected Deferred Not a Bug
Q6. How do you raise a defect in HP QC and what parameters you key in?
To log a new defect in HP QC we navigate to Defects Tab -> New Defect. while adding a new test case we key in Parameters as follows - Summary Assigned to Detected in Release Project Status Priority Reproducible Description Attachment (Screenshots of error) Linked entities (If required)
Q7. How do you write a test case, what parameters you key in?
For adding a test case we key in Parameter as follows :- Test case Id Release Project Version Pre-requisite Test Data Test Objective Test Steps / description Actual result Expected result Status
Q8. What is the prerequisite to login on the home page?
- User should have required access and credential for login on website.
- User should have compatible browser version.
Q9. Suppose 10 tasks are assigned to 4 developers in a sprint. What will be your approach to test those development tasks?
Initially, my approach will be to test module wise and later will perform end to end testing once all developer code is ready to test.
Q10. What is priority and severity?
Priority is defined degree of fix and severity says how early it has to be fixed. The tester can set defect priority in case he/she is blocked to run further scenarios which are interdependent.
There is four combinations for these terms as follows -
- Low severity and low priority
- High severity and high priority
Example - On an eCommerce website, every customers get error message on the booking form and cannot place orders, or the product page throws a Error 500 response.
- Low severity and High priority
Example - Latest browser version, shows that the buttons are slightly overlapping with each other. Although, they are still clickable separately, the visual representation is getting disturbed.
- High severity and Low priority
Example - Customers who uses very old browsers cannot continue with their purchase of a product. Because the number of customers with very old browsers is very low, it is a low priority to fix the issue.
Q11. You have submitted the form and details will be saved in DB and result can be verified on third-party platform, What will be your test steps?
Test case steps are as follows :-
- Login to Page with valid credentials.
- Submit the form with required details.
- Verify expected response on web.
- Verify the submitted details Saved correctly on a third-party platform.
Q12. Your test outcome will reflect on a third-party platform, What will be your approach if third-party platform is down?
I will follow-up with the concerned team regarding this and will execute my test cases once it’s accessible.
Q13. What is static and dynamic testing?
Under Static Testing, code is not executed. It manually checks the code, requirement documents, and design documents to find errors. Hence, the name “static”. The main objective of this testing is to improve the quality of software products by finding errors in the early stages of the development cycle so it is a kind of verification process.
Under Dynamic Testing, a code is executed. It checks for functional behavior of software system, memory/CPU usage, and overall performance of the system. The main objective of this testing is to confirm that the software product works in conformance with the business requirements. This testing is also called an Execution technique or validation testing.
Q14. What is Sanity testing?
Sanity testing is a subset of regression testing. After receiving the software build, sanity testing is performed to ensure that the code changes introduced are working as expected. This testing is a checkpoint to determine if testing for the build can proceed or not.
Q15. What is the SQL query to fetch the no of records from the Database Table?
Select count * from table Employee.
Q16. What is different Test Techniques?
Test Techniques are as follows -
- Black Box Testing - also known as Specification based testing, analyses the functionality of a software/application without knowing much about the internal structure/design of the item.
- White Box Testing - also known as Structure based testing, requires a profound knowledge of the code as it includes testing of some structural part of the application.
- Experience Based Testing - Its a constant approach to studies, analyzes the product and accordingly applies his skills, traits, and experience to develop test strategy and test cases to perform necessary testing.