Software Testing Interview Questions For Experienced
Software Testing Interview Questions For Experienced
We can run more tests to make sure that the problem has a clear description.
We can also run a few more tests to ensure that the same problem doesn’t exist
with different inputs.
Once we are certain of the full scope of the bug, we can add details and report it.
How will you overcome the challenges faced due to the unavailability of
proper documentation for testing?
If the standard documents like System Requirement Specification or Feature
Description Document are not available, then QAs may have to rely on the following
references, if available.
Screenshots
A previous version of the application
Wireframes
Another reliable way is to have discussions with the developer and the business
analyst. It helps in solving the doubts, and it opens a channel for bringing clarity on the
requirements. Also, the emails exchanged could be useful as a testing reference.
Smoke testing is yet another option that would help verify the main functionality of the
application. It would reveal some very basic bugs in the application. If none of these
work, then we can just test the application from our previous experiences.
Unit testing
Smoke testing
UAT
Sanity testing
Interface testing
Integration testing
System testing
Regression testing
What are functional test cases and non-functional test cases?
1. Requirement Analysis
2. Test Planning
3. Test Case Development
4. Environment Setup
5. Test Execution
6. Test Cycle Closure
In software testing, what does a fault mean?
Fault is a condition that makes the software fail to execute while performing the
considered function.
Priority: It specifies which bug should get fixed first. It defines the user’s point of view.
It gets measured as the ratio of defects fixed to total the number of issues discovered.
The day of birth of a defect is the day it got assigned and accepted by the
development team.
The issues which got dropped are out of the scope.
Age can be both in hours or days.
The end time is the day the defect got verified and closed, not just the day it got
fixed by the development team.
Quality Control (QC) is relevant to the quality of the product. QC not only finds the
defects but suggests improvements too. Thus, a process that is set by QA is
implemented by QC. QC is the responsibility of the testing team.
Software testing is the process of ensuring that the product which is developed by
developers meets the users’ requirements. The aim of performing testing is to find bugs
and make sure that they get fixed. Thus, it helps to maintain the quality of the product to
be delivered to the customer.
A unique ID
Defect description: A short description of the bug
Steps to reproduce: They include the detailed test steps to emulate the issue.
They also provide the test data and the time when the error has occurred
Environment: Add any system settings that could help in reproducing the issue
Module/section of the application in which the error has occurred
Severity
Screenshots
Responsible QA: This person is a point of contact in case you want to follow-up
regarding this issue
Bug release: A bug release is when a particular version of the software is released with
a set of known bug(s). These bugs are usually of low severity/priority. It is done when a
software company can afford the existence of bugs in the released software but not the
time/cost for fixing it in that particular version.
What is the difference between performance testing and monkey
testing?
Performance testing checks the speed, scalability, and/or stability characteristics of a
system. Performance is identified with achieving response time, throughput, and
resource-utilization levels that meet the performance objectives for a project or a
product.
Monkey testing is a technique in software testing where the user tests the application by
providing random inputs, checking the behavior of the application (or trying to crash the
application).