Functional testing Usability testing

 Ensure that the product behaves  Focuses on customer acceptance

according to the functional
requirements and does not take into
consideration design principles.
 A series of tests which perform a
feature by feature validation of
behaviour, using a wide range of
normal and erroneous input data.
and how well the customer can use
the product to complete the required
task.
 Investigates all aspects of the
usability of a product, including
overall structure, navigation flow,
layout of elements on a page, clarity
of content and overall behaviour.

Functionality Integration Compatibility

Unit Testing
Testing Testing Testing

Functionality testing Unit Testing Integration Testing Compatibility Testing

refers to the testing of Functionality testing When the various Testing the courseware
programmatic should start at the modules are combined on the various kinds of
features and is most source, namely by the and the features are all user hardware and
appropriate for sites programmers who running together, it is software
of higher complexity write the code. When said to be integrated, configurations is called
that contain features programmers test and testing of the full compatibility testing.
such as database their own code, program is called If the courseware has
access, dynamic page module by module, it integration testing. multimedia and/or
generation, and other is referred to as unit interactive elements, it
dynamic/interactive testing. Although all of the should go through
elements - namely modules may seem to compatibility testing.
features that require Each programmer tests work perfectly in With the various
actual programming his or her own isolation, they often versions of
(rather than just a modules thoroughly exhibit defects when audio/video/animation
static screen). and does not start a combined as a system. codec or driver, that
new module before have been released, it
testing and fixing the Reasons include is possible that
previous one. unexpected inputs and features that work fine
outputs between on one machine may
The programmer tests modules, incompatible stall or malfunction on
not simply by running variables, and just another. Problems
the code a few times about anything else reveal themselves in
to see if it works, but that can go wrong. such situations that
rather by feeding the might never be
code common, discovered otherwise.
uncommon, and even
unexpected inputs to
make sure it handles
them correctly and
does not malfunction.
 Functional testing can be defined as testing the individual functionality of modules.
 It refers to testing the software product at an individual level, to check its
functionality.
 It is very different from unit or integration testing; you cannot write innumerable test
cases for functional testing, since it is more complex than unit testing.
 Functional testing tools strive to test the functionality of the software. Then, test
cases are developed to check the software for expected and unexpected results.
 This type of testing is carried out more from a user perspective. That is to say, it
considers the expectation of the user for a type of input.
 Selenium is one of the most common tools used for functional testing.

Integration testing can be classified as a testing level, while functional testing can be
considered a testing type.

 For any system or software product to work efficiently, every component has to be in sync
with each other. Integration testing tools strive to connect and integrate the different parts
of the software to coexist and work without errors.

 The tools used for integration testing are the same as those used for unit testing, though it
takes a while for the test database to get configured.

 It is used in complex situations, when unit testing proves to be insufficient to test the
system.
Usability is a quality attribute that assesses how easy user interfaces are to use. The word "usability"
also refers to methods for improving ease-of-use during the design process.

Usability is defined by 5 quality components:

 Learnability: How easy is it for users to accomplish basic tasks the first time they encounter
the design?
 Efficiency: Once users have learned the design, how quickly can they perform tasks?
 Memorability: When users return to the design after a period of not using it, how easily can
they reestablish proficiency?
 Errors: How many errors do users make, how severe are these errors, and how easily can
they recover from the errors?
 Satisfaction: How pleasant is it to use the design?

There are many other important quality attributes. A key one is utility, which refers to the design's
functionality: Does it do what users need? Usability and utility are equally important: It matters little
that something is easy if it's not what you want. It's also no good if the system can hypothetically do
what you want, but you can't make it happen because the user interface is too difficult. To study a
design's utility, you can use the same user research methods that improve usability.