Important Question on Manual Testing
Before going for the question and answer we will understand what the interviewer will be expecting from you. I have listed some points that you should on what question. So let’s see the points one by one
The interview starts with very common and compulsory questions which is
1. Tell me about yourself?
- To this question what is the point to be kept in front of the interviewer?
- You have to mention the projects that you have worked on.
- You have to mention certification if you went through it.
- You have to mention your skills and the technology you know.
- If you have done any internships you should mention
- Recent tools or technology that you upgraded got certification.
- At the end, you can tell about your family but it’s optional.
2. Why do you want to make your career in software testing?
- When you get this type of question in an interview you should not tell these listed points
- Should not tell about the gaps
- Should not tell about your problems because of which you are moving to test
- Instead, you should show curiosity and passion for software testing
- Which software is being launched to use them to understand them
- Should not mention your gaps, covid, or any govt exams.
So from here, we will start with the Important Question on Manual Testing that may ask in the interview.
- What do you know about STLC(Software Testing life cycle)?
- Software Testing Life Cycle (STLC) is a process used to test software and ensure that quality standards are met. Tests are carried out systematically over several phases. During product development, phases of the STLC may be performed multiple times until a product is deemed suitable for release. Need to explain each and every phase in detail.
3. If an application is given to you and you don’t have any test case and scenario with to do the testing then what will be your approach or strategy to test the application
- To this question, you should tell that your approach will be exploratory testing.
Exploratory is a type of software testing where there is no test case created for the application and you are totally new to the application that time you explore the application with that you do the testing also will be checking the functionality in ad-hoc manner and do documentation at high level.
Note: Are you tired of software that crashes or doesn’t work as expected? Do you want to deliver high-quality software products that meet the needs of your customers? Look no further than software testing Classes in Pune
4. If an application is given to you with 1000 test cases and you have only 2 days to sign off then what will be your approach of testing the application?
- Testing the important functionality from a business point of view if you have time you can go for testing for further functionality or else as you have only 2 days you can provide sign-off once you complete testing important functionality.
- If high-level testing is to be done on Gmail then what is the high-level scenario?
- Login page, forgot password, register, compose, inbox, sent item, trash, spam, etc are the high-level scenario to be tested in Gmail.
5. What are the principles of software testing?
- Software testing is governed by seven principles:
- Absence of errors fallacy: Even if the software is 99% bug-free, it is unusable if it does not conform to the user’s requirements. Software needs to be bug-free 99% of the time, and it must also meet all customer requirements.
- Testing shows the presence of errors: Testing can verify the presence of defects in software, but it cannot guarantee that the software is defect-free. Testing can minimize the number of defects, but it can’t remove them all.
- Exhaustive testing is not possible: The software cannot be tested exhaustively, which means all possible test cases cannot be covered. Testing can only be done with a select few test cases, and it’s assumed that the software will produce the right output in all cases. Taking the software through every test case will cost more, take more effort, etc., which makes it impractical.
- Defect clustering: The majority of defects are typically found in a small number of modules in a project. According to the Pareto Principle, 80% of software defects arise from 20% of modules.
- Pesticide Paradox: It is impossible to find new bugs by re-running the same test cases over and over again. Thus, updating or adding new test cases is necessary in order to find new bugs.
- Early testing: Early testing is crucial to finding the defect in the software. In the early stages of SDLC, defects will be detected more easily and at a lower cost. Software testing should start at the initial phase of software development, which is the requirement analysis phase.
- Testing is context-dependent: The testing approach varies depending on the software development context. Software needs to be tested differently depending on its type. For instance, an ed-tech site is tested differently than an Android app.
6. What is system testing?
- System testing is a level of testing that will validate the fully integrated software product is working fine or not so you can say when you are doing system testing so you are testing end to end system is application is working as per specification or not right
For Free, Demo classes Call: 020-71177008
Registration Link: Click Here!
7. Explain black-box testing, white-box testing, and grey-box testing.
Black-box testing in software testing: In black-box testing, the system is tested only in terms of its external behaviour; it does not consider how the software functions on the inside. This is the only limitation of the black-box test. It is used in Acceptance Testing and System Testing.
White-box testing in software testing: A white-box test is a method of testing a program that takes into account its internal workings as part of its review. It is used in integration testing and unit testing.
Grey-box testing in software testing: A Gray Box Testing technique can be characterized as a combination of a black box as well as a white box testing technique used in the software testing process. Using this technique, you can test a software product or application with a partial understanding of its internal structure.
8. Explain boundary value analysis in software testing.
- BVA (Boundary Value Analysis) is a black box software testing technique that uses boundary values to create test cases. Input values near the boundary have a higher probability of error, so BVA is used to test boundary values. BVA includes values at the boundaries in the test cases. If the input falls within the boundary range, then the test is positive; if it falls outside, then it is negative. There are several types of values, including maximum or minimum, inside or outside edge, and typical or error values.
9. What is the V model in software testing?
- V-models, also known as validation or verification models, are SDLC models where the process occurs sequentially in a V-shape. This method consists of associating a testing phase with each corresponding development stage. As each development activity is accompanied by a testing activity, the next test phase occurs only after the previous phase has been completed.
- Validation: It is defined as a process that involves dynamic testing of software products by executing the code. This process validates whether we are building the right software that meets that customer’s requirement or not. It involves various activities like system testing, integration testing, user acceptance testing, and unit testing.
- Verification: The technique involves static analysis (review) without running the code. It is defined as a process that involves analyzing documents. This process verifies whether the software conforms to specifications or not. Its ultimate goal is to ensure the quality of software products, design, architecture, etc.
Note: whether you’re looking to enhance your career prospects or want to stay ahead of the curve in today’s competitive software industry, our Software Testing Training in Pune is the perfect solution.
Call the Trainer and Book your free demo Class For Software Testing Call now!!!
| SevenMentor Pvt Ltd.
© Copyright 2021 | SevenMentor Pvt Ltd.