Annexure – I

Micro-Project Proposal
Write test cases and Defect report for
Employee Payment System
1.0. Aims/Benefits of the Micro-Project
The microproject aims Employee Payment System application in Advanced Java include
automating payroll processing for efficiency, enhancing accuracy to reduce errors, and
improving data management with a centralized database. It also focuses on facilitating reporting
for better financial analysis and ensuring compliance with legal regulations and tax
requirements.

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 software for performance measures using Not Addressed

automated testing tools.

3.0 Project Methodology

1. Focused on the selection of an appropriate topic for the micro-project.
2. Select the topic i.e. Write test cases and Defect report for Employee Payment System.
3. Detailed study on my topic.
4. Gather All Information based on the topic of the micro-project.
5. Analysis and study of topic in detail.
6. Followed all the above methodologies to successfully complete my micro-project.

4.0 Action Plan

Sr. Planned Planned Name of
Details of activity
No. Start Date Finish Date Responsible
Team Member
Information Gathering and Topic Rushikesh More
1 Finalization
Preparing Project Proposal and Rushikesh More
2
Approval
Rushikesh More
3 Implementing Project
Rushikesh More
4 Preparing Project Report
Rushikesh More
5 Presenting Project
Rushikesh More
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.
1
Computer System Intel core i3, 8GB RAM 01
2
Editor Microsoft Word 2021 01
3
Website GeeksForGeeks 01
4
Other Resources Google, Chrome 01

Name of Member with Roll No. and Enrollment No.

Roll No Enrollment No Name of Member

44 2207760194 Rushikesh MadhukarMore

Approved by

(Prof. P.B. Khairnar )

Name and Signature of Staff

MET’s Institute of Technology, Polytechnic, Nashik 2

 Annexure – II
Micro-Project Report
Write test cases and Defect report for
Employee Patment System
1.0 Rationale
The rationale for developing an Employee Payment System application in Advanced Java lies in the need for
efficient payroll management, which reduces manual errors and saves time. By automating calculations and
record-keeping, the system enhances accuracy and ensures timely payments. It provides a centralized
database, improving data accessibility and security. Additionally, the application supports compliance with
regulatory standards, mitigating legal risks. Ultimately, it contributes to better financial planning and employee
satisfaction.

2.0 Aims/Benefits of the Micro-Project

The microproject aims Employee Payment System application in Advanced Java include
automating payroll processing for efficiency, enhancing accuracy to reduce errors, and improving
data management with a centralized database. It also focuses on facilitating reporting for better
financial analysis and ensuring compliance with legal regulations and tax requirements.

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 software for performance measures using Not Addressed

automated testing tools.

4.0 Literature

Review

What is a Test Case?

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

Parameters of a Test Case:
 Module Name: Subject or title that defines the functionality of the test.
 Test Case Id: A unique identifier assigned to every single condition in a test case.
 Tester Name: The name of the person who would be carrying out the test.
 Test scenario: The test scenario provides a brief description to the tester, as in providing a small
overview to know about what needs to be performed and the small features, and components of
the test.
 Test Case Description: The condition required to be checked for a given software. for eg. Check if
only numbers validation is working or not for an age input box.
 Test Steps: Steps to be performed for the checking of the condition.
 Prerequisite: The conditions required to be fulfilled before the start of the test process.
 Test Priority: As the name suggests gives priority to the test cases that had to be performed first, or
are more important and that could be performed later.
 Test Data: The inputs to be taken while checking for the conditions.
 Test Expected Result: The output which should be expected at the end of the test.
 Actual Result: The output that is displayed at the end.
 Environment Information: The environment in which the test is being performed, such as the
operating system, security information, the software name, software version, etc.
 Status: The status of tests such as pass, fail, NA, etc.
 Comments: Remarks on the test regarding the test for the betterment of the software.

When do we Write Test Cases?

 Before development: Test cases could be written before the actual coding as that would help to
identify the requirement of the product/software and carry out the test later when the
product/software gets developed.
 After development: Test cases are also written directly after coming up with a product/software or
after developing the feature but before the launching of a product/software as needed to test the
working of that particular feature.
 During development: Test cases are sometimes written during the development time, parallelly. So,
whenever a part of the module/software gets developed it gets tested as well.
So, test cases are written in such cases, as test cases help in further development and make sure that
we are meeting all the needed requirements.
Why Write Test Cases?
Test cases are one of the most important aspects of software engineering, as they define how the testing
would be carried out. Test cases are carried out for a very simple reason, to check if the software works or
not. There are many advantages of writing test cases:
 To check whether the software meets customer expectations: Test cases help to check if a
particular module/software is meeting the specified requirement or not.
 To check software consistency with conditions: Test cases determine if a particular
module/software works with a given set of conditions.

MET’s Institute of Technology, Polytechnic, Nashik 4

  Narrow down software updates: Test cases help to narrow down the software needs and required
updates.
 Better test coverage: Test cases help to make sure that all possible scenarios are covered and
documented.
 For consistency in test execution: Test cases help to maintain consistency in test execution. A well-
documented test case helps the tester to just have a look at the test case and start testing the
application.
 Helpful during maintenance: Test cases are detailed which makes them helpful during the
maintenance phase.

Types of Test Cases

 Functionality Test Case: The functionality test case is to determine if the interface of the software
works smoothly with the rest of the system and its users or not. Black box testing is used while checking
for this test case, as we check everything externally and not internally for this test case.
 Unit Test Case: In unit test case is where the individual part or a single unit of the software is tested.
Here each unit/ individual part is tested, and we create a different test case for each unit.
 User Interface Test Case: The UI test or user interface test is when every component of the UI that the
user would come in contact with is tested. It is to test if the UI components requirement made by the
user are fulfilled or not.
 Integration Test Case: Integration testing is when all the units of the software are combined and then
they are tested. It is to check that each component and its units work together without any issues.
 Performance Test Case: The performance test case helps to determine response time as well as the
overall effectiveness of the system/software. It’s to see if the application will handle real-world
expectations.
 Database Test Case: Also known as back-end testing or data testing checks that everything works fine
concerning the database. Testing cases for tables, schema, triggers, etc. are done.
 Security Test Case: The security test case helps to determine that the application restricts actions as
well as permissions wherever necessary. Encryption and authentication are considered as main
objectives of the security test case. The security test case is done to protect and safeguard the data of
the software.
 User Acceptance Test Case: The user acceptance case is prepared by the testing team but the
user/client does the testing and review if they work in the real-world environment.

MET’s Institute of Technology, Polytechnic, Nashik 5

  Test Cases for Employee Payment System: -

MET’s Institute of Technology, Polytechnic, Nashik 6

MET’s Institute of Technology, Polytechnic, Nashik 7
MET’s Institute of Technology, Polytechnic, Nashik 8
MET’s Institute of Technology, Polytechnic, Nashik 9
Test Cases for Employee Payment System: -

MET’s Institute of Technology, Polytechnic, Nashik 1

MET’s Institute of Technology, Polytechnic, Nashik 1
MET’s Institute of Technology, Polytechnic, Nashik 1
MET’s Institute of Technology, Polytechnic, Nashik 1
 1. Open age
calculator
Error message
Check
2. Enter displayed "Non-
calculation 2023-01-01
Application date from ("Non- Gregorian
TC26 with non- (Hebrew Pass
is running non- Gregorian dates not
Gregorian calendar)
Gregorian dates not supported"
dates calendar supported")
3. Click
calculate
1. Open age
calculator Output is
Ensure
formatted "You are
proper Application 2. Enter
TC27 01-01-2000 correctly (e.g., 24 years Pass
formatting is running valid date "You are 24 old."
of output
3. Click years old.")
calculate
1. Open
Validate age age
for users Application calculator
TC28
born on is running 2. Enter
February 29 birth date
of
February 29

MET’s Institute of Technology, Polytechnic, Nashik 1

  Write Test Plan for Age Calculation Application

Introduction

The purpose of this test plan is to outline the testing strategy for the Age Calculation application. This
software tool Calculate Age between Celsius, Fahrenheit, and Kelvin. The goal is to ensure That the
application meets its functional requirements, is user-friendly, and performs accurately under Various
Conditions.

Test Items

 Temperature Converter Application (Web and Mobile versions)

 User Interface (UI)
 API (if applicable)

Features to be tested

1. Functional Requirements
o Conversion between Celsius, Fahrenheit, and Kelvin.
o Input validation (numeric input only).
o Handling of edge cases (e.g., absolute zero).
2. User Interface
o Layout and design consistency across devices.
o Responsiveness of the UI.
3. Performance
o Speed of conversion.
o Load testing for multiple users.
4. Usability
o User experience and accessibility.
o Help and documentation availability.

MET’s Institute of Technology, Polytechnic, Nashik 1

5. Compatibility
o Cross-browser functionality.
o Mobile device compatibility.

Approach

1. Test Types
o Manual Testing
o Automated Testing (for repetitive test cases)
2. Testing Levels
o Unit Testing
o Integration Testing
o System Testing
o User Acceptance Testing (UAT)
3. Test Techniques
o Black-box testing for functional aspects.
o Boundary value analysis for input ranges.
o Exploratory testing for usability aspects.

Test Deliverables

 Test Plan Document

 Test Case Document
 Test Scripts (for automated tests)
 Test Data
 Test Summary Report
 Defect Reports
 UAT Feedback Report

Test Tasks

1. Requirement Analysis
2. Test Case Development
3. Test Environment Setup
4. Execution of Test Cases
5. Defect Reporting and Tracking
6. Test Closure Activities

Environmental Needs

 Development and Test Environments (web server, database, etc.)

 Testing tools (e.g., Selenium for automation, JIRA for tracking)
 Access to multiple devices/browsers for compatibility testing

MET’s Institute of Technology, Polytechnic, Nashik 1

 Responsibilities

 Test Manager: Overall test planning and execution oversight.

 Test Engineers: Test case development, execution, and defect reporting.
 Developers: Fixing reported defects and supporting the testing process.
 Product Owner: Defining acceptance criteria and supporting UAT.

Staffing and Training Needs

 Staffing: 2-3 test engineers, 1 test manager.

 Training: Familiarization with the Age calculation application, testing tools, and any relevant
domain knowledge.

Schedule

 Requirement Analysis: 1 week

 Test Case Development: 1 week
 Environment Setup: 1 week
 Test Execution: 2 weeks
 Defect Resolution: 1 week
 UAT: 1 week
 Test Closure: 1 week

Risks and Contingencies

 Risk: Delays in defect resolution.

o Contingency: Adjust the testing schedule to accommodate additional time for defect fixes.
 Risk: Resource availability.
o Contingency: Cross-train team members to cover for absences.
 Risk: Incomplete requirement documentation.
o Contingency: Schedule regular check-ins with stakeholders to ensure alignment.

MET’s Institute of Technology, Polytechnic, Nashik 1

  Defect Report for Age Calculation Application: -

Sr. Field Description

N
o
1. ID 161
2. Project Name Age Calculation Appliction
3. Severity Critical
4. Priority High
5. Steps to replicate 1. Open the Age calculation application.
2. Enter the Year.
3. Enter the Date of Birth.
4. Enter the Month.
5. Click to calculate the age.
6. Expected Result The application should accurately calculate and display
a person's age based on their birth date, considering
the
current date.
7. Actual Result The application returns an incorrect age if the birth date is
not properly validated or if the current date is not
accurately retrieved.
8. Reported By P.B. Khairnar
9. Assigned to Rushikesh More
10. Date & Time 15/08/2024

5.0. Actual Methodology

1. Focused on the selection of an appropriate topic for the micro-project.
2.Select the topic i.e. Write test cases and Defect report for Age
Calculation Application.
3. Detailed study on my topic.
4. Gather All Information based on the topic of the micro-project.
5. Analysis and study of topic in detail.
6. Following all the above methodologies to successfully complete my micro-project.

Sr. Planned Planned Name of

Details of activity
No. Start Date Finish Date Responsible
Team Member
Information Gathering and Topic Rushikesh More
1 Finalization
Preparing Project Proposal and Rushikesh More
2 Approval
Rushikesh More
3 Implementing Project
Rushikesh More
4 Preparing Project Report
Rushikesh More
5 Presenting Project
Rushikesh More
6 Submission of Project and Report

MET’s Institute of Technology, Polytechnic, Nashik 1

 6.0. Actual Resources Used
Sr.
Name of Resource/Material Specifications Qty. Remarks
No.
1
Computer System Intel core i3, 8GB RAM 01
2
Editor Microsoft Word 2021 01
3
Website GeeksForGeeks 01
4
Other Resources Google, Chrome 01

7. 0. Skill Developed/Learning outcomes of this Micro-Project: -

1. Understanding Requirements: learn to analyze the application’s requirements and determine
what needs to be tested? This includes understanding conversion formulas and boundaries.
2. Problem-Solving: Identifying potential issues or edge cases and figuring out how to test for
them enhances your problem-solving abilities.

8. 0. Application of this Micro-Project: -

1. General Software Testing
2. Quality Assurance (QA) Practices
3. User Experience (UX) and Usability
4. Performance and Reliability Testing

MET’s Institute of Technology, Polytechnic, Nashik 13

 Annexure - IV
Micro-Project Evaluation Sheet
Name of Student: Dongare Ganesh Vasant Enrollment No:2207760158
Name of Programme: Computer Engineering Semester: Fifth
Course Title: Software Testing Code: 22518
Title of the Micro-Project: Write test cases & Defect Report for Age Calculation Application.
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 software for performance measures using Not Achieved

automated testing 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
3
Target
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. P.B. Khairnar

Dated Signature:

MET’s Institute of Technology, Polytechnic, Nashik 14

MET’s Institute of Technology, Polytechnic, Nashik 15