JSPM’s

JAYAWANTRAO SAWANT POLYTECHNIC,

Handewadi Road, Hadapsar, Pune-28
Department of Computer Engineering
Academic Year 2023-24

MICRO PROJECT

TITLE OF THE PROJECT

Different Testing Tools

Program: CO Program code: CO5I

Course: STE Course code: 22518
Class: TYCO-2 Group No: M
Project Guide: Mrs. R. F. Shikhare

1
 MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION

Certificate
This is to certify that Mr. Singh Minto Hansraj, Sawant Abhijeet
Naganath and Satyam Kumar of the 5th Semester of Diploma in
Computer Engineering of Institute Jayawantrao Sawant
Polytechnic (Code: 0711) have completed the Micro Project
satisfactorily in Subject – STE (22518) for the academic year 2023-
2024 as prescribed in the curriculum.
Place: Hadapsar, Pune. Enrollment No: 1. 2107110320
2. 2107110324
3. 2107110452

Date: -------------- Exam Seat No: ------------------

-------------------------------------

Subject Teacher Head of the Department Principal

2
 MICRO PROJECT
GROUP DETAILS

Roll Enrollment
Sr No. Name Seat No.
No. No.

1 53 Abhijeet Naganath Sawant 2107110320

2 56 Singh Minto Hansraj 2107110324

3 109 Satyam Kumar 2107110452

3
 INDEX

Sr No. Content Page No.

1 Certificate 2

2 Group Details 3

3 Index 4

4 Annexure I (Part A) 5

5 Introduction 6-8

6 Types of Software Testing 9-14

7 Manual Testing and Autonomous Testing 15

8 Different Testing Tools. 16-26

9 Benefits of Software Testing Tools 27

10 Factors to consider when choosing a Software Testing Tool 28

11 Annexure II (Part B) 29

12 Annexure IV (Teachers Evaluation Sheet) 30-35

4
 JSPM’s
JAYAWANTRAO SAWANT POLYTECHNIC, Handewadi Road,
Hadapsar, Pune-28
Department of Computer Engineering
Academic Year 2023-24

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 Specification Quantity Remarks

NO resource/material
1 Browser Crome 1
2 Computer Ryzen 7 RAM 8GB Operating 1
System 64Bit

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

6
  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 cross-

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

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

8
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).

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

10
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

For our better understanding let's see them one by one:

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.

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

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

13
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

14
Manual Testing and Autonomous Testing.

What is Manual Testing?

Manual testing is a process in which test cases are executed manually without the help of
any automated tool. It ensures that all the functions in the application are working, as
defined in the requirement document. Since no tools are involved in Manual Testing, it is
slow, repetitive, costly, and time-consuming. Manual testing is helpful where human
interaction is required and better suited. For example, User Acceptance testing is a type of
manual testing performed when human intervention is necessary to test the ready-to-use
product before releasing it in the market. Manual testing always takes place when human
intervention is needed and needs to test the application from a user perspective. Let’s
look at an example below to understand better how Manual Testing works.

What is Automation Testing?

Automation Testing is a technique that uses tools to write scripts and execute test cases. It
is the best way to enhance the execution speed, effectiveness, and test coverage in
software testing. Besides, it is cost-effective and helps find possible bugs quickly.

15
Different Testing Tools

Choosing the right automation testing tool

Automation testing tools are applications designed to verify function and/or non-
functional software requirements via automated test scripts. To help accelerate release
velocity, improve project quality, and strengthen outcomes. Automation testing tools
allow you to effortlessly create, run, and maintain tests and support a centralized view of
analytics of test results.
As Agile and DevOps practices serve as the standard for software testing, establishing a
clear-cut automation testing tool evaluation strategy is essential. Ultimately, this strategy
needs to answer the following questions:
1. What features are you looking for?
2. Who’s going to use the tool for testing? Devs or QA teams?
3. Can it be integrated with CI/CD pipelines or toolchains?
4. Is it easy to maintain scripts and reuse test assets?
5. What is your team’s budget?
6. Where can you get support for technical issues?
Unfortunately, there isn’t a one-size-fits-all automation tool; it boils down to your team’s
specific needs.

16
Select your best-fit automation testing tool
To pick the best automation testing tool for your team, don’t just blindly follow other
teams’ success. Instead, look at your team’s specific needs, human resources, and future
scalability to choose the best-fit option. For example, if your team’s testers are
experienced developers, using Selenium or Appium for an automation framework is a
good option since it allows you to build and scale from the ground up. However, if your
team consists of mostly manual testers and you need a low-code solution to start, but
one that can also grow and scale, ready-made frameworks like the Katalon Platform can
be a perfect solution.
The following is our list of the top 15 automation testing tools available to support your
testing needs.

Top 15 automation testing tools (with feature highlights)

17
 1. The Katalon Platform

The Katalon Platform is a low-code and scalable automation testing tool for web,
API, desktop (Windows), and mobile applications. To date, the Katalon community has
surpassed one million users and is the trusted automation solution of over 100,000
businesses.
Without having to code or build a test automation framework from scratch, users can
simply download the tool and focus solely on testing. Additionally, Katalon offers frequent
releases to stay compatible with the latest platforms/browsers/OS.

Feature highlights:
 Flexible methods for test design: record & playback, manual, and scripting mode
 Supported testing methodologies: BDD, DDT, keyword-driven testing, cross-
browser testing (Headless, Chrome, Edge, Firefox, and Safari), and cross-platform
mobile testing (iOS, Android)
 Automatic retry failed tests, smart wait, and self-healing mechanisms
 Reusable test objects, keywords, and test cases with test artifact sharing and page
object model design
 Native integrations with popular CI/CD and ALMs tools (Jira, GitLab, Jenkins,
Bitbucket, Azure DevOps, etc.)
 Smart debugging UI and test reporting to troubleshoot failures quickly
 Integration with popular collaboration tools for better test planning
 Detailed tool documentation and video tutorials on Katalon Academy
Website: https://katalon.com/
Price: Free and flexible paid plans

18
 2. Selenium

Rolled out in 2004, Selenium is one of the most, if not the most, popular open-source
frameworks for web testing automation. Its suite of software consists of Selenium
WebDriver, Selenium Grid, and Selenium IDE.
Feature highlights:
 Supported programming languages: Java, C#, Python, JavaScript, Ruby, PHP, etc.
 Supported browsers: Chrome, Firefox, IE, Microsoft Edge, Opera, Safari, etc.
 Testing on local or remote machines via the Selenium server
 Parallel and cross-browser executions to reduce execution time and increase test
coverage
 Integrations with other testing frameworks (e.g., TestNG for reporting) and CI/CD
tools
Website: https://www.selenium.dev/
Price: Free

3. Appium

Like Selenium, Appium is also an open-source automation testing tool, for mobile
applications. Using mobile JSON wire protocol, Appium allows users to write automated
UI tests for native, web-based, and hybrid mobile applications on both Android and iOS.
Feature highlights:
 Supported programming languages: Java, C#, Python, JavaScript, Ruby, PHP, Perl
 Cross-platform testing with reusable test scripts and the same APIs
 Execution across real devices, simulators, and emulators

19
  Integrations with other testing frameworks and CI/CD tools
Website: https://appium.io/
Price: Free

4. TestComplete

TestComplete can automate functional UI testing for desktop, mobile, and web
applications. With built-in support for 500+ controls and third-party frameworks,
TestComplete can handle and identify dynamic UI elements in most available
technologies.
Feature highlights:
 Supported programming languages: JavaScript, Python, VBScript, JScript, Delphi,
C++, C#
 Flexible methods for test design: record & playback, manual, and scripting modes
with built-in keywords
 Object identification with property-based and AI visual recognition
 Parallel, cross-browser, and cross-device testing
 Integrations with other testing frameworks, CI/CD tools, and SmartBear ecosystem
Website: https://smartbear.com/product/testcomplete/overview/
Price: From $2,702/year

5. Cypress

Purely supporting JavaScript frameworks, Cypress is a developer-centric automation tool

for end-to-end web testing. Built upon a new architecture, Cypress can directly operate

20
within a browser in the same run-loop as your application, enabling native access to
elements and faster executions.
Feature highlights:
 Supported programming language: JavaScript
 Snapshots of test step execution and debuggability from familiar developer tools
 Control over function behavior, server response, timers, and network traffic
 Connection to Cypress Cloud for test performance and optimization
 Integrations with popular CI/CD tools
Website: https://www.cypress.io/
Price: Free or from $75/month for Cypress Cloud

6. Ranorex Studio

Ranorex Studio can automate GUI testing for web, mobile, and desktop applications.
Equipped with both low-code automation and full IDE, Ranorex’s framework is easy to
start for beginners and productive to use for experienced testers.
Feature highlights:
 Supported programming languages: VB.Net and C#
 Broad support for web, mobile, and desktop technologies
 Ranorex Spy tool and RanoreXPath for reliable recognition of GUI elements
 Flexible methods for test design: record & playback and scripting mode
 Distributed or parallel testing with Selenium Grid
 Integrations with other testing frameworks and CI/CD tools
Website: https://www.ranorex.com/
Price: From €2,890/year

21
 7. Perfecto

Perfecto is a cloud-based and automated testing platform for web and mobile
applications. From automated cross-environment executions, custom capabilities, test
analysis, and broad integrations, Perfecto makes continuous testing more achievable for
DevOps teams.
Feature highlights:
 Scriptless test creation for UI web applications
 Real-user stimulation for mobile testing: network visualization and other
environmental conditions
 Parallel and cross-platform executions
 Advanced test analytics with a centralized dashboard and AI noise filtering
 Integrations with other testing frameworks and CI/CD tools
Website: https://www.perfecto.io/products/platform/overview
Price: From $125/month

8. LambdaTest

LambdaTest provides automated testing on the cloud. Its cloud service allows teams to
scale up their test coverage with speedy parallel, cross-browser, and cross-device testing.
Feature highlights:
 Online Selenium Grid on the cloud of over 2,000 devices, browsers, and OSs
 Support for Cypress test scripts parallel and cross-browser executions
 Geolocation web testing across over 27 countries
 Integrations with other testing frameworks and CI/CD tools
Website: https://www.lambdatest.com/automation-testing
Price: From $99/month

22
 9. Postman

Postman is one of the most widely used automation testing tools for API. It allows users
to write different kinds of tests, from functional and integration to regression tests, and
execute them automatically in CI/CD pipelines via the command line.
Feature highlights:
 Friendly and easy-to-use interface equipped with code snippets
 Support for multiple HTML methods, Swagger, and RAML formats
 Broad support for API schemas to generate collections and API elements
 Test suite creation, executions with parameterization, and debugging
 Integrations with popular CI/CD tools
Website: https://www.postman.com/
Price: Free or from $12/user/month

10. _SoapUI

This open-source API testing tool is designed for REST and SOAP web services. Some vital
features include automated functional, performance, regression, and security testing.
Users can also aim for the commercial version, ReadyAPI (formerly SoapUI Pro), for more
advanced capabilities.
Feature highlights:
 Drag and drop to create tests, even with complex scenarios
 Service stimulation to reduce efforts of building production systems for testing
 Quick and easy test script reusability
 More protocol support, capabilities, and CI/CD integration with ReadyAPI
Website: https://www.soapui.org/
Price: Free or from $749/year for ReadyAPI

23
 11._Eggplant Functional

As part of Eggplant’s ecosystem, Eggplant Functional is a GUI automation testing tool for
mobile, desktop, and web applications. With an image-based approach, it allows a single
script to automate different combinations of platforms and technologies.
Feature highlights:
 Flexible methods for test design: recording, manual mode, and assisted scripting
 Unique English-like scripting language: SenseTalk
 Connection to the Eggplant ecosystem for more testing capabilities and
monitoring
 Integrations with popular CI/CD tools
Website: https://www.eggplantsoftware.com/product-downloads
Price: Contact sales

12._Tricentis Tosca

Tricentis Tosca is a comprehensive automation tool for web, API, mobile, and desktop
testing. It has a unique model-based testing approach, allowing users to scan an
application’s UI or APIs to create a business-familiar model for test creation and
maintenance.
Feature highlights:
 Codeless test creation and high reusability of test assets with the model-based
approach
 Risk-based test optimization with smart test design and requirement prioritization
 Service virtualization to stimulate and build realistic testing environments
 API scanning with extensive support for API Technologies
 Parallel and cross-platform testing

24
  Integrations with other testing frameworks and CI/CD tools

Website: https://www.tricentis.com/products/automate-continuous-testing-tosca/
Price: Contact sales

13. Apache JMeter

This open-source tool is designed for automated performance testing, primarily for web
applications. It can stimulate a heavy load of users to access web services and analyze the
AUT’s performance. JMeter can also be used for functional API testing.
Feature highlights:
 Friendly and easy-to-use interface
 Test plan creation with recording feature
 Test execution in both GUI and CLI modes
 Support for many different servers, applications, and protocol types
 Integrations with popular CI/CD tools
Website: https://jmeter.apache.org/
Price: Free

14. Robot Framework

Robot Framework is a generic open-source framework for test automation, especially for
acceptance testing and acceptance test-driven development. Built with a keyword-driven
approach, it’s low-code to start and also extensible with a rich ecosystem of tools and
libraries.
Feature highlights:
 Test case creation with easy tabular syntax

25
  Keyword-driven and data-driven testing support

 Variables for testing in different environments

 Support for plenty of external libraries and integrations with other tools
Website: https://robotframework.org/
Price: Free

15. Protractor

This open-source framework automates end-to-end testing primarily for Angular and
AngularJS applications. It works as an integrator of Selenium, WebDriver, Jasmine,
Node.js, and other technologies. Protractor can also work well for regression testing with
non-Angular apps.
Feature highlights:
 Test execution in a real browser using native events
 Element identification in Angular applications with extended HTML attributes
 Support for behavior-driven development frameworks like Jasmine and Mocha
 Automatic waiting
 Parallel and cross-browser testing with Selenium Grid
Website: https://www.protractortest.org/
Price: Free

26
Benefits of Software Testing Tools
Software testing tools offer many benefits for developers, testers, and QA teams.

 Higher product quality. Software testing tools help deliver higher-quality

applications by improving the accuracy of tests, increasing the coverage of
code that is tested, accelerating the pace of testing, and delivering feedback to
developers earlier in the process.

 Improved security. Cybercrime is a substantial threat to organizations large

and small, and software vulnerabilities are a significant target for malicious
actors. Software testing tools help ensure that applications are free of flaws
and vulnerabilities that hackers can exploit, protecting companies, their users,
partners, and customers from exposure to cyber criminals.

 More cost-effective development. By uncovering defects and design issues

earlier in the software developer lifecycle, software testing tools enable
developers to fix bugs more easily and cost-effectively.

 Ensure compatibility. Software testing tools can help ensure that a piece of
software will work across multiple browsers, operating systems, and devices.

 Greater customer satisfaction. Ultimately, software testing tools help

development organizations deliver products that satisfy customer
requirements and expectations.

27
Factors to consider when choosing a Software
Testing Tool

 Cost: The most critical factors when choosing a testing tool are budget, cost,
and end-user requirements. Depending on the size of your team or your usage
choice, you need to opt for a solution.

 Compatibility: Your testing tools should efficiently run and execute test cases
on different cross-browser platforms, and it will save time from running test
cases on different platforms manually.

 Ease of use: Select a user-friendly testing tool. Otherwise, your test process
will be time-consuming and you will need to put extra effort into getting
accustomed to the tool.

 Technical support: The testing tools vendor should provide all possible
technical support for their users. A good testing tool should have features like
FAQs, live chat, phone calls, email support, an online user guide, product
documentation, help desk tickets, and more.

 Community support: A software tester must join a community to meet

people with the same profession. It’s helpful for independent testers to know
trending software testing tools and techniques.

28
 JSPM’s
JAYAWANTRAO SAWANT POLYTECHNIC, Handewadi Road,
Hadapsar, Pune-28
Department of Computer Engineering
Academic Year 2023-24

Title of Micro project: Different Testing Tools.

1.0 Brief Description:

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 Course Outcome Integrated

----------------------------------------------------------------------------------------------------------------------
4.0 Actual Procedure Followed.
1. Decided project name.
2. Made the logic for the Code.
3. Made the code and removed all the errors from the code.
4. Tested the code to see if it's working properly or not.
5. Made the report for the representation.

5.0 Actual Resources Used (mention the actual resources used.)

Sr. Name of Specification Quantity Remarks
NO resource/material
1 Browse Crome 1
2 Computer Ryzen 7 RAM 8GB Operating System 64Bit 1

6.0 Outputs of the Micro Projects

-----------------------------------------------------------------------------------------------------------------------
----------------------------------------------------------------------------------------------------------------------
7.0 Skill Developed/ Learning out of this Micro project
Throughout this project, we developed some important skills like leadership quality, scheduling of
the project, and risk management. One of the most important skills we developed is the
communication and coordination between our team members. We also learned planning skills, time
management, and adaptability.

29
 Teacher Evaluation Sheet

Name of students: Singh Minto Hansraj

Enrollment No: 2107110324
Name of program: Computer Engineering
Semester: 5th
Course Title: STE
Code: 22518
Title of Micro Project: Different Testing Tools.
Course Outcomes Achieved:
1.

Evaluation as per suggested Rubric for Assessment of Micro Project

Sr. Characteristics to be Poor Average Good Excellent
No assessed
(Marks1- (Marks 4 - (Marks 6 - (Marks 9 -
3) 5) 8) 10)
1 Relevance to the course
2 Literature Survey /
Information Collection
3 Project Proposal
4 Completion of the Target as
per the Project Proposal
5 Analysis of data and
representation
6 Quality of Prototype/ Model
7 Report preparation
8 Presentation
9 Defense

30
Micro Project Evaluation Sheet
Process Assessment Product Assessment Total
Marks
Part A - Project Project Par B - Project Individual
Proposal Methodology Report/Working Presentation/ Viva 10
Model
(2 Marks) (2 Marks) (4 Marks)
(2 Marks)

Note: Every course teacher is expected to assign marks for group evaluation in the first 3
columns and individual evaluation 4th column

Comment/ suggestion about teamwork/leadership/ interpersonal communication (If any)

………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………
………………………………………………………………………………………………………
………………………………………………
Any other comment:
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………

Name and Designation of the Faculty Member: Mrs. R. F. Shikhare

Signature: ………………………….

31
 Teacher Evaluation Sheet

Name of students: Sawant Abhijeet Naganath

Enrollment No: 2107110320
Name of program: Computer Engineering
Semester: 5th
Course Title: STE
Code: 22518
Title of Micro Project: Different Testing Tools.
Course Outcomes Achieved:
1.

Evaluation as per suggested Rubric for Assessment of Micro Project

Sr. Characteristics to be Poor Average Good Excellent
No assessed
(Marks1- (Marks 4 - (Marks 6 - (Marks 9 -
3) 5) 8) 10)
1 Relevance to the course
2 Literature Survey /
Information Collection
3 Project Proposal
4 Completion of the Target as
per the Project Proposal
5 Analysis of data and
representation
6 Quality of Prototype/ Model
7 Report preparation
8 Presentation
9 Defense

32
Micro Project Evaluation Sheet
Process Assessment Product Assessment Total
Marks
Part A - Project Project Par B - Project Individual
Proposal Methodology Report/Working Presentation/ Viva 10
Model
(2 Marks) (2 Marks) (4 Marks)
(2 Marks)

Note: Every course teacher is expected to assign marks for group evaluation in the first 3
columns and individual evaluation 4th column

Comment/ suggestion about teamwork/leadership/ interpersonal communication (If any)

………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………
………………………………………………………………………………………………………
………………………………………………
Any other comment:
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………

Name and Designation of the Faculty Member: Mrs. R. F. Shikhare

Signature: ………………………….

33
 Teacher Evaluation Sheet

Name of students: Satyam Kumar

Enrollment No: 2107110452
Name of program: Computer Engineering
Semester: 5th
Course Title: STE
Code: 22518
Title of Micro Project: Different Testing Tools.
Course Outcomes Achieved:
1.

Evaluation as per suggested Rubric for Assessment of Micro Project

Sr. Characteristics to be Poor Average Good Excellent
No assessed
(Marks1- (Marks 4 - (Marks 6 - (Marks 9 -
3) 5) 8) 10)
1 Relevance to the course
2 Literature Survey /
Information Collection
3 Project Proposal
4 Completion of the Target as
per the Project Proposal
5 Analysis of data and
representation
6 Quality of Prototype/ Model
7 Report preparation
8 Presentation
9 Defense

34
Micro Project Evaluation Sheet
Process Assessment Product Assessment Total
Marks
Part A - Project Project Par B - Project Individual
Proposal Methodology Report/Working Presentation/ Viva 10
Model
(2 Marks) (2 Marks) (4 Marks)
(2 Marks)

Note: Every course teacher is expected to assign marks for group evaluation in the first 3
columns and individual evaluation 4th column

Comment/ suggestion about teamwork/leadership/ interpersonal communication (If any)

………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………
………………………………………………………………………………………………………
………………………………………………
Any other comment:
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………………………………………………………………………
………………………………………

Name and Designation of the Faculty Member: Mrs. R. F. Shikhare

Signature: ………………………….

35