1. What
is black box testing and white box testing ?
Black Box Testing: It is testing of the
application or product in which we do not test the back end, internal structure
or the code.
White Box Testing: It is a testing of the
application or product in which we test the back end, internal structure or the
code.
2. What
is Software Testing Lifecycle ?
The software testing lifecycle is the steps
from the beginning to the end of the testing. It involves below steps:
Gathering Requirements and Analysis
Creating Test Plans
Create Test cases
Set up, and configure test environment
Test execution
Close the test cycle
3. What
is a test case ?
A test case is a testing artifact that has
the testing steps, testing data, preconditions, status(pass/fail), actual
result, expected result etc. The test case shows whether the functionality being tested satisfied the software
requirement or not.
4. What
is a test plan?
A test plan is a document that has a detail
picture of the testing activities to be included in the testing. It has the
objectives, schedule, scope, dependencies, entry/exit criteria, pass/fail
criteria, resources, and other information related to the testing to be carried
out to deliver a quality product.
5. What
is non-functional testing ?
The testing which does not include testing
of functionality is non-functional testing. Such as performance testing, load
testing, security testing, usability testing etc. Similarly, the testing of
documents, requirements, environment, network, user access, etc also fall under
non-functional testing.
6. What
is load testing ?
It
is a testing to find out the product or
software’s threshold point or limitation. In this, the load is increased
to test
how much load a software or product can handle or manage before it
breaks. In a practical situation, a number of virtual users are created
and access the
application concurrently by the users. This test determines whether the
application remains stable or not under actual load conditions.
7. What
is stress testing ?
It is a testing to find out how the
application or software behaves when the load is increased up to the breaking
point, or the load crosses the threshold. This testing is done to check the application
response in abnormal conditions. We check
if the system reaches the breaking point, does it show the right error message,
does it recover after it fails.
8. What
is regression testing ?
A regression testing is a testing of a
product or software after a new fix or change has been added to the
product. After a fix or change has been
added, then we have to test the new functionality which was fixed or changed, or
newly added. Regression testing comes into the picture after we do the testing of
the new functionality. We test the overall product to test if the remaining
functionality is working fine or not, if the new functionality has impacted
other existing functionality or not. To check if there are any new bugs because
of the change.
9. What
is verification and validation ?
Verification: It determines if the software
or product meets the business requirement or specifications.
Validation: It determines if the software
or product meets the client’s expectations.
10. What is the difference between Verification and Validation ?
Verification is the process of determining if the product meets the business requirements or specifications.
We test the design, codes, data, front end, back end.
Done while the product is under development.
Involves low level testing such as reviews, inspections, analysis.
Finds bugs early
Verification is done before Validation
Tested by software testers, QAs
Validation is the process of determining if the product meets client’s expectation or need.
We validate the actual product.
Done after the product is developed.
Involves high level testing such as Performance/Load/Stress Testing, black box testing, white box testing, grey box testing
Finds bugs missed by verification.
Validation is done after Verification.
Tested by client/customer/UAT.