Annexure – I

Micro-Project Proposal
Test cases & Defect report for Digital Clock using Swing

1.0. Aims/Benefits of the Micro-Project

1. Its helps to know about Test Case.
2. Its helps to understand how to write Test Case.
3. Its helps to know Test Case Specifications.

2.0 Course Outcomes Addressed

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

3.0 Project Methodology

1. Planning the overview of the project.
2. Analyzing the various way of data communication through Bluetooth connectivity.
3. Authentication of relevant information collected through various media.
4. We have experimented about exchanging data through Bluetooth connectivity.
5. Initiating for project.

4.0 Action Plan

Planned
Sr. Planned Name of Responsible
Details of activity Finish
No. Start Date Team Member
Date
Information Gathering and Topic
1
Finalization
Preparing Project Proposal and
2
Approval
3 Implementing Project

4 Preparing Project Report

5 Presenting Project

6 Submission of Project and Report

MET’s Institute of Technology, Polytechnic, Nashik 1

5.0 Resource Required
Sr.
Name of Resource/Material Specifications Qty. Remarks
No.
HP-Victus
AMD Ryzen 5 5600H with
1 Computer System 01
Radeon Graphics 3.30
GHz 8.00 GB RAM
2 Editor MS Word 01

Name of Member with Roll No and Enrollment No.

Roll No Enrollment No Name of Member

08 2107760011 Jadhav Atahrv Kailas

Approved by

(Prof. Priyanka B. Khairnar_)

Name and Signature of Staff

MET’s Institute of Technology, Polytechnic, Nashik 2

 Annexure – II
Micro-Project Report
Test cases & Defect report for Digital Clock using Swing
1.0. Rationale
Software testing can be stated as the process of verifying and validating whether a
software or application is bug-free, meets the technical requirements as guided by its
design and development, and meets the user requirements effectively and efficiently
by handling all the exceptional and boundary cases.
o The process of software testing aims not only at finding faults in the existing software
but also at finding measures to improve the software in terms of efficiency, accuracy,
and usability. It mainly aims at measuring the specification, functionality, and
performance of a software program or application.

2.0. Aims/Benefits of the Micro-Project

1. helps to know about Test Case.
2. Its helps to understand how to write Test Case.
3. Its helps to know Test Case Specifications

3.0 Course Outcomes Addressed

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

4.0 Literature Review

➢ Memory Test case in Software testin

The test case is defined as a group of conditions under which a tester determines
whether a software application is working as per the customer's requirements or
not. Test case designing includes preconditions, case name, input conditions, and
expected result. A test case is a first level action and derived from test scenarios.

A test case is a defined format for software testing required to check if a particular
application/software is working or not. A test case consists of a certain set of conditions
that need to be checked to test an application or software i.e. in more simple term
when conditions are checked it checks if the resultant output meets with the expected
output
or not. A test case consists of various parameters such as Id, condition, steps, input,
expected result, result, status, and remarks.

MET’s Institute of Technology, Polytechnic, Nashik 3

 ➢ Test Case Parameters
1) Test Case ID
2) Test Scenario
3) Test Steps
4) Prerequisites
5) Test Data
6) Expected/Intended Results
7) Actual Results
8) Test Status – Pass/Fail

➢ Objectives of Test Case:-

1) Finding defects which may get created by the programmer while developing the
2) software.
3) Gaining confidence in and providing information about the level of quality.
4) To prevent defects.
5) To make sure that the end result meets the business and user requirements.
6) To ensure that it satisfies the BRS that is Business Requirement Specification and
SRS
7) that is System Requirement Specifications.
8) To gain the confidence of the customers by providing them a quality product.

➢ Advantages of Test Case :-

1) Guaranteed good test coverage.
2) Reduced maintenance and software support costs.
3) Reusable test cases.
4) Confirmation that the software satisfies end-user requirements.
5) Improved quality of software and user experience.
6) Higher quality products lead to more satisfied customers.
7) More satisfied customers will increase company profits.

➢ Disadvantages of Test Case:

1) It takes time to write test cases.
2) It's difficult to write tests for legacy code.
3) Tests require a lot of time for maintenance.
4) It can be challenging to test GUI code.
➢ Types of Test Case:
Functionality test cases
This is a type of black box testing that can reveal if an app's interface works with the rest of
the system and its users by identifying whether the functions that the software is expected
to perform are a success or failure. Functionality test cases are based on system

MET’s Institute of Technology, Polytechnic, Nashik 4

 specifications or user stories, allowing tests to be performed without accessing the internal
structures of the software. This test case is usually written by the QA team.

Performance test cases

These test cases can help validate response times and confirm the overall effectiveness of
the system. Performance test cases include a very strict set of success criteria and can be
used to understand how the system will operate in the real world. Performance test cases
are typically written by the testing team, but they are often automated because one system
can demand hundreds of thousands of performance tests.

Unit test cases

Unit testing involves analyzing individual units or components of the software to confirm
each unit performs as expected. A unit is the smallest testable element of software. It often
takes a few inputs to produce a single output.

User interface test cases

This type of test case can verify that specific element of the graphical user interface (GUI)
look and perform as expected. UI test cases can reveal errors in elements that the user
interacts with, such as grammar and spelling errors, broken links and cosmetic
inconsistencies. UI tests often require cross-browser functionality to ensure an app
performs consistently across different browsers. These test cases are usually written by the
testing team with some help from the design team.

Security test cases

These test cases are used to confirm that the system restricts actions and permissions when
necessary to protect data. Security tests cases often focus on authentication and encryption
and frequently use security-based tests, such as penetration testing. The security team is
responsible for writing these test cases -- if one exists in the organization.

Integration test cases

An integration test case is written to determine how the different software modules interact
with each other. The main purpose of this test case is to confirm that the interfaces
between different modules work correctly. Integration test cases are typically written by the
testing team, with input provided bythe development team.

Database test cases

This type of test case aims to examine what is happening internally, helping testers
understand where the data is going in the system. Testingteams frequently use SQL queries
to write database test cases.

MET’s Institute of Technology, Polytechnic, Nashik 5

 Usability test cases
A usability test case can be used to reveal how users naturally approach and use an
application. Instead of providing step-by-step details, a usability test case will provide the
tester with a high-level scenario or task to complete. These test cases are typically written
by the design and testing teams and should be performed before user acceptance testing.

User acceptance test cases

These test cases focus on analyzing the user acceptance testing environment. They are
broad enough to cover the entire system and their purpose is to verify if the application is
acceptable to the user. User acceptance test cases are prepared by the testing team or
product manager and then used by the end user or client. These tests are often the last step
before the system goes to production.

Regression testing
This test confirms recent code or program changes have not affected existing system
features. Regression testing involves selecting all or some of the executed test cases and
running them again to confirm the software's existing functionalities still perform
appropriately.

Test Case Expected

Test Case ID Input Data Actual Result Status
Name Result
Current time
Time displayed in Current
1 Launch Passed
Display the format time
Application
"hh:mm:ss a" displayed
correctly
Current day of
the week Current day
Day Display
2 Launch displayed of the week Passed
Application displayed
correctly
Current date Current date
Date displayed in displayed
3 Launch Passed
Display the format correctly
Application
"MMMMM dd,
yyyy"
itle of the Title of the
Window window should window is "My
4 Launch be "My Clock Clock Program" Passed
Title
Application Program"
Window size
Window should be Window size
5 Launch Passed
Size 350x200 pixels is 350x200
Application
pixels
Window Window is not
Resize
6 Window Not should not be resizable Passed
Window
Resizable resizable

MET’s Institute of Technology, Polytechnic, Nashik 6

 Time label font
Time N/A size should be Time label
7 Passed
Font 50 font size is 50
Size
N/A Time label font Passed
Time Font color should be Time label
8 green font color is
Color
(0x00FF00) green
(0x00FF00)
Time label Time label
Time N/A background background
9 Passed
Backgrou color should be color is black
nd Color black
Time label
Time Label N/A should be Time label is
10 Passed
Opaque opaque opaque
Property
N/A Day label font
Day Font size should be Day label font
11 Passed
Size 35 size is 35
Day Font N/A Day label font Day label font
12 Family family should family is "Ink Passed
be "Ink Free" Free"
N/A Day label font
Day Font family should Day label
13 Passed
Family be "Ink Free" font family is
"Ink Free"
Date label font Passed
N/A family should Date label
Date Font
14 be "Ink Free" font family
Family
is "Ink
Free"
Date format Passed
Date Launch should be Date format
15 Display Application "MMMMM dd, is
Format yyyy" "MMMMM
dd, yyyy"
Wait for 5 Passed
Time Update seconds Time label
Time label
16 should update
updates
every second
correctly
for 5 seconds
every second
for 5 seconds
Wait for 5 Day label Passed
Day Update seconds Day label updates
17 should update correctly
every second every second
for 5 seconds for 5 seconds
Wait for 5
Date Update
seconds Date label
Date label
18 should update Passed
updates
every second
correctly
for 5 seconds
every second
for 5 seconds

MET’s Institute of Technology, Polytechnic, Nashik 7

 Multiple Labels Launch Passed
Display Application All three
All three
19 labels (Time,
labels are
Day, Date)
displayed
should be
correctly
displayed
Time should be Passed
Time Display Wait for 1 displayed Time is
20 Continuity minute continuously displayed
without continuousl
interruption y without
interruption
Wait for 1 Passed
Day Display minute Day should be
Day is
21 Continuity displayed
displayed
continuously
continuously
without
without
interruption
interruption
N/A Passed
Date Date format
Date format is
22 Format should be
valid
Validity valid
(MMMMM
(MMMMM
dd, yyyy)
dd, yyyy)
Time Format Time format Time format Passed
Validity N/A
should be is valid
valid (hh:mm:ss a)
23
(hh:mm:ss a)

Day Format Passed

Validity N/A Day format
Day format is
24 should be
valid (EEEE)
valid (EEEE)
Exit Passed
Application Application
Click Close Application
25 should exit
Button exits correctly

Window Passed
Position after Restart
Window Window is
Restart Application
26 position centered after
should be restart
centered
after restart
Time Label Passed
Alignment N/A Time label Time label is
27 should be horizontally
horizontally centered
centered
Day Label N/A Day label Passed
Alignment should be Day label is
28 horizontally horizontally
centered centered
Date label
Date Label N/A should be Date label is
29 Alignment horizontally horizontally Passed
centered centered

MET’s Institute of Technology, Polytechnic, Nashik 8

 ➢ Defect Report
A defect report is a document that includes complete details about the application/software
defects, sources, what are the actions needed to resolve them, and the expected result.
Developers can check this defect report, understand the problem & its solution and make
improvements accordingly.

➢ attributes of defect
1. Defect ID
2. Defect Name
3. Project Name
4. Module Name
5. Phase introduced
6. Phase found
7. Defect type
8. Severity
9. Priority
10. Summary
11. Description
12. Status
13. Reported by/ Reported on
14. Assigned to, etc…..

MET’s Institute of Technology, Polytechnic, Nashik 9

Defect Report For File Data Transfer Application using swing :

Defect ID 101

Defect Name Wrong Time Display

Project Name Digital Clock using Swing

Module Name Time Display

Phase found When you start the application

Defect type Functional defect

Severity Critical

Priority High

Summary Incorrect time displayed

When we start the application the

Description
Time one hour after the current time.

Status Assigned

MET’s Institute of Technology, Polytechnic, Nashik 10

 Actual Methodology Followed

Planned
Sr. Planned Name of Responsible
Details of activity Finish
No. Start Date Team Member
Date
Information Gathering and Topic
1
Finalization
Preparing Project Proposal and
2
Approval
3 Implementing Project

4 Preparing Project Report

5 Presenting Project

6 Submission of Project and Report

5.0 Actual Resources Used

Sr.
Name of Resource/Material Specifications Qty. Remarks
No.
HP-Victus
AMD Ryzen 5 5600H with
1 Computer System 01
Radeon Graphics 3.30
GHz 8.00 GB RAM
2 Editor MS Word 01

6.0 Output of the Micro-Project

7.0 Skill Developed/Learning outcomes of this Micro-Project

1) Apply various Software Testing methods.
2) Prepare test case for different types and levels of testing.
3) Prepare test plan for an application
4) Identify bugs to create defect report of given application .
5) Test software for performance measures using automated testing tools.

8.0 Application of this Micro-Project

o Guaranteed good test coverage.
o Reduced maintenance and software support costs.
o Reusable test cases.
o Confirmation that the software satisfies end-user requirements.
o Improved quality of software and user experience.

Annexure - IV

MET’s Institute of Technology, Polytechnic, Nashik 11

 Micro-Project Evaluation Sheet
Name of Student: Jadhav Atharv Kailas Enrollment No: 2107760011
Name of Programme:Computer Engineering Semester:Fifth
Course Title: Software Testing Code: 22518
Title of the Micro-Project: Test cases & Defect report for Digital Clock using Swing
Course Outcomes Achieved:-
a) Apply various Software Testing methods. Achieved
b) Prepare Test cases for different types and levels of testing. Achieved
c) Prepare Test plan for an application. Achieved
d) Identify bugs to create defect report of given application. Achieved
e) Test softwares for performance measures using automated testing Achieved
tools.

Sr. Characteristics to be Poor Average Good Excellent Sub-

No. assessed (Marks 1-3) (Marks 4-5) (Marks 6-8) (Marks 9-10) Total
(A) Process and Product Assessment (Convert above total marks out of 6 Marks)
1 Relevance to the course
Literature Review/
2
Information Collection
Completion of the Target
3
as per Project Proposal
Analysis of Data and
4
Representation
Quality of
5
Prototype/Model
6 Report Preparation
(B) Individual Presentation/Viva (Convert above total marks out of 4 Marks)
7 Presentation
8 Viva

(A) Process and Product Assessment (B) Individual Presentation/Viva Total Marks
(6 Marks) (4 Marks) (10 Marks)

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

Name and Designation of the Teacher: Prof. Priyanka B. Khairnar

Dated Signature:

MET’s Institute of Technology, Polytechnic, Nashik 12