Top Software Testing Interview Questions And Answers
Top Software Testing Interview Questions And Answers
Top Answers to Software Testing Interview Questions
- 1. Compare Software Testing Vs. Debugging
Criteria Software testing Debugging Process Known conditions, predefined methods and expected outcome Unknown conditions, not preset method and unpredictable outcome Prerequisite No need of design knowledge Need full design knowledge Goal Finding error or bug Finding a cause for the error or bug
- 2. Explain Monkey testing.
Monkey testing is a type of Black Box Testing used mostly at the Unit Level. In this testing, the tester enters data in any format and check the software is not crashing. This uses Smart monkey and dumb monkey.
Smart monkeys are used for load and stress testing; they will help in finding the bugs. They have high development cost.
Dumb monkey are important for basic testing. They help in finding those bugs that have high severity. Dumb monkey are less expensive as compared to Smart monkeys.
- 3. What is the difference between baseline and benchmark testing?
The difference between baseline and benchmark testing are:
– Baseline testing is the process of running a set of tests to capture performance information whereas Benchmarking is the process of comparing application performance with respect to industry standard that is given by some other organization.
– Baseline testing uses the information collected to make changes in the application so as to improve performance and capabilities of the application whereas benchmark testing gives information of our application with respect to other applications.
– Baseline compares present performance of application with its own previous performance whereas benchmark compares our application performance with other company’s application’s performance.
Learn Software Testing in 20 hrs. Download e-book nowCLICK HERE
- 4. Explain bug life cycle.
• When a tester finds a bug, the bug is assigned NEW or OPEN with status.
• The bug is assigned to Development Project Managers who will analyze the bug. They will check whether it is a valid defect. If not valid, the bug is rejected, and its new status is REJECTED.
• Now, the tester checks whether the similar defect was raised earlier. If yes, the defect is assigned a status ‘DUPLICATE’
• Once the bug is fixed, the defect is assigned a status ‘FIXED’
• Next the tester will re-test the code. In case, the test case passes, the defect is CLOSED
• If test case fails again, the bug is RE-OPENED and assigned to the developer.
- 5. How can we perform Spike testing in JMeter?
Spike Testing is performed to understand what changes happen on the application when there is a sudden increase in the number of users.
In JMeter, spike testing can be achieved using Synchronizing Timer. Synchronizing Timer will synchronize requests of multiple threads. It will add delays between requests such that all threads fire at the same time thus creating heavy load bursts on our application
- 6. Explain the concepts of Test Fusion Report of QTP.
Test Fusion report displays different aspects of the test run, soon after the tester runs a test. The Test Fusion report is used to display all the aspects of test run, it specifies where the application failures occurred, the test data used, and the detailed explanation of every checkpoint stating pass or failure and the application screen shots of every step by highlighting the discrepancies.
– Test Fusion Report is a compilation of the entire testing process. It includes an overview of where the failures occurred, the test data that was used in testing, screen shots to support inconsistencies and detailed view of checkpoints.
- 7. What is Silk Test?
Silk Test is a tool developed for performing regression and functionality testing of the application. Silk Test is a tool, used when we are testing the applications based on Windows, Java, Web or traditional client/server. Silk Test helps in preparing the test plan and managing of those test plans to provide direct access to the database and field validation.
- 8. What is Requirements Traceability Matrix?
Requirements Traceability Matrix (RTM) is a tool to make sure that the project requirements remain same throughout the whole development process. RTM is used in the development process because of following reasons:
– To determine whether the developed project meets the user requirements.
– To determine all the requirements given by the user.
– To make sure the application requirements can be fulfilled in the verification process.
- 9. What is elementary process?
Software applications are made up of several elementary processes. There are two types of elementary processes:
– Dynamic elementary Process: The dynamic elementary involves process of moving data from one location to another. The location can be either within the application or outside it.
– Static elementary Process: It involves maintaining the data of the application.
Download latest questions asked on Software Testing in top MNC's ?
- 10. What is the role of QA in project development?
– QA team is responsible for monitoring the development process.
– Responsibilities of QA team are – Planning, Testing and Process execution.
– QA Leads create time tables and agrees on a Quality Assurance plan for the product.
– The team communicates the QA process to the team members.
– The professionals ensure traceability of test cases to requirements.
- 11. What are the tools of performance testing?
Some popular commercial testing tools are:
• LoadRunner(HP): used for web and other applications. It provides a variety of application environments, platforms and database.
• QAload(Compuware): used for load testing of web, database and char-based system.
• WebLoad(RadView): it allows comparison of Running test with Test metrics.
• Rational Performance Tester (IBM): used to identify presence and cause of system performance bottlenecks.
• Silk Performer (Borland): allows prediction of behavior of e-business environment before it is deployed, regardless of size and complexity.