Transcript of 30 Scenario-based Manual Testing Interview questions & answers|Combined from 20 real-time interviews

hi friends welcome to a automation channel in this video Let's quickly see about 30 important realtime scenario based manual testing interview questions okay and I have few automation questions as well so these questions are combined from multiple manual and automation testing real interviews and why these realtime scenario based questions are very important because it shows how much hands-on experience we have working in software testing industry that is it proves you have really worked in realtime testing projects and not coming from any other background so candidates from another technology like devops or networking or development who is trying to move into testing industry can really make use of this video so please do watch the whole video this video is really going to help for your upcoming interview so let's quickly start and the first question is assume your application is having 500 total test cases how do you make sure all these test cases are tested after production deployments so testing all the test cases is literally impossible so what do we do here is we start by testing our regression test suit and make sure business critical test cases are working fine so once we complete regression testing and if we have enough time and bandwidth we go for validating low priority and UI test cases okay so because testing all the test cases after each and every production deployments is literally impossible so we validate the high priority test cases and make sure our application major functionality is working fine and if you have automation test suit available for all the test cases you can explain that scenario also to the interviewer okay so let's see the next question so how long you will perform smoke test and when do you perform smoke test and what are the test cases you cover as part of smoke testing so usually for smoke test we take around 20 to 30 minutes and smoke test is performed IM immediately whenever a new build is given for testing okay so what do we test as part of smoke test we test the pz test cases and make sure iCal features are tested that is we test one end to end flow as part of smoke testing okay and we don't take more than 20 to 30 minutes for performing smoke test okay so the next question is Dev is providing tickets to test very late in the Sprint regularly what will you do here okay so many projects face this issue we might get tickets to test very late in the Sprint so what do we do we take the high priority tickets early and we complete testing those High Priority tickets okay so to make sure the same issue is not happening again what can we do is we can talk about this issue in our Sprint retrospective meeting and make sure the same issue is not happening again so our managers and business owners might talk to development team and bring a solution to this issue so we can bring about talk about this issue in the Sprint retrospective me meeting okay so the next question is you said you are responsible for performing automation as well so when do you perform manual and when do you create automation scripts so many candidates say they are responsible for creating automation scripts as well so we all work in agile model now so when do you perform manual and when do you perform automation scripts uh so this is a tricky question okay so usually at the start of the Sprint we create test cases okay and then parallely we execute test cases whenever the ticket is ready for testing and we start Automation in the middle of the Sprint or at the end of the Sprint okay we usually don't start Automation in the start of the Sprint we in the start of the Sprint we start creating test cases and we execute test cases whenever a ticket is ready to test so for automation we start in the middle of the Sprint or at the end of the Sprint for new user stories you are responsible for performing manual testing and for those new user stories also you are responsible for performing automation whenever the user story does not have any major you can start creating automation scripts also for the new user stories okay so the answer here is we start Automation in the middle or at the end of the Sprint and we do in Sprint automation as well okay for the new user stories so let's see the next question what will you do when you identify a blocker issue so this question has been asked in many interviews so what will we do initially we should analyze the network logs or application logs and check what kind of issue it is whether it is a d issue or whether it is a server side issue and immediately create a critical PR priority ticket in your management tool test management tool or project management tool like jira attach logs and screenshots and also inform the team through mail or teams okay not only informing we have to follow up till closure of that particular major defect and once the defect is fixed and moved to production or staging you are you are responsible for performing one round of regression test also so all these things you have to answer in this question okay so let's see the next question so what will you do when requirements change continuously and you have very less time to complete newly added requirements testing so this is one common scenario we Face nowadays so requirements keep on changing at the last moment and what we can do is connect with our business owner and see why requirements have been modified and get clear functional knowledge about the newly added procurement okay that will be helpful for us to create test cases and notify about the timeline issue to your business owners and internal team managers because we have very less time for testing we might leave any test cases or test scenarios for validation so it is very important for us to notify about the timeline issued to the internal team members and business owners okay and please do make sure critical user stories or requirements are tested and delivered on time in this scenario so low priority tickets can be validated later but we have to make sure critical user stories are tested and delivered on time okay so let's see the next question what are the different types of testing you perform in your project they are not asking about what different typ of testing are present what different types of testing you are performing in your project so I am performing like smoke regression integration usability localization API database performance tesing so you can explain whatever types of testing you are performing in your current project so a defect is identified in production and how will you make sure the same defect is not occurring again so your defect is identify because it's a qms so it has been identified in production how will you make sure the same defect is not occurring again in production yes we can add that test case or test scenario to our regression test suit and make sure the same defect is not occurring again okay so what process or procedure you follow for performing manual testing this is an important interview question so in the beginning what do we do user stories get prioritized in the Sprint planning meeting and once the Sprint is started we start creating test cases and test case test cases will be reviewed by our test lead okay so if you have any clarification rise any to the business owners and you can start test execution once the tickets are ready to test so then we will rise defects and get it fixed and finally we retest the reported defects and move the tickets to Business review and the business test is done and the ticket status is moved to done and finally closed okay so this is the procedure or process we follow for performing manual testing so what type of software development model you are working on and why it is useful so as you know many projects are now following agile software development life cycle model because agile model focuses on rapid delivery of the working software okay so customer gets a chance to view the working software from start of the project to the end of the project okay and if he has any feedback it gets addressed immediately we won't wait till the end of the project okay also testing gets started in the beginning of the project in ail sdlc okay it focuses on continuous Improvement this is an important interview question okay aile is a popular software development life cycle model used in many projects because it's very successful okay so what strategy you are following for Designing test cases this is an popular interview question for Designing test cases we can follow techniques like equalent partitioning boundary value analysis de table testing and state transition technique okay this improves our test coverage okay this improves our test coverage like in positive way and in negative way also we write we should write test cases in a positive manner also as a tester we should focus on writing test cases more in a negative manner okay so these techniques helps us to improve our test coverage and why is localization testing important or necessary so localization testing is a popular technique testing technique nowadays okay because the website being developed not only works in the Home Country it works in multiple countries okay so if we have to test our website in multiple languages we have to test the currencies in multiple uh countries okay so for India it's rupes and for UK and us it's US Dollars okay so we have to test the websites in multiple languages and multiple currencies date and time formatting everything has to be checked okay so localization testing verifies and applications F functionality and usability in specific region okay and automating every test cases is possible or not that is 100% automation is possible or not definitely 100% automation is not possible okay there might be few test cases in your project where automation is not possible or impossible okay so be careful in answering this question because 100 percentage automation is not possible in multi many projects okay out of 10 N 9 or8 projects 100% automation is not possible okay so we depend on manual testing for those test cases where automation is not possible okay let's see the next question why regression testing is performed and what are the advantages this is an important interview question regression testing is performed when new functionality is added to the existing application consider a new feature is added to your website to make sure our existing test cases are also working fine we perform regression testing okay let's see the next question so consider you are testing WhatsApp messenger and what are the major test cases you will cover I've seen in many interviews nowadays interviewer ask about writing test cases to Whatsapp Facebook Instagram and Google Etc so please do prepare test cases before attending interview it will be really useful okay so for WhatsApp Messenger or Facebook initially start by telling what are the major test cases for the app like verify app installation is successful verify user is able to log in successfully with phone number and valid OTP verify uh user is not able to log in with invalid OTP and then once app is logged in so you can talk about the major scenarios like verify messages delivered verify video file attachment is successful and delivered successfully okay talk about UI related test cases at last while explaining test cases okay initially talk about major scenarios and then come to UI related scenarios like accessibility scenarios bold text scenarios Etc okay so this is an important interview question so please do read all the test cases here and next question is can you explain some test cases to test your login page okay this is also an popular interview question so please do read all the test cases so initial test case is to launch where verify application is launched successfully and then verify user is able to log in with different username and password combination like valid and invalid data so valid username valid password invalid username invalid password and you you can write as many combinations as you can and one important case is password password should be masked and verify account lock scenarios verify character length verify keyboard scenarios like tabbing and Enter key validations okay so verify page is compatible with multiple OS and multiple browsers verify different URL combinations so launch the login page with HTTP and without HTTP with www Etc these are some of the URL combinations you can test the app with okay and next question is can you explain some test cases to test a search functionality almost all the website have search boxes okay this is also an important interview question so initial test case is to verify search results are displayed successfully on entering valid search data enter valid data and search result should be successful that is the important test case okay then test next test case is verify no results found message on entering invalid test St okay verify search options are shown when you enter your search keyword okay verify search results are displayed when users select options from search options suppose when you type something some options will be displayed right when we select that option also search results should be displayed okay verify keyboard validations like Enter key tabbing and verify character length in the sarch box so these are some important test cases then you can talk about UI test cases like placeholder Etc okay and next question question is consider you are testing an e-commerce applications that sells and deliver products what are the major test cases you are going to cover here uh kindly note here what they are asking what are the major test cases you cover here so you don't have to talk about much negative scenarios here talk about the end to end flow here like how we are going to do a smoke test okay initial test Cas is to launch an application then login uh and verify user is landed in dashboard and then verify user is able to search products and add to C and then then verify user is able to apply coupon and check out and proceed to payment page successfully and verify user is able to complete payment and verify order status is shown as place and verify user is able to log out successfully here I am talking about only end to endend case I'm not talking about negative scenarios like validating error messages UI color text button color Etc okay I'm just talking about entry and flow from login to log out okay because they have asked only the major test cases here I think more than 12 to 13 test cases are there this is more than enough to explain in an interview okay and next question is can you explain what is acceptance criteria so if you are using jira or any other project management tools you can you would have seen a text called acceptance criteria in top of your requirement okay it means this below set of requirement should be met for this user story to be considered completed so this acceptance criteria will be set by your business owner consider you are developing a login page okay and acceptance criteria will be mentioned like the login page should contain username and password field with login button each field should accept 30 characters okay all these criteria should be tested and it should be working fine then only the business owner will accept the ticket and move to done status and close the ticket okay this is known as acceptance criteria so let's see the next question consider you have joined a new project and manager ask you to implement test process what will you do here okay so if the manager is asking to create a new test process what we have to do is clearly Define the test objectives like Define the test scope what are you going to test in this application and Define the test coverage and test priority okay you have to implement thorough test case review process to make sure all the scenarios are covered and Implement risk-based testing and you have to maintain proper test data management okay and make sure you are automating repetitive test cases to avoid unnecessary manual testing also okay so these are some of the major things you can do if someone ask you to implement test process okay so let's see the next question without proper documentation how will you test or design test cases okay so we have to understand the entire scope of the project here and research for similar features and design test cases accordingly okay and what else we can do is connect with your business owners and get an idea of what is their expectation and then then we can start designing test cases okay once you get an mock images or wireframes from the business you can enhance your already developed test cases okay this is how without proper documentation we can start creating test cases let's see the next question you found a defect and developer says it's not a defect what will you do here this is a funny question so we find found a defect and the developer started saying it's not an defect or he is not going to fix it because he feels it's not a def okay if you still feel you have clarification then you have to confirm with your business owner so many testers I have seen they will just close the defect because development conver confirmation he's confirmed that it's a not and defect but if you still feel or you have clarification you have to take it to the business and confirm confirm it with them okay because they are the final owners okay so we basically have to get confirmation from them and how Sprint velocity is calculated this is recently asked in many interviews okay so if Sprint Sprint one has 20 story points and Sprint two has 21 story points and Sprint three has 40 story points how we can calculate Sprint velocity is add these overall story points and divide by the total number of Sprint that is 20 + 21 + 40 divided by 3 so 27 is the Sprint velocity here okay so next question is why agile model is useful and what are the benefits you see in agile software development model so it's useful because we deliver the software frequently and customer teams gets a chance to review the software every 2 or 3 weeks so they can provide their feedbacks and make changes very quickly okay so in other models testing is done at the end of the trade which has led to many issues that's why aile model is a successful model in our current software testing industry or development industry as well so how do you make sure applications performance is good when there is a large user load so you can talk talk about how we are doing performance tesing here so many projects used J meter and many projects use Google search console for capturing performance metrics so if you're doing it Sprint phas you can explain in to the interview that we are capturing performance metrics every spin twice that is after production deployment we do performance testing as well and make sure our application performance is stable okay and the next question is how do you validate or what do you validate as part of API testing okay as part of API testing we validate status codes and verify whether the API returns successful status codes like 200 and we perform data validation testing like we verify the content the body and we validate against the expected values here and we also check for response time and we check the content type and content length as part of header verification as well okay so these are some of the things we validat as part of API testing and why do you think automation testing is necessary because automation testing saves cost and saves lot of manual effort we automate repetitive test cases so that manual testing is avoided here which will save a lot of lot amount of cost here okay and next question is what are the different fields or components in a test case template or in jira okay the different components like test case description test steps actual and expected results sity test data status date tested and tester name these are some of the components in the test case template or in jira so many of us are creating test cases in jira instead of excel right these are the components we can add okay and next question is what are the different fields components or your user story goes through in a test management tools like jira that is from start to the end you have to explain the different components your user story goes through in your test management till so initially as you know it will be in open State and then it will be assigned to the developer so developer moves to in progress State once development is done it moves to development done status okay and then it will move to in code review status one code review done it will be resolved and move to testing State okay what will we do we will move it to in verification State and we will reopen if it is not working fine or if it is working fine we will move the ticket to Business review and they will validate the ticket and move it to done status and finally the scrum master or any business owner will close the ticket so these are the different components a user story goes through in a tool like jir okay the last question is explain about your automation test process so where do you start test scripting to how do you merge the code to G repo you have to explain about the entire process initially we read the requirements or test cases and we start creating test scripts and once we create test scripts we commit the changes to get and code review is completed and we will create a PR and me the changes to master branch and we verify the logs in bamboo or genkins pipeline as well this is the automation test process many of the projects are maintaining okay so we have come to the end of today's video I hope this video will be really useful for your upcoming inter interviews so please do subscribe our Channel aay automates and watch out for more testing training and interview preparation related videos so thank you again take care see you next time bye