Day 2

 Types of Manual Testing

 How to perform Manual Testing?

 Automation Testing

 What is Functional Testing?

 Unit Testing

 Integration Testing

 System Testing

 Acceptance Testing

 Regression Testing

 When can we perform Regression Testing?

 What is Positive Testing?

 What is Negative Testing?

Manual testing can be further divided into three types of testing,

which are as follows:

o White box testing

o Black box testing
o Gray box testing

White-box testing
The white box testing is done by Developer, where they check every line of a code
before giving it to the Test Engineer. Since the code is visible for the Developer
during the testing, that's why it is also known as White box testing.
Black box testing
The black box testing is done by the Test Engineer, where they can check the
functionality of an application or the software according to the customer /client's
needs. In this, the code is not visible while performing the testing; that's why it is
known as black-box testing.

Gray Box testing

Gray box testing is a combination of white box and Black box testing. It can be
performed by a person who knew both coding and testing. And if the single person
performs white box, as well as black box testing for the application, is known as Gray
box testing.

How to perform Manual Testing

o First, tester observes all documents related to software, to select testing areas.
o Tester analyses requirement documents to cover all requirements stated by the
customer.
o Tester develops the test cases according to the requirement document.
o All test cases are executed manually by using Black box testing and white box testing.
o If bugs occurred, then the testing team informs the development team.
o The Development team fixes bugs and handed software to the testing team for a
retest.

Automation testing
Automation testing is a process of converting any manual test cases into the test
scripts with the help of automation tools, or any programming language is known as
automation testing. With the help of automation testing, we can enhance the speed
of our test execution because here, we do not require any human efforts. We need to
write a test script and execute those scripts.
What is Functional Testing?
FUNCTIONAL TESTING is a type of software testing that validates the software
system against the functional requirements/specifications. The purpose of
Functional tests is to test each function of the software application, by providing
appropriate input, verifying the output against the Functional requirements.
Functional testing mainly involves black box testing, and it is not concerned
about the source code of the application. This testing checks User Interface,
APIs, Database, Security, Client/Server communication and other functionality
of the Application Under Test. The testing can be done either manually or using
automation.

What do you test in Functional Testing?

The prime objective of Functional testing is checking the functionalities of the
software system. It mainly concentrates on –

 Mainline functions: Testing the main functions of an application

 Basic Usability: It involves basic usability testing of the system. It checks
whether a user can freely navigate through the screens without any
difficulties.
 Accessibility: Checks the accessibility of the system for the user
 Error Conditions: Usage of testing techniques to check for error
conditions. It checks whether suitable error messages are displayed.

How to do Functional Testing

Following is a step by step process on How to do Functional Testing :

 Understand the Functional Requirements

 Identify test input or test data based on requirements
 Compute the expected outcomes with selected test input values
 Execute test cases
 Compare actual and computed expected results

Unit Testing
Unit testing involves the testing of each unit or an individual component of the
software application. It is the first level of functional testing. The aim behind unit
testing is to validate unit components with its performance.

A unit is a single testable part of a software system and tested during the
development phase of the application software.

The purpose of unit testing is to test the correctness of isolated code. A unit
component is an individual function or code of the application. White box testing
approach used for unit testing and usually done by the developers.
Whenever the application is ready and given to the Test engineer, he/she will start
checking every component of the module or module of the application
independently or one by one, and this process is known as Unit
testing or components testing.

Integration testing
Integration testing is the second level of the software testing process comes after
unit testing. In this testing, units or individual components of the software are tested
in a group. The focus of the integration testing level is to expose defects at the time
of interaction between integrated components or units.

Unit testing
uses modules for testing purpose, and these modules are combined and tested in
integration testing. The Software is developed with a number of software modules
that are coded by different coders or programmers. The goal of integration testing is
to check the correctness of communication among all the modules.
Once all the components or modules are working independently, then we need to
check the data flow between the dependent modules is known as integration
testing.

System Testing
System Testing includes testing of a fully integrated software system. Generally, a
computer system is made with the integration of software (any software is only a
single element of a computer system). The software is developed in units and then
interfaced with other software and hardware to create a complete computer system.
In other words, a computer system consists of a group of software to perform the
various tasks, but only software cannot perform the task; for that software must be
interfaced with compatible hardware. System testing is a series of different type of
tests with the purpose to exercise and examine the full working of an integrated
software computer system against requirements.

To check the end-to-end flow of an application or the software as a user is known

as System testing. In this, we navigate (go through) all the necessary modules of an
application and check if the end features or the end business works fine, and test the
product as a whole system.
It is end-to-end testing where the testing environment is similar to the production
environment.

Acceptance testing
Acceptance testing is formal testing based on user requirements and function
processing. It determines whether the software is conforming specified requirements
and user requirements or not. It is conducted as a kind of Black Box testing where
the number of required users involved testing the acceptance level of the system. It is
the fourth and last level of software testing.
User acceptance testing (UAT) is a type of testing, which is done by the customer
before accepting the final product. Generally, UAT is done by the customer (domain
expert) for their satisfaction, and check whether the application is working according
to given business scenarios, real-time scenarios.

In this, we concentrate only on those features and scenarios which are regularly used
by the customer or mostly user scenarios for the business or those scenarios which
are used daily by the end-user or the customer.

However, the software has passed through three testing levels (Unit Testing,
Integration Testing, System Testing) But still there are some minor errors which can
be identified when the system is used by the end user in the actual scenario.

What is regression testing?

Regression testing is a black box testing technique. It is used to authenticate a code
change in the software does not impact the existing functionality of the product.
Regression testing is making sure that the product works fine with new functionality,
bug fixes, or any change in the existing feature.

Regression testing can be performed on a new build when there is a significant

change in the original functionality. It ensures that the code still works even when the
changes are occurring. Regression means Re-test those parts of the application,
which are unchanged.

When can we perform Regression Testing?

We do regression testing whenever the production code is modified.

We can perform regression testing in the following scenario, these are:

 When new functionality added to the application.

Example:
A website has a login functionality which allows users to log in only with email. Now
providing a new feature to do login using Facebook.

What is Positive Testing?

It is used to check whether our application works as expected or not. And if an error
is detected at the time of positive testing, the test is considered as fail. A positive
testing is a technique whenever a test engineer writes the test cases for a set of
respective outputs.

In positive testing, the test engineer will always check for only a good set of values.

In other words, we can say that positive testing is a process where the system or an
application is tested against the valid input data.

And the primary purpose of performing the positive testing is to validate whether the
software does what it is supposed to do.

In simple terms, we can say that positive testing is implemented by providing

a positive point of view.

For example, Numbers like 9999999.

Example of Positive Testing

In the following example, we are trying to understand the working of positive testing.

o Suppose, we have one test scenario, where we want to test an application that
includes a simple text box.
 o To enter Phone Number according to the business needs it accepts only numerical
values.
o Hence, in positive testing, we will only give the positive numerical values in order to
test whether it is working as per the requirement or not.

What is Negative Testing?

It is implemented to check how the application can gracefully handle invalid input or
unpredicted user performance.

The fundamental purpose of executing the negative testing is to ensure the

application's stability against the effects of different variations of improper validation
data set.

Negative testing is also known as error path testing or failure. And it helps us to
identify more bugs and enhance the quality of the software application under test.

Once the positive testing is complete, then only we can execute the negative testing,
which helps to identify more bugs and enhance the quality of the software
application under test.

We can say that the negative testing is executing by keeping the negative point of
view in simple terms. For example, 99999abcde

Example of Negative Testing?

Let see one example which will help us to understand the negative testing in an
effective way.
 o Suppose we have one sample form where the Mobile Number field can only accept
the numbers' value and does not accept the unique characters and alphabets values.
o However, let's entered the unique characters and alphabets values on the Mobile
number field to test that it accepts the individual characters and alphabets values or
not.
o We expect that the textbox field will not accept invalid values and show an error
message for the incorrect entry.

Reference Links
https://www.javatpoint.com/software-testing-tutorial

https://www.javatpoint.com/manual-testing

https://www.javatpoint.com/acceptance-testing

https://www.javatpoint.com/system-testing

https://www.javatpoint.com/unit-testing

https://www.javatpoint.com/integration-testing

https://www.javatpoint.com/regression-testing

https://www.guru99.com/functional-testing.html

https://www.javatpoint.com/positive-testing-vs-negative-testing