experience interview questions on manual testing
experience interview questions on manual testing
File Name:experience interview questions on manual testing.pdf
Size: 3400 KB
Type: PDF, ePub, eBook
Uploaded: 25 May 2019, 17:19
Rating: 4.6/5 from 551 votes.
Last checked: 5 Minutes ago!
eBook includes PDF, ePub and Kindle version
In order to read or download experience interview questions on manual testing ebook, you need to create a FREE account.
✔ Register a free 1 month Trial Account.
✔ Download as many books as you like (Personal use)
✔ Cancel the membership at any time if not satisfied.
✔ Join Over 80000 Happy Readers
experience interview questions on manual testing
The site to be tested was a simple customer-facing website (sort of like an online TV channel) that had both Web and Mobile components. So they decided to collect the QA interview questions from the previous attendees and they gave me a questionnaire. They wanted me to give the answers to the next candidate and coach that person to be successful in the testing QA interview. Surprised- because the questions were really basic and a 10 year experienced QA should have been able to answer them easily. After being done with the exercise, I thought it would be nice to share this experience with the STH readers. For beginners, this will be good live exposure. For others, it will be a friendly reminder of how important fundamentals are no matter how experienced we are. Answer: Step 1: is to get a thorough understanding of the AUT: This could be by reading the requirement documents thoroughly. In other words, we identify the test requirements. The focus in this step is to identify “What” to test. The outcome of this step is a list of Test Scenarios. Step 3: Once we have the test scenarios, we concentrate next on “How” to test them. This phase involves writing detailed steps about how to test a particular feature, what data to enter ( Test Data ) and what is the expected result. Answer: Following important fields should be included in a good Bug Report: A unique ID Defect Description: a short describing what the bug is. Answer: With any application that we test, we are trying to see if a certain set of requirements are met by the application or not. But when it comes to a user-facing site, apart from concentrating on functionality, we also have to look into a few usability features, maybe performance and security aspects also to a certain extent. The first level of testing is: Does the site satisfy its functional requirements. The next level of testing is: how easy is it to use the site, do the options make a logical sense and meet the expectations of the user or not.
experience interview questions on manual testing, 2 years experience interview questions manual testing, interview questions on manual testing for 2 years experience pdf, experience interview questions on manual testing job, experience interview questions on manual testing questions and answers, experience interview questions on manual testingng, experience interview questions on manual testing questions.
For Example, if the user has to be pass 3-4 screens to submit the basic information they are going to be annoyed, so such issues have to be addressed. Another example, after entering username and password, the user might click on the tab- which means the control should go to “Sign in” button, instead if it’s going to cancel, the user is going to be really annoyed and the experience of using the site is going to be compromised. Such issues have to be caught. For Example, if I leave the site idle for more than 10 minutes, is it auto logging out or not. Answer: IF the detailed standard documentation like BRD and FSD are unavailable, the tester will have to depend on some point of reference. Screenshots A previous version of the application Wireframes, etc Another factor that helps immensely, is to talk to the developers or the business analysts (when available) to get a confirmation on our understanding or clarifications in case of doubts. When none of these situations works, we can just conceptualize the application based on our previous IT application experience and create the basic set of test scripts. Answer: The key is to make sure that all the testers know about all the modules and that there is no knowledge concentration in one place. Involving everyone in test script peer reviews, defect meetings, and KT sessions are going to ensure that everyone is aware of the application to the best extent possible. Also, by encouraging the concept of teamwork we can have the team members collaborate, help and aid each other for better productivity. Answer: The onsite coordinator is a point of contact for the offshore team and to the client for any information regarding the testing engagement. A real value-add to a tester’s job is when we involve ourselves in the Root Cause Analysis process for a bug rather than simply reporting it. If there are logs, system files or anything like that, that might help us find any evidence of the issue- we should try to find it.
Answer: How to test an application having video or audio. Answer: Mobile App Testing Important Test Scenarios: Check if the app works well with multiple carriers and multiple devices. Usability of the features on a mobile screen. Installations, uninstalling, launching the app with network and without a network, testing functionality. Logs at iOS iPhone configuration utility for Android Monitor.bat can be used for debugging. That was it. Now, it wasn’t that simple. I conclude, hoping that this effort will be beneficial and meaningful to our readers. Please let us know below in the comments section on how we did. Author: This post is written by our STH team member Swati Seela.Reply alpesh October 8, 2018 at 10:30 am Both severity and priority are High Since application does not appear in results, chances of failures are more. Reply Deepty March 28, 2016 at 11:17 pm I have been to an interview recently where I have been asked quite tricky questions like 1. if you have reported a bug and developer says he cannot reproduce it.Still developer doesn’t replicate it then you probably need to take it to manager for further discussion and decision making in the defect call. For point 2, i second Swetha’s views mentioned here. Reply venkat April 5, 2020 at 6:31 pm Large number of Test Cases, you must be able to prioritize test cases as not all of them will have same priority. You may end up with High Priority, Medium Priority, and Low Priority set of Test Cases. Reply Kaustubh May 25, 2016 at 10:54 am Would like to thank Swati for the such a good article. The content is really and practical as well. Do keep sharing similar kind of information. Rgds Reply Rosi June 22, 2016 at 1:37 am Nice explanation for each andevery question for above duscussed questions.Reply Ramachandran July 15, 2016 at 2:03 am Thanks for this useful article, it is giving hope to bring new ideas!!
Reply SUsil July 24, 2016 at 6:40 pm Hii All, 1-Can anyone tell me which automation tool is more popular UFT or selenium? 2- Can anyone share some experiences of automation interviews. Reply dhanalakshmi July 28, 2016 at 8:28 am hi thiz is dhanalakshmi.Really helpful. Reply radika August 2, 2016 at 8:18 am There is a one page in that 1-100lines are present,how we will click 50th line. There is a one home page how we will write xpath for all elements present in that home page dynamilly. I am still looking for real time questions in testing.Reply divya May 24, 2019 at 5:15 am As per terminology Smoke should be performed first then Sanity sathish September 4, 2019 at 6:16 am Smoke test only, for checking the stability of the application we need to perform smoke test first, then only sanitary testing Reply Mukta November 8, 2017 at 1:52 pm Hi, Excellent set of questions. Thank you for posting it. Though I have 2 questions: 1. what are test estimation techniques. And, you dont have time to do full regression.Reply Sagar Pandya December 13, 2017 at 3:23 pm Can be more detailed, but good effort. Reply Supriya January 25, 2018 at 7:57 am There are 3 piece of code to be tested.Code B is dependent on code A and code C is independent. Now code B is ready for testing but code A is not and code C is ready for testing. What approach will you follow to test it. Reply Padma January 9, 2019 at 3:17 pm Will go with Code C first as this is independent part Next code B excluding code A part as code B depended on code A Then after will go with code A Reply ravi gk June 14, 2019 at 5:51 am we can follow bottom-up approach, by using driver(duplicate module) for code A. code B is ready for testing but is dependent on code A. Drew Henderson February 15, 2018 at 7:15 pm My question is, I am a Manual tester, but want to take steps to be an Automation tester. I am stumped as to where to start learning on this. 1. What will I need to be a successful Auto tester 2.
What are the step by step actions that I need take, from the very basic. 3. I do not know a language (example: Java). These are a few questions that I have. Reply Swapnil January 18, 2020 at 4:40 am 1. Learn all BASIC JAVA concepts. (plenty of free courses are are available or you can subscribe to paid courses on udemy. Use you tube for basic tutorials. 3. Once you get familiar with very basic Selenium concept you can research same on udemy for selenium tutorials. One more thing, without a programming Language its impossible to become a Automation Tester. And JAVA i thing is easiest to learn. Reply Balleshwar Jha January 29, 2020 at 11:46 am first of all tui Mr. Sankar ar sathe contact kor tar por tui nijar gar ta oke dis taholei hoya jabi bal.Reply Saurabh March 16, 2018 at 7:35 am I believe interview is an activity where we must be knowing that how to speak, what to speak. If we know the answers of questions but not able to speak than it won’t work out. Every-time it doesn’t possible that we know answers of all questions asking by an interviewer. But in this condition we must be know that how to tackle. I hope everyone would be able to relate these words if any of the questions you got stuck or not able to answer. All The Best!! Reply Sonam February 8, 2020 at 3:35 pm awesome!! Reply sameer April 16, 2018 at 10:34 am Very useful Reply teju April 23, 2018 at 6:19 am I wasn’t able to answer a few tricky questions during my interviews. This blog from you helped me in preparing answers for such questions, with the help of tips shared. Thank you so much. Reply Srikanth June 27, 2018 at 12:21 pm Q: If there is a bug which you missed to report and your product release date is near. And, you dont have time to do full regression. Thank You! Few query below: 1. What is the difference between Test Script and Test Scenario? 2. Please provide material on Test Estimation. Reply Mahesh February 14, 2019 at 8:38 am The application is functionally and independently stable.
In UAT testing again is it necessary to do regression testing. Reply Anand March 21, 2019 at 5:36 pm As i understand, smoke testing should be done first. Smoke testing is done just before the build is accepted for system or regression testing. It describes the readiness of the build for further testing. On the other hand sanity testing is done just before the product is ready for delivery to the client i.e., at the last stages of the test closure just to ensure nothing is broken before it is shipped to client. Reply Kushal April 21, 2019 at 2:55 pm Hi, This is Kushal. I have experience in SEO and m interested in software testing domain. So, want to switch on to Manual testing. Please if some could help me regarding the required concepts and if there is any openings for Manual testing. Reply Halim May 26, 2019 at 10:07 pm Hello, As a French teacher, I took Manual testing class long time ago. Now I want to come back to this field. Can anyone help me or guide me how to write a role of Manual tester for my interview. I am writing a query which gives me lakhs of records. Now each record I have to request to the server. Reply Nandita June 9, 2019 at 6:17 pm You been assigned new work as part of an ongoing project. You have never had exposure to the technologies used, or had the opportunity to test anything like this before. The only thing you have been provided is a high level overview and the User Story that provides a bit more technical insight. In addition, the lead developer has given you a list of possible tests that need to be performed. She is available to answer any questions you may have. Most of the development has been completed barring some small changes. You been given 2 weeks to complete the testing. Reply Saju July 4, 2019 at 4:36 am Where did you get this question from. You are responsible for the testing across a number of projects. Due to the nature of the product life cycle, some teams don’t always require testing on an ongoing basis.
You are currently working on an important piece of work, however you been informed that you need to help test a critical part of the backend. The development of it was delayed and so now testing is crucial. At the same time, an additional small piece of work has been sent to you, which needs to be tested ASAP, and is due to be deployed into production tomorrow. Briefly explain how you would manage this sudden influx of work. Reply Saju July 4, 2019 at 4:43 am Tessian?:-) Reply Honey Jazz November 28, 2019 at 9:27 am Hi, i had attended an interview to which i am searching answer for. So the question is If u have completed all testing and release is day after tommorrow and it is the deadline like u have to submit it. But next day another Software with some new OS version has release with which ur software is not compatible.Reply Sonam February 8, 2020 at 3:14 pm Very Helpful questions. Reply soniya July 12, 2020 at 4:35 am Thanks for sharing useful information,Please keep posting. Reply Ranu August 7, 2020 at 11:39 am What is retrospective testing.Reply Bavani August 28, 2020 at 2:06 am Retrospective meeting is end of the each sprint which the scrum master conducted and as a team we discussed about what was done well during the sprint what worked well and what didn’t work well and could be done to improve the work for next sprint. It helped to progress our project make it us success. You will absolutely love our tutorials on QA Testing, Development, Software Tools and Services Reviews and more. They have thought through all the answers and tried the best to keep them simple and easy to remember. However, if you like to improve any of the answers or wish to add a new question, then do let us know. These could help you in presenting yourself with confidence.
Follow professional etiquette Show your confidence Make proper eye contact and stand straight Brace for a great start Dress well ( Prefer a formal outfit) Neither talk too much nor pretend to be too familiar Be polite while replying Take time to think before answering a question Ask questions about the job profile and the business unit Don’t show any desperation Be authentic, candid and concise Thank the interviewer in person The list of most important manual testing interview questions appears next. Read them all to boost your testing concepts. It qualifies a system on various aspects such as usability, accuracy, completeness, efficiency, etc.Here are some compelling reasons to prove why is it needed. Once you get the requirements baselined, System testing plan and test case preparation should start. It also helps in exploring any gaps in the functional requirements. If it is on the higher side, then PO and EM can decide to stop testing. If the team achieves the desired level of code coverage (CC) ratio, then they can choose to end the validation. It may bring changes in the process and cause to replace the weak practices if it identifies any. It includes review activities such as the inspection of documents, test cases, source code, and automation, etc. It also results in changes to the product. It includes different types of testing to perform, which are functional (unit, usability, integration, etc.) and non-functional (compatibility, security, performance, etc.). It comprises of the following activities. It comprises of the following activities. They treat the software as a black box and validate it as per the end-user point of view. It helps uncover potential flaws in the software. It gathers data from the product description, requirement, and use case documents. Whereas, the Test Plan document contains test cases corresponding to test scenarios. 2.
Master Test Plan captures every test to be run during the overall development of the application, whereas the test plan describes the scope, approach, resources, and schedule of performing the execution. 3. MTP includes test scenarios for all the phases of the application development lifecycle. Whereas, a separate test plan also exists for the Unit, Functional, and System testing, which includes cases specific to related areas. 4. A Master Test Plan suffices for big projects which require execution in all phases of testing. However, preparing a basic Test Plan is enough for small projects. Each test case intends to test the application functionality. Testers define the test data according to the test requirements. They can do it manually or use generation tools. This metric helps testers to add missing test cases. How would you ensure it? But you can follow the below steps to come closer. It is useful in testing that follows the bottom-up approach. These are relevant for testing that uses the top-down approach. In this case, we call module-B as the Test Stub. 2. Now, module-B can’t send or receive data directly from module-A. In such a scenario, we’ve to move data from one module to another using some external features called Test Driver. They make up for missing components to simulate data exchange. It first validates the High-level modules and then goes for low-level modules. In this, testing occurs from bottom to up. Finally, it verifies the integrated modules to ensure the system is working as expected. It verifies the whole system to ensure that the application is behaving as expected. However, it should happen before the UAT (User Acceptance testing). It requires you to identify the most basic test cases for execution. For example, if we are testing a calculator app; we may multiply a number by three and check whether the sum of the digits of the answer is divisible by 3.
It certifies that the code can handle the desired international support without breaking any functionality. And also, it ensures that there would be no data loss and display problems. It is beneficial because this does not require Dev to complete coding for starting QA. Instead, the coding and testing both go hand in hand. However, it may require continuous customer interaction. It expects them to have the following attributes: It gives users access to public classes, functions, and member variables for calling them from external applications. It lays down a model for components to being interaction with each other. It makes use of the code and a programming tool to call the API. It ignores the UI layer of the application and validates the path between the client and the API. The client software forwards a call to the API to get the specified return value. API testing examines whether the system is responding with the correct status or not. They don’t have permission to get to the source code but can use the API calls. This testing covers authorization, usability, exploratory, automated, and document validation. Sometimes the client also does it, and in some cases, it may get outsourced. It is to ensure customer feedback before final delivery. Whereas, in the pilot test, few members of the testing team visit the customer site to set up the product. They give their feedback also to improve the quality of the end product. Let’s see what all color box testings are available. It got invented by Tom McCabe. Also, in many cases, it simulates failures to validate whether components support redundancy or not. This reference baseline refers to the last accepted test results. If there are new changes in the source code, then it requires re-execution of tests to form the current baseline. If the latest results get accepted, then the current baseline becomes the reference.
The objective of performing end-to-end tests is to discover software dependencies and to assert that the correct input is getting passed between various software modules and sub-systems. It also helps to estimate the number of faults remaining in the program. But we should get all assumptions well documented in the test plan. If yes, then we can say that there are enough test cases to test the product. Finally, the QA should carry out System testing. When the execution of all test cases finishes with a success, it indicates that the code has met the requirements. They can negatively impact the scope, quality, timeliness, and cost of a project. But it’s the leader who ensures that the whole team understands the individual role in managing the risk. It also prioritizes the sequence of resolving the identified risks for testing purposes. This type of risk has no impact on the company business. It focuses on the following two aspects. We, as a tester, first of all, write down the use cases for all the possible workflows of the said features. It allows us to integrate manual, automated as well as framework-based test scripts in the same IDE. It defines the full functionality of a product. Most of these tests take the form of user or business cases that resemble the standard transactions. Some of these are as follows: Some of these are as follows: They often get called System’s Quality Attributes. It is a testing model that proposes to execute test execution in a systematic and planned way. In the STLC model, many activities occur to improve the quality of the product. If some specifications are not precise or have a disagreement, then the stakeholders like business analyst (BA), architects, customers provide clarity. It is a crucial step as the team here defines the whole testing strategy for the project. Hence, it gets also known as the Test strategy phase. This phase starts soon after the RA phase gets over.
After the planning ends, the testing team can begin writing the test case development tasks. In this stage of STLC, the principal activity is to write down specific test cases for the requirements. While performing this task, they also need to prepare the input data required for testing. Once the test plan is ready, it needs to be reviewed by senior members or the lead. It is an industry-wide standard for ensuring the test case gets correctly mapped with the requirement.Only after the test setup is available, the team can determine which conditions the application would go through testing. The team or any member outside the group can also help in setting up the testing environment. In some organizations, a developer or the customer can also create or provide the testing beds. Simultaneously, the test team starts writing the smoke tests to ensure the readiness of the test infra. In this stage, the team runs the test cases as per the test plan defined in the previous steps. If some tests have failed, then the defects should get logged, and the report should go to the developer for further analysis. As per the books, every error or failure should have a corresponding defect. It helps in tracing back the test case or the bug later. As soon as the development team fixes it, the same test case should execute and report back to them. Such information is beneficial for future STLC cycles.An application can encounter either software errors or network errors. They would term it as product failure. Both of them represent an unexpected behavior of the software. But in some cases, errors are fixed values. The error discovered by a manual tester becomes a Defect. The defect which the dev team admits known as a Bug. If a build misses on the requirements, then it is a functional failure. It may have variations from company to company or even get customized for some projects as the software testing process drives it to not getting out of the way.
If the end-user sees an issue in the application, then such bugs lead to Defect leakage. And this process of finding bugs is also called as Bug Leakage. It usually is an indication of financial loss or cost to the environment or business reputation. It gets determined by dividing the defect count found with the size of the software or component. It indicates the effectiveness of a testing process by measuring the ratio of defects discovered before the release and reported after release by customers. It is an indicator of the efficiency of the development team to fix issues before the release. It is a clear indicator of the efficiency of the test cases getting executed in the test execution stage of the release. It helps in ensuring and measuring the quality of the test cases. Don’t club bugs that yield the same outcome. Prefer to group issues depending on what module they occur. 2. Collaborate with the dev team to discover new ways to categorize the problems. E.g., use the same static library for the components which counted for the most bugs. 3. Put more energy into locating the problem areas in the source code instead of doing a random search. 4. Re-order the test cases and pick the critical ones first to begin. 5. Pay attention to the end-user response and assess the risk areas around. This method got introduced by Thomas J. McCabe in the year 1976. It sees a program as a graph using the control flow representation. It reduces the human intervention to a great extent. We use different test automation tools like QTP, Selenium, and WinRunner. These tools help in speeding up the testing tasks. After completing the test execution, these tools also generate the test reports. In such cases, executing the regression tests is sufficient for validation. These provide some of the best technical questionnaires for Senior test engineers.
That’s why we came up with this blog post on the top manual testing interview questions for both the beginner and the experienced test engineers. Exploratory testing is a hands-on approach in which testers are involved in minimum planning and maximum test execution. The planning involves the creation of a test charter, a short declaration of the scope of a short (1 to 2 hour) time-boxed test effort, the objectives and possible approaches to be used. The test design and test execution activities are performed in parallel typically without formally documenting the test conditions, test cases or test scripts. This does not mean that other, more formal testing techniques will not be used. For example, the tester may decide to use boundary value analysis but will think through and test the most important boundary values without necessarily writing them down. The relationship between test cases and requirements is shown with the help of a document. This document is known as a traceability matrix. 5. What is Equivalence partitioning testing. Equivalence partitioning testing is a software testing technique which divides the application input test data into each partition at least once of equivalent data from which test cases can be derived. By this testing method, it reduces the time required for software testing. 6. What is white box testing and list the types of white box testing. White box testing technique involves selection of test cases based on an analysis of the internal structure (Code coverage, branches coverage, paths coverage, condition coverage, etc.) of a component or system. It is also known as Code-Based testing or Structural testing. Different types of white box testing are Statement Coverage Decision Coverage 7. In white box testing, what do you verify. In white box testing following steps are verified.
Verify the security holes in the code Verify the incomplete or broken paths in the code Verify the flow of structure according to the document specification Verify the expected outputs Verify all conditional loops in the code to check the complete functionality of the application Verify the line by line coding and cover 100 testing 8. What is black box testing. What are the different black box testing techniques. Black box testing is the software testing method which is used to test the software without knowing the internal structure of code or program. This testing is usually done to check the functionality of an application. The different black box testing techniques are Equivalence Partitioning Boundary value analysis Cause-effect graphing 9. What is the difference between static and dynamic testing. Static testing: During Static testing method, the code is not executed, and it is performed using the software documentation. Dynamic testing: To perform this testing the code is required to be in an executable form. 10. What are verification and validation. Verification is a process of evaluating software at the development phase. It helps you to decide whether the product of a given application satisfies the specified requirements. Validation is the process of evaluating software at the after the development process and to check whether it meets the customer requirements. 11. What are the different test levels. What is Integration testing. Integration testing is a level of software testing process, where individual units of an application are combined and tested. It is usually performed after unit and functional testing. 13. What Test Plans consists of. Test design, scope, test strategies, approach are various details that Test plan document consists of. What is the difference between UAT (User Acceptance Testing) and System testing.