Interview question for Software tsting
These questions are collected after consulting with top industry experts in the field of Manual and Automation testing. If you want to brush up with the software testing basics, which I recommend you to do before going ahead with this Software Testing Interview Questions, take a look at this article on Software Testing Tutorial. If you are a tech-savvy who wants to up-skill yourself with all the latest technologies, take a look at this list of Top Trending Technologies.
1. Tell me about a situation in which you had to adjust to changes over which you had no control. How did you handle it?
In the automobile industry, you can expect changes to occur. Cars change as people change, so you can at least expect to see innovations in their products and the solutions they offer their customers. You may also expect changes in management and changes in policies that might affect how you do your job. Show the interviewer at Ford that you can adjust when changes happen. The interviewer is most interested in your response to the change, how you adapted and evolved yourself! Focus on your ability to stay confident and flexible in these situations.
2. What are the different methods of testing?
There are three methods of software testing and they are as follows:
1. Black-Box Testing
2. White-Box Testing
3. Grey-Box Testing
• Black-box testing: It is a testing strategy based solely on requirements and specifications. In this strategy, it requires no knowledge of internal paths, structures, or implementation of the software being tested.
• White box testing: It is a testing strategy based on internal paths, code structures, and implementation of the software being tested. White box testing generally requires detailed programming skills.
• Gray box testing: It is a strategy for software debugging in which the tester has limited knowledge of the internal details of the program.
3. Are you willing to work overtime, nights, weekends?
If you are interviewing for customer service or sales, chances are you will need to be open to working a variety of shifts. When you start a new job, you need to flexible about the schedule you’re willing to work. Don’t let this question catch you off guard! If you want to know more about what to expect from the employee agenda at Ford, now is the time to ask! Share that you are open, flexible and curious about what type of schedule you may have when you first get started. Answer truthfully and clearly.
4. What are the different levels of testing?
There are mainly four testing levels and they are:
Mock test to judge your Software Testing interview skills.
Take this mock test paper which will help you to prepare for a testing interview as well as the CSTE certification exam.
5. What is Verification and Validation in Software Testing?
Verification: It is a static analysis technique. Here, testing is done without executing the code. Examples include – Reviews, Inspection, and walkthrough.
Validation: It is a dynamic analysis technique where testing is done by executing the code. Examples include functional and non-functional testing techniques.
In the V model, the development and QA activities are done simultaneously. There is no discrete phase called Testing, rather testing starts right from the requirement phase. The verification and validation activities go hand in hand.
6. What is usability testing?
It is a testing methodology where the end customer is asked to use the software to see if the product is easy to use, to see the customer’s perception and task time. An accurate way to finalize the customer point of view for usability is by using prototype or mock-up software during the initial stages.
7. What is the difference between Performance Testing, Load Testing, and Stress Testing? Explain with examples?
Many people get confused with these testing terminologies for the detailed explanation of Performance, Load and Stress Testing types with examples for better understanding.
8. Explain the procedure for manual testing?
The manual testing process comprises the following steps:
• Planning and Control
• Analysis and Design
• Implementation and Execution
• Evaluating exit criteria and Reporting
• Test Closure activities
9. What is the test case?
A test case is a document which has a set of conditions or actions that are performed on the software application in order to verify the expected functionality of the feature.
Test cases describe a specific idea that is to be tested, without detailing the exact steps to be taken or data to be used. For example, in a test case, you document something like ‘Test if coupons can be applied on actual price‘.
10. What is API testing?
API testing is a type of software testing where application programming interfaces (APIs) are tested to determine if they meet expectations for functionality, reliability, performance, and security. In simple terms, API testing is intended to reveal bugs, inconsistencies or deviations from the expected behavior of an API
11. How to create and run testng.xml?
In TestNG framework, we need to create testng.xml file to create and handle multiple test classes. We do configure our test run, set test dependency, include or exclude any test, method, class or package and set priority etc in the xml file.
12. How to pass parameter through testng.xml file to a test case?
We could define the parameters in the testng.xml file and then reference those parameters in the source files.
Create a java test class, say, ParameterizedTest.java and add a test method say parameterizedTest() to the test class. This method takes a string as input parameter. Add the annotation @Parameters(“browser”) to this method
13. What makes a good test engineer?
A software test engineer is a professional who determines how to create a process that would best test a particular product in the software industry.
• A good test engineer should have a ‘test to break’ attitude, an ability to take the point of view of the customer
• Strong desire for quality and attention to minute details
• Tact and diplomacy to maintain a cooperative relationship with developers
• Ability to communicate with both technical (developers) and non-technical (customers, management) people
• Prior experience in the software development industry is always a plus
• Ability to judge the situations and make important decisions to test high-risk areas of an application when time is limited.