A

Micro project report On

“Different Testing Tools”

SUBMITTED TO M.S.B.T.E., Mumbai

For the Award of

DIPLOMA IN COMPUTER ENGINEERING BY

Roll no Name of Student Enrollment no

08 Sanskar Shashikant Dongare 2212140102

UNDER THE GUIDANCE OF

Ms.Sarade R.
DEPARTMENT OF COMPUTER ENGINEERING

SVP’s Swami Vivekanand Institute of Technology(Poly),Solapur

Khed Solapur-413255
Evolution sheet for Micro Project

Academic Year:- 2023-24 Name of Faculty:- MS .Waghamare P.U

Course:- Computer Engineering Course code:- CO5I
Subject:- Operating System Subject Code:- 22414
Semester:- 5th Scheme:- I

Title of Project:- “ Different Testing Tools”

COs addressed by the Micro Project:

CO 1
CO 2

Comments/Suggestions about team work/leadership/inter-personal communication (if any)

Marks out of 6 Marks out of 4 Total

for for performance mars
Roll No Name of students performance in in oral/ out of
group activity Presentation 10

08 Rohit Pramod Gore

Name and
MS .Sarade R.
Signature of
faculty

2023-24
AFFILIATED TO

M.S.B.T.E.
 SVP’s Swami Vivekanand Institute of Technology(Polytechnic),
Solapur
.

CERTIFICATE

This is to certify that the Project report entitled

Submitted by

Roll no Name of Student Enrollment no

08 Sanskar Shashikant Dongare 2212140102

is a bonafide work carried out by above students, under the guidance of Ms.Waghmare P.S .. and it
is submitted towards the fulfillment of requirement of MSBTE, Mumbai for the award of Diploma in
Computer Engineering at SVP’s COE (Polytechnic), Solapur during the academic year 2023-2024.

(Ms.Sarade R. )

Guide

(Ms.Waghmare P.S .) (MrsBhosale K. S.)

HOD Principal

Place: Solapur

Date: /
Title of Micro project: Different Testing Tools.

1.0 Brief Introduction

This project is about the Different Testing tools required to test the Software. Software Testing tools
are the tools that are used for the testing of software. Software testing tools are often used to assure
firmness, thoroughness, and performance in testing software products. Unit testing and subsequent
integration testing can be performed by software testing tools.
2.0 Aim of Micro Project:
The primary purpose of software testing is to detect flaws at any step of the development process.
The higher the number of issues detected at an early stage, the higher the software testing success
rate. Bug Prevention: This is the immediate action of bug discovery, that occurs as a result of bug
discovery.

3.0 Action Plan (Sequence and time required for major activities for 8 weeks)
Sr. Details of activity Planned start Planned Finish Name of Responsible
No date date Team Members
1 Collecting the information of view 1. Minto Singh
2 Sorting the information of view 2. Abhijeet Sawant
3 Compilation of the project 3. Satyam Kumar
4 Submission of the project

4.0 Resources required (major resources such as raw material, some machining facility, software,
etc.)
Sr. Name of resource/material Specification Quantity Remarks
NO
1 Browser Crome 1
2 Computer Ryzen 7 RAM 8GB Operating 1
System 64Bit
Introduction

Software Testing tools are the tools that are used for the testing of software. Software testing tools are
often used to assure firmness, thoroughness, and performance in testing software products. Unit
testing and subsequent integration testing can be performed by software testing tools. These tools are
used to fulfill all the requirements of planned testing activities. These tools also work as commercial
software testing tools. The quality of the software is evaluated by software testers with the help of
various testing tools.

Types of Testing Tools

Software testing is of two types, static testing, and dynamic testing. Also, the tools used during these
tests are named accordingly on these testings. Testing tools can be categorized into two types which are
as follows:

1. Static Test Tools: Static test tools are used to work on the static testing processes. In the
testing through these tools, the typical approach is taken. These tools do not test the real execution
of the software. Certain input and output are not required in these tools.
Static test tools consist of the following:

• Flow analyzers: Flow analyzers provide flexibility in the data flow from input to output.
• Path Tests: It finds unused code and code with inconsistency in the software.
• Coverage Analyzers: All rationale paths in the software are assured by the coverage analyzers.

• Interface Analyzers: They check out the consequences of passing variables and data in the
modules.
2. Dynamic Test Tools: The dynamic testing process is performed by the dynamic test
tools. These tools test the software with existing or current data. Dynamic test tools comprise the
following:

• Test driver: The test driver provides the input data to a module-under-test (MUT).
• Test Beds: It displays source code along with the program under execution at the same time.
• Emulators: Emulators provide the response facilities that are used to imitate parts of the system
not yet developed.
• Mutation Analyzers: They are used for testing the fault tolerance of the system by knowingly
providing the errors in the code of the software.

There is one more categorization of software testing tools. According to this classification, software
testing tools are of 10 types:

Test Management Tools: Test management tools are used to store information on how testing
is to be done, help to plan test activities, and report the status of quality assurance activities. For
example, JIRA, Redmine, Selenium, etc.

Automated Testing Tools: Automated testing tools help to conduct testing activities without
human intervention with more accuracy and less time and effort. For example, Appium, Cucumber,
Ranorex, etc.

Performance Testing Tools: Performance testing tools help to perform effectively and
efficiently performance testing which is a type of non-functional testing that checks the application for
parameters like stability, scalability, performance, speed, etc. For example, WebLOAD, Apache JMeter,
Neo Load, etc.

Cross-browser Testing Tools: Cross-browser testing tools help to perform crossbrowser

testing that lets the tester check whether the website works as intended when accessed through
different browser-OS combinations. For example, Testsigma, Testim, Perfecto, etc.

Integration Testing Tools: Integration testing tools are used to test the interface between the
modules and detect the bugs. The main purpose here is to check whether the specific modules are
working as per the client’s needs or not. For example, Citrus, FitNesse, TESSY, etc.

Unit Testing Tools: Unit testing tools are used to check the functionality of individual modules
and to make sure that all independent modules work as expected. For example, Jenkins, PHPUnit,
JUnit, etc.
Mobile Testing Tools: Mobile testing tools are used to test the application for compatibility on
different mobile devices. For example, Appium, Robotium, Test IO, etc.

GUI Testing Tools: GUI testing tools are used to test the graphical user interface of the software.
For example, EggPlant, Squish, AutoIT, etc.

Bug Tracking Tools: The bug tracking tool helps to keep track of various bugs that come up
during the application lifecycle management. It helps to monitor and log all the bugs that are detected
during software testing. For example, Trello, JIRA, GitHub, etc.

Security Testing Tools: Security testing is used to detect vulnerabilities and safeguard the
application against malicious attacks. For example, NetSparker, Vega, ImmuniWeb, etc.
Types of Software Testing
As we know, software testing is a process of analyzing an application's functionality as per the customer's
prerequisite.

If we want to ensure that our software is bug-free or stable, we must perform various types of software
testing because testing is the only method that makes our application bug-free.

The different types of Software Testing

The categorization of software testing is a part of diverse testing activities, such as test strategy, test
deliverables, a defined test objective, etc. Software testing is the execution of the software to find
defects.

The purpose of having a testing type is to confirm the AUT (Application Under Test).

To start testing, we should have a requirement, application-ready and, and necessary resources available.
To maintain accountability, we should assign a respective module to different test engineers.
The software testing is mainly divided into two parts, which are as follows:

• Manual Testing
• Automation Testing

What is Manual Testing?

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

In other words, we can say that it is a procedure of verification and validation. Manual testing is used to
verify the behavior of an application or software in contradiction of requirements specification.

We do not require any precise knowledge of any testing tool to execute the manual test cases. We can
easily prepare the test document while performing manual testing on any application.

To get detailed information about manual testing, click on the following link:
https://www.javatpoint.com/manual-testing.

Classification of Manual Testing

In software testing, manual testing can be further classified into three different types of testing, which
are as follows:

• 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.

Subsequently, the code is noticeable for developers throughout testing; that's why this process is
known as WBT (White Box Testing).

In other words, we can say that the developer will execute the complete white-box testing for the
particular software and send the specific application to the testing team.

The purpose of implementing white box testing is to emphasize the flow of inputs and outputs over the
software and enhance the security of an application.

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

Another type of manual testing is 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.

Then, the developers will fix those defects, do one round of White box testing, and send it to the testing
team.

Here, fixing the bugs means the defect is resolved, and the particular feature is working according to
the given requirement.

The main objective of implementing black box testing is to specify the business needs or the customer's
requirements.

In other words, we can say that black box testing is a process of checking the functionality of an
application as per the customer's requirement. The source code is not visible in this testing; that's why it
is known as black-box testing.
  Types of Black Box Testing

Black box testing is further categorized into two parts, which are discussed below:

• Functional Testing
• Non-function Testing

Further, it's divided into sub-topics.

Functional Testing

1. Unit Testing 2.
Integration Testing
3. System Testing.

Non-Function Testing

1. Performance Testing
2. Usability Testing
3. Compatibility Testing
.