Manual Testing

Testing any software or an application according to the client's needs without using any
automation tool is known as manual testing.

Classification of Manual Testing

 White Box Testing

 Black Box Testing
 Grey Box Testing
White Box Testing: In white-box testing, the developer will inspect every line of code before
handing it over to the testing team or the concerned test engineers.

White box testing is also known as open box testing, glass box testing, structural testing, clear
box testing, and transparent box testing.
Black Box Testing: In this testing, the test engineer will analyze the software against
requirements, identify the defects or bug, and sends it back to the development team.

White Box Testing Vs Black Box Testing Vs Gray Box Testing

Types of Black Box Testing
 Functional Testing
 Non-function Testing

Functional Testing: The test engineer will check all the components systematically against
requirement specifications is known as functional testing. Functional testing is also known as
Component testing. In functional testing, all the components are tested by giving the value,
defining the output, and validating the actual output with the expected value.

Types of Functional Testing

 Unit Testing
 Integration Testing
 System Testing

Unit Testing: Unit testing is a method of testing individual units or components of a software
application. It is typically done by developers and is used to ensure that the individual units of
the software are working as intended
Integration Testing: Integration testing is a method of testing how different units or
components of a software application interact with each other. It is used to identify and resolve
any issues that may arise when different units of the software are combined.

Different Ways of Performing Integration Testing:

 Top-down integration testing: It starts with the highest-level modules and differentiates
them from lower-level modules.

 Bottom-up integration testing: It starts with the lowest-level modules and integrates them
with higher-level modules.

 Big-Bang integration testing: It combines all the modules and integrates them all at once.

 Incremental integration testing: It integrates the modules in small groups, testing each
group as it is added.

System Testing: System Testing is carried out on the whole system in the context of either
system requirement specifications or functional requirement specifications or in the context of
both.

Types of Non-functional Testing

 Performance Testing
 Usability Testing
 Compatibility Testing

Performance Testing: In performance testing, the test engineer will test the working of an
application by applying some load.
Usability Testing: In usability testing, we will analyze the user-friendliness of an application
and detect the bugs in the software's end-user interface.

Compatibility Testing: In compatibility testing, we will check the functionality of an

application in specific hardware and software environments. Once the application is functionally
stable then only, we go for compatibility testing.

Automation Testing

The most significant part of Software testing is Automation testing. It uses specific tools to
automate manual design test cases without any human interference. Automation testing is the
best way to enhance the efficiency, productivity, and coverage of Software testing. In other
words, we can say that whenever we are testing an application by using some tools is known as
automation testing.

What are Verification and Validation?

Verification: The process of ensuring that software accomplishes its objectives without defects is
known as verification. It's the procedure for determining whether the product being developed is
correct or not. It determines whether the resulting product meets our specifications. It is mainly
focused on functionality.

Validation: Validation is the process of determining whether a software product meets the
required standards, or in other words, whether it meets the product's quality criteria. It is the
process of verifying product validation or ensuring that the product we are building is correct.
Validation focuses on the quality of the software

What are different SDLC models available?

 Waterfall model
 Spiral model
 Incremental model
 Agile Model
 Big bang model
 Iterative model

Waterfall Model
Which SDLC model is the best?

According to the annual State of Agile report, Agile is the best SDLC methodology and also one
of the most widely used SDLC in the IT industry. The reason is that it is a hybrid of incremental
and iterative approaches and works well in a flexible environment.
S.no. Purpose Agile model Waterfall model
Agile model follows the
incremental approach, where each
Waterfall model follows a sequential
1. Definition incremental part is developed
design process.
through iteration after every
timebox.
In the agile model, the measurement In the waterfall model, generally the
2. Progress of progress is in terms of developed measurement of success is in terms of
and delivered functionalities. completed and reviewed artifacts.
Agile model is flexible as there is a On the other hand, the waterfall model
possibility of changing the is rigid as it does not allow to modify
3. Nature
requirements even after starting the the requirements once the development
development process. process starts.
Customer interaction in waterfall
In Agile model, there is a high
model is very less. It is because, in a
Customer customer interaction. It is because,
4. waterfall model, the product is
interaction after every iteration, an incremental
delivered to the customer after overall
version is deployed to the customer.
development.
It has a small team size. As smaller
In the waterfall model, the team may
5. Team size is the team, the fewer people work
consist more members.
on it so that they can move faster.
 Agile model is not a suitable model Waterfall model works well in smaller
for small projects. The expenses of size projects where requirements are
6. Suitability developing the small projects using easily understandable. But waterfall
agile is more than compared to model is not suitable for developing
other models. the large projects.
The test plan is reviewed after each Test plan is reviewed after complete
7. Test plan
sprint. development.
Testing team can take part in the
It is difficult for the testing team to
8. Testing requirements change phase without
initiate any change in needs.
problems.

What are the drawbacks of the spiral model?

The spiral model is a hybrid of the iterative development process and the waterfall model, with a
focus on risk analysis. In the SDLC Spiral model, the development process begins with a limited
set of requirements and progresses through each development phase. Until the application is
ready for production, the software engineering team adds functionality for the increased
requirement in ever-increasing spirals.