MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION, MUMBAI

A Project Report
On

“Test Cases on Git-Hub Application”

In

Second Year Computer Engineering

Submitted by

MR. SHRIDHAR RAJENDRA SHELAR

MR. SANSKAR SAGAR BHUIMBAR

MR. SAHIL SHIVAJI DESAI

MR. ABHIMANYU ARJUN TIPPE

UNDER THE GUIDANCE OF

Mr. S. P. LATKAR
SANT GAJANAN MAHARAJ RURAL POLYTECHNIC MAHAGAON

ACADEMIC YEAR

2024 – 2025
 Maharashtra State Board of Technical Education, Mumbai

SANT GAJANAN MAHARAJ HOSPITAL & RESEARCH CENTER

SANT GAJANAN MAHARAJ RURAL POLYTECHNIC

AP/-MAHAGAON, SITE- CHINCHEWADI, TAL-GADHINGLAJ, DIST – KOLHAPUR

CERTIFICATE
THIS IS TO CERTIFY THAT THE FOLLOWING STUDENTS OF THIRD YEAR, FIFTH
SEMESTER OR DIPLOMA IN COMPUTER ENGINEERING OF INSTITUTE SANT
GAJANAN MAHARAJ RURAL POLYTECHNIC, MAHAGAON – (CODE-0965) HAS
COMPLETED MICRO PROJECT- “Test Cases on Git-Hub Application” – IN SUBJECT –
SOFTWARE TESTING (CODE- 22518) FOR ACADEMIC YEAR 2024-2025

ROLL
STUDENT NAME ENROLLMENT NO.
NO.
03 SHRIDHAR RAJENDRA SHELAR 2209650004

09 SANSKAR SAGAR BHUIMBAR 2209650012

55 SAHIL SHIVAJI DESAI 23212210180

58 ABHIMANYU ARJUN TIPPE 23212210184

DATE: PLACE: MAHAGAON

Mr.S.P.LATKAR Mr.G.K.BIRANGADDI Mrs.R.S.PATIL

(Project Guide) (Head Of Department) (PRINCIPAL)
 INDEX

SR NO CONTENTS PAGE NO

1.0 Rationale

Literature Review
2.0

Proposed Methodology
3.0

4.0 Action Plan

Resource Required
5.0

6.0 Course Outcome Integrated

7.0 Literature Review

8.0 Actual Procedure Followed

9.0 Actual Resources Required

Output of the Micro – Project

1. Introduction
10.0
2. Test Objective
3. Test Case Specification
4. Test Case
11.0 Skills Developed/Learning Out of this project

12.0 Application of this Micro-Project

13.0 Conclusion

13.1 References
 Part A – Micro-project Proposal
Title: “ Test Cases On Git-Hub Application”

1.0 Rationale:
In this project we are going to test an “Git-Hub Application” using Software Testing .This
project has been worked upon to create a test cases of GitHub Software. The software is tested
for anticipated behavior of common things that is done in GitHub by Developer and check for
possible errors in test cases which when are Confirmed to be affirmative, only then shall the
procedure ahead continue. It makes it easy for developers to share code files and collaborate
with fellow developers on open-source projects. GitHub also serves as a social networking
site where developers can openly network, collaborate their work.

2.0 Literature Review:

a) We require knowledge of various software testing techniques to test an
application.
b) We must know how to prepare Functionality Requirement Specification
document, as it contain all the functionality related to the software.
c) We must know how to prepare test cases for testing the specified software.
d) We should at last provide conclusion related to the project and Application.

3.0 Proposed Methodology:

a) Firstly ,we will decide which Software Testing Techniques are required to
test the “GitHub Application”.
b) Then we will prepare Functionality Requirement Specification Document
for GitHub Application.
c) We will then prepare Specification for GitHub Application.
d) Then we will design Test Cases for GitHub Application, to check the
functionality of software.
e) After that we will prepare a Defect Report if any serious bug or defect is
encountered in the software.
f) At last, we will prepare a Summary Report and provide a proper conclusion.
4.0 Action Plan:
Planned Name of responsible
Sr. Planned
Details of activity Finish team
No. Start date
date members
Shridhar Shelar
Decide the subject of Sanskar Bhuimbar
1.
project. Sahil Desai
Abhimanyu Tippe

Shridhar Shelar
Collecting information of
2. Sanskar Bhuimbar
project.
Sahil Desai

Shridhar Shelar
3. Designing Test cases.
Abhimanyu Tippe

Sanskar Bhuimbar
Execute Test Cases and
4. Sahil Desai
write the results of it
Abhimanyu Tippe

3. Creating report. Sahil Desai

5.0 Resource Required:

Sr. Name of resource /

Specification Quantity Remarks
No. material
Intel(R) Core (TM) i3 CPU32
1. Computer system 1 Used
bit operating system

2. Operating System Windows 11 _ Used

Microsoft Office - Excel

3. Software 2013, _- Used
Word 2013
Part B – Micro-project Report

6.0 Course Outcome Integrated:

a) Apply various software testing methods.
b) Prepare test cases for different types and levels of testing.
c) Prepare test plan for an application.
d) Test software for performance measures using automated testing tools.
e) Identify bugs to create defect report of given application.

7.0 Literature Review:

a) Firstly we will decide which Software Testing Techniques are required to
test the “GitHub Application”.
b) Then we will prepare Functionality Requirement Specification Document
for GitHub Application.
c) We will then prepare Test Cases for GitHub Application.
d) Then we will design Test Cases for GitHub Application, to check the
functionality of software.
e) After that we will prepare a Defect Report if any serious bug or defect is
encountered in the software.
f) At last we will prepare a Summary Report and provide a proper conclusion.

8.0 Actual Procedure Followed:

• Introduction to Software Testing and application of GitHub Application.
• Prepared Functionality Requirement Specification documents of GitHub Application .
• Prepared Test Cases for GitHub Application.
• Prepared & executed Test Cases for GitHub Application.
9.0 Actual Resources Required:

Sr. Name of resource

Specification Quantity Remarks
No. material
Intel(R) Core (TM) i31450
1. Computer system
CPU32 bit operating system
1 Used

2. Operating System Windows 11 - Used

Microsoft Office - Excel 2013,
3. Software
Word 2013
- Used

10.0 Outputs of the Micro-Project :

Prepare Test Cases for GitHub Application.

1. Introduction

The Test Plan is designed to prescribe the scope, approach, resources, and schedule of all testing
activities of the Git-Hub app.
The Plan identify the item to be tested ,the features to be tested, the types of testing to be performed
,the personnel responsibility for testing, the resource and schedule required to complete testing,
and risks associated with the plan.

2. Test Objective

The Test objective is to verify the Functionality of app Git-Hub, the project should focus on the
registration on the Git-Hub Application.

3. Test Case Specification

This project has been worked upon to create a test cases of GitHub software.
The software is tested for anticipated behavoir of common things that is done in GitHub
by Developer and check for possible errors in test cases which when are Confirmed to be
affirmative,only then shall the procedure ahead continue.
GitHub is an online software development platform used for storing,tracing and
collaborating on software project.It enables developers to upload their own code files and
to collaborate with fellow developers on open source projects.
It also serves as a social networking sites in which developers can openly network and
collaborate their work.
And in test case we discuss the major cases that always performed.
 4.Test Cases:-

Test-
Test Test Pre- Expected Actual Statu
case Test steps Test data
Scenario Case condition results results s
ID
To 1.Enter
"MindTeste
Verify verif Username
Username r" It should Registered
Github y the 2.Enter Email
TC-1 , Email, "Tester@12 be Successful Pass
applicatio regist ID
Password 3.com" registered ly
n ration 3.Enter
Tester1122
. Password
To 1.Enter Owner
verif Owner, 2.Enter
Verify Repository
y Repositor Repository "MindTeste Repository
Github created
TC-2 creati y Name, Name r" "Smart should be Pass
applicatio Successful
on of Descriptio 3.Enter Home" created
n ly
regist n Description
ration (optional)
To
verif Name Of
1.Enter Name
Verify y Project, "Digital Project
Of Project Project
Github copyi project Watch" copied
TC-3 2.Click On should be Pass
applicatio ng should be Copy Successful
Project copied
n the pre – project ly
3.Click on src
proje made
ct
To 1. Initialize the Code
Verify git add. && Code
verif local directory Pulled &
Github Root git commit should be
TC-4 y as a Git Pushed Pass
applicatio Project "initial Pulled &
pull,p repository Successful
n commit" Pushed
ush 2.Open cmd ly
Navigatin 1. Click on a
Verify Chec g directly file 2. then History
History
Github k the to the click on checked
TC-5 git log should be Pass
applicatio histor commits history 3. view Successful
checked
n y page of a the commit ly
repository history
1. under your
repository
Navigate
Verify Delet name, click Repository
to the Click on Repository
Github e settings Deleted
TC-6 main page "Delete this should be Pass
applicatio repos 2.under danger Successful
of the repository" Deleted
n itory zone, click ly
repository
delete
repository
11.0 Skill Developed/learning out of this Micro-Project:-
This Project is created for improving the testing knowledge of applications.
1. Studying of the different types of testing techniques.
2. Learned how to prepare Test Cases to test if the application is working properly or not.
3. Learned about SRS (Software Required Specification) document.
4. Studied advantages and disadvantages of testing and how necessary it is to build a defect
free software and user friendly.

12.0 Application of this Micro-Project:-

The Proposed GitHub application is the completely computerized.
1. In proposed system there is no need to maintain data about medical because all process of
that data done in computerized.
2. The modern age the age of computer is an electronic device, which fetched record very
quickly. The computers are very quickly accepted in trade line as it as many advantages
such as speed, accuracy, security etc.
3. In this proposed system all the add, edit, delete, search in project of computer are done
through computerized system.
4. Easy and fast retrieval of information.
5. Better storage capability. More efficient operation.
13.1 Conclusion :
Testing is a critically important verification method that takes up a very large portion of a
project’s resources, including schedule, budget, staffing, and facilities. Unlike the many
constructive activities of systems engineering, testing is relatively unique because it is inherently
destructive. Its primary purpose is to force the system or its components to fail so that the defects
that caused the failure can be uncovered and then fixed. In addition to defect detection, testing is
also performed to provide sufficient objective evidence to justify confidence in the system’s
quality, fitness for purpose, and readiness for being accepted and placed into operation.

13.2 References :

Web References:
https://www.javatpoint.com/software-testing-principles
https://www.browserstack.com/guide/how-to-write-test-cases
https://www.geeksforgeeks.org/software-testing-tutorial/?ref=lbp
https://docs.github.com/en/apps/github-marketplace/using-the-github-marketplace-api-in-your-
app/testing-your-app
https://www.guru99.com/top-20-test-management-tools.html

Book References:
“Software Testing” Second Edition, ISBN 978-81-7758-031-0, Ron Patton, Pearson publication.