1) What is the PDCA cycle and where testing fits in?

There are four steps in a normal software development process. In short,

these steps are referred to as PDCA.

PDCA stands for Plan, Do, Check, Act.

o Plan: It defines the goal and the plan for achieving that goal.

o Do/ Execute: It depends on the plan strategy decided during the

planning stage. It is done according to this phase.

o Check: This is the testing part of the software development phase. It

is used to ensure that we are moving according to plan and getting the
desired result.

o Act: This step is used to solve if there any issue has occurred during
the check cycle. It takes appropriate action accordingly and revises the
plan again.

The developers do the "planning and building" of the project while testers do
the "check" part of the project.
2) What is the difference between the white box, black
box, and gray box testing?
Black box Testing: The strategy of black box testing is based on
requirements and specification. It requires no need of knowledge of internal
path, structure or implementation of the software being tested.

White box Testing: White box testing is based on internal paths, code
structure, and implementation of the software being tested. It requires a full
and detail programming skill.

Gray box Testing: This is another type of testing in which we look into the
box which is being tested, It is done only to understand how it has been
implemented. After that, we close the box and use the black box testing.

3)What are the advantages of designing tests early in the

life cycle?
Designing tests early in the life cycle prevent defects from being in the main
code.

4) What are the types of defects?

There are three types of defects: Wrong, missing, and extra.

Wrong: These defects are occurred due to requirements have been

implemented incorrectly.

Missing: It is used to specify the missing things, i.e., a specification was not
implemented, or the requirement of the customer was not appropriately
noted.

Extra: This is an extra facility incorporated into the product that was not
given by the end customer. It is always a variance from the specification but
may be an attribute that was desired by the customer. However, it is
considered as a defect because of the variance from the user requirements.

5) What is exploratory testing?

Simultaneous test design and execution against an application is called
exploratory testing. In this testing, the tester uses his domain knowledge
and testing experience to predict where and under what conditions the
system might behave unexpectedly.
6) When should exploratory testing be performed?
Exploratory testing is performed as a final check before the software is
released. It is a complementary activity to automated regression testing.

7) What are the advantages of designing tests early in the

life cycle?
It helps you to prevent defects in the code.

8) Tell me about the risk-based testing.

The risk-based testing is a testing strategy that is based on prioritizing tests
by risks. It is based on a detailed risk analysis approach which categorizes
the risks by their priority. Highest priority risks are resolved first.

9) What is acceptance testing?

Acceptance testing is done to enable a user/customer to determine whether
to accept a software product. It also validates whether the software follows a
set of agreed acceptance criteria. In this level, the system is tested for the
user acceptability.

Types of acceptance testing are:

1. User acceptance testing: It is also known as end-user testing. This

type of testing is performed after the product is tested by the testers.
The user acceptance testing is testing performed concerning the user
needs, requirements, and business processes to determine whether
the system satisfies the acceptance criteria or not.

2. Operational acceptance testing: An operational acceptance testing

is performed before the product is released in the market. But, it is
performed after the user acceptance testing.

3. Contract and regulation acceptance testing: In the case of

contract acceptance testing, the system is tested against certain
 criteria and the criteria are made in a contract. In the case of
regulation acceptance testing, the software application is checked
whether it meets the government regulations or not.

4. Alpha and beta testing: Alpha testing is performed in the

development environment before it is released to the customer. Input
is taken from the alpha testers, and then the developer fixes the bug
to improve the quality of a product. Unlike alpha testing, beta testing
is performed in the customer environment. Customer performs the
testing and provides the feedback, which is then implemented to
improve the quality of a product.

10) What is accessibility testing?

Accessibility testing is used to verify whether a software product is accessible
to the people having disabilities (deaf, blind, mentally disabled etc.).

11) What is Adhoc testing?

Ad-hoc testing is a testing phase where the tester tries to 'break' the system
by randomly trying the system's functionality.

12) What is Agile testing?

Agile testing is a testing practice that uses agile methodologies i.e. follow
test-first design paradigm.

13) What is API (Application Programming Interface)?

Application Programming Interface is a formalized set of software calls and
routines that can be referenced by an application program to access
supporting system or network services.

14) What do you mean by automated testing?

Testing by using software tools which execute test without manual
intervention is known as automated testing. Automated testing can be used
in GUI, performance, API, etc.

15) What is Bottom-up testing?

The Bottom-up testing is a testing approach which follows integration testing
where the lowest level components are tested first, after that the higher level
components are tested. The process is repeated until the testing of the top-
level component.

16) What is Baseline Testing?

In Baseline testing, a set of tests is run to capture performance information.
Baseline testing improves the performance and capabilities of the application
by using the information collected and make the changes in the application.
Baseline compares the present performance of the application with its
previous performance.

17) What is Benchmark Testing?

Benchmarking testing is the process of comparing application performance
with respect to the industry standard given by some other organization.

It is a standard testing which specifies where our application stands with

respect to others.

18) Which types are testing are important for web testing?
There are two types of testing which are very important for web testing:

o Performance testing: Performance testing is a testing technique in

which quality attributes of a system are measured such as
responsiveness, speed under different load conditions and scalability.
The performance testing describes which attributes need to be
improved before the product is released in the market.
 o Security testing: Security testing is a testing technique which
determines that the data and resources be saved from the intruders.

19) What is the difference between web application and

desktop application in the scenario of testing?
The difference between a web application and desktop application is that a
web application is open to the world with potentially many users accessing
the application simultaneously at various times, so load testing and stress
testing are important. Web applications are also prone to all forms of attacks,
mostly DDOS, so security testing is also very important in the case of web
applications.

20) What is the difference between verification and

validation?
Difference between verification and validation:

Verification Validation

Verification is Static Testing. Validation is Dynamic

Testing.

Verification occurs before Validation. Validation occurs after

Verification.

Verification evaluates plans, document, Validation evaluates

requirements and specification. products.

In verification, inputs are the checklist, Invalidation testing, the

issues list, walkthroughs, and actual product is tested.
inspection.

Verification output is a set of Invalidation actual

document, plans, specification and product is output.
requirement documents.
Regression Retesting

21) What is the difference between Retesting and

Regression Testing?
A list of differences between Retesting and Regression Testing:
 Regression is a type of software Retesting is the process of
testing that checks the code change testing that checks the test
does not affect the current features cases which were failed in the
and functions of an application. final execution.

The main purpose of regression Retesting is applied on the

testing is that the changes made to defect fixes.
the code should not affect the existing
functionalities.

Defect verification is not an element of Defect verification is an

Regression testing. element of regression testing.

Automation can be performed for Automation cannot be

regression testing while manual performed for Retesting.
testing could be expensive and time-
consuming.

Regression testing is also known as Retesting is also known as

generic testing. planned testing.

Regression testing concern with Regression testing can be

executing test cases that was passed performed in parallel with the
in earlier builds. Retesting concern retesting. Priority of retesting
with executing those test cases that is higher than the regression
are failed earlier. testing.

22) What is the difference between preventative and

reactive approaches to testing?
Preventative tests are designed earlier, and reactive tests are designed after
the software has been produced.

23) What is the purpose of exit criteria?

The exit criteria are used to define the completion of the test level.

24) Why is the decision table testing used?

A decision table consists of inputs in a column with the outputs in the same
column but below the inputs.

The decision table testing is used for testing systems for which the
specification takes the form of rules or cause-effect combination. The
reminders you get in the table explore combinations of inputs to define the
output produced.

25) What is alpha and beta testing?

These are the key differences between alpha and beta testing:

No. Alpha Testing Beta Testing

1) It is always done by developers at the It is always performed by

software development site. customers at their site.

2) It is also performed by Independent It is not be performed by

testing team Independent testing team

3) It is not open to the market and It is open to the market and

public. public.

4) It is always performed in a virtual It is always performed in a

environment. real-time environment.

5) It is used for software applications It is used for software

and projects. products.

6) It follows the category of both white It is only the kind of Black

box testing and Black Box Testing. Box Testing.
 7) It is not known by any other name. It is also known as field
testing.

26) What is Random/Monkey Testing?

Random testing is also known as monkey testing. In this testing, data is
generated randomly often using a tool. The data is generated either using a
tool or some automated mechanism.

Random testing has some limitations:

o Most of the random tests are redundant and unrealistic.

o It needs more time to analyze results.

o It is not possible to recreate the test if you do not record what data
was used for testing.

27) What is the negative and positive testing?

Negative Testing: When you put an invalid input and receive errors is
known as negative testing.

Positive Testing: When you put in the valid input and expect some actions
that are completed according to the specification is known as positive testing.

28) What is the benefit of test independence?

Test independence is very useful because it avoids author bias in defining
effective tests.

29) What is the boundary value analysis/testing?

In boundary value analysis/testing, we only test the exact boundaries rather
than hitting in the middle. For example: If there is a bank application where
you can withdraw a maximum of 25000 and a minimum of 100. So in
boundary value testing we only test above the max and below the max. This
covers all scenarios.
The following figure shows the boundary value testing for the above-
discussed bank application.TC1 and TC2 are sufficient to test all conditions
for the bank. TC3 and TC4 are duplicate/redundant test cases which do not
add any value to the testing. So by applying proper boundary value
fundamentals, we can avoid duplicate test cases, which do not add value to
the testing.

30) How would you test the login feature of a web

application?
There are many ways to test the login feature of a web application:

o Sign in with valid login, Close browser and reopen and see whether
you are still logged in or not.

o Sign in, then log out and then go back to the login page to see if you
are truly logged out.

o Log in, then go back to the same page, do you see the login screen
again?

o Session management is important. You must focus on how do we keep

track of logged in users, is it via cookies or web sessions?

o Sign in from one browser, open another browser to see if you need to
sign in again?

o Log in, change the password, and then log out, then see if you can log
in again with the old password.