Maharashtra State Board of Technical Education

Mumbai. (M.S.)

MICRO PROJECT

On

“TEST PLAN AND TEST CASE FOR

NOTEPAD”
Submitted by
AKSHAYA PAWAR

G.S. Mandal’s

Department of Computer Engineering

Marathwada Institute of Technology,
Polytechnic, Aurangabad.

Academic Year: - 2024-2025

MAHARASHTRA STATE
BOARD OF TECHNICAL EDUCATION
 CERTIFICATE
This is to certify that : -
Enrollment Exam
Name of Student No. Seat No.
14 AKSHAYA PAWAR 2200660141

have successfully completed “TEST PLAN AND TEST CASE FOR

NOTEPAD” Micro-project for the subject Software Testing as in the enclosed
‘Portfolio’ during his tenure of Completing the Diploma in Computer
Engineering CO5I(A) in Academic Year 2024-2025 from M.I.T. Polytechnic,
Aurangabad with Institute Code 0066.

Date:

Prof.A. S. Nagrik Prof. A. S. Nagrik

Guide H.O.D.

Principal
Marathwada Institute of Technology,
Polytechnic, Aurangabad
 INDEX
Annexure-IV Micro Project Teacher Evaluation Sheet

Annexure-I A “Format for Micro-Project Proposal”

1.0 Aim/Benefits of Micro Project

2.0 Course Outcomes Addressed

3.0 Proposed Methodology

4.0 Action Plan

5.0 Resources required

Annexure-II A “Format for Micro-Project Report”

1.0 Rational

2.0 Aim/Benefits of Micro Project:

3.0 Course Outcomes Achieved

4.0 Literature Review

5.0 Actual Methodology Followed

6.0 Actual Resources Used

7.0 Outputs of the micro projects

8.0Skill Developed/Learning outcome of this micro project

9.0 Applications of this micro project

 Annexure-IV

Micro Project

Name of Programme: Diploma in Computer Engineering Semester : - 5th

Perform Course Title : SOFTWARE TESTING Code: 22413
Title of Micro Project : TEST PLAN AND TEST CASE FOR
NOTEPAD

Course Outcomes Achieved:

a) Prepare test cases for different types and levels of testing.

b) Prepare test plan for an application.

Process and Individual Total

Roll Enrollment Exam Product Presentation/ Marks
Name of Student
No. No. Seat No. Assessment Viva (10)
(06) (04)
14 AKSHAYA PAWAR 2200660141

Comments / Suggestions about work:

___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________
___________________________________________________________________________________

Signature of Teacher :__________________________

Name of the Teacher : Prof A.S.Nagrik

 Annexure-I

Micro-Project Proposal

Title of Micro-Project : TEST PLAN AND TEST CASE FOR

NOTEPAD

Aim/Benefits of Micro Project

The primary aim of a test case for Notepad is to ensure that the application performs as
expected across a variety of scenarios, covering basic functionalities like opening, editing,
saving, and printing text files. A test plan for Notepad outlines the overall testing strategy,
specifying the scope, objectives, resources, schedule, and types of testing.
2.0 Course Outcomes Addressed
a) Prepare test cases for different types and levels of testing.
b) Prepare test plan for an application.

3.0 Proposed Methodology

1. Firstly I selected the topic for micro project. Then I started research on my
micro project topic and have gone through Software Testing syllabus, books,
videos and websites.

2.Secondly information collected from books:

We collected information from various books listed as,
b. Software Engineering Using Technical publication
c. Software Engineering Prefer by Technical publication.
d. Software Engineering Prefer by Nirali Publication.
3.Information collected from web resources:
We collected information’s from various sites
a. www.google.com
b. www.geeksforgeeks.com
c. www.youtube.com
4.Designing use case diagram done by:
1. Akshaya Pawar
5. Preparation of report done by:
Akshaya Pawar
4.0 Action Plan
Sr. Details of Activity Planned Planned Name of
No Start Date Finish Date Responsible
Team Members

5.0 Resources required (major resources such as raw material, some machining
facility, software etc.)
Sr. Name of Resource/Material Specification Qty. Remarks
No
1. Laptop ASUS 1

2. Software Testing Textbook 5th SEM 1

Names of Team Members with Roll No. : -

Roll No. Name of Student

14 AKSHAYA PAWAR

Annexure-II
Micro-Project Report
(Format for Micro-Project Report minimum 4 pages)
Title of Micro-Project : TEST PLAN AND TEST CASE FOR
NOTEPAD

1.0 Rationale (Importance of the project, in about 30 to 50 words. This is a modified

version of the earlier one written after the work)

2.0 Aim/Benefits of Micro Project:

The primary aim of a test case for Notepad is to ensure that the application performs as
expected across a variety of scenarios, covering basic functionalities like opening, editing,
saving, and printing text files. A test plan for Notepad outlines the overall testing strategy,
specifying the scope, objectives, resources, schedule, and types of testing.
3.0 Course Outcomes Achieved (Add to the earlier list is more Cos are addressed)

a) Prepare test cases for different types and levels of

testing.
b) Prepare test plan for an application.

4.0 Literature Review : -

Test cases for notepad are asked in many testing interviews. Depending on
your level of experience, you’ll be asked feature specific test cases for
notepad. Depending on the operating system you use, the notepad
application will have different features and some additional or less
features.

Let’s assume the noteapp application that we are going to test here is
windows based “Notepad”. It has following options: create new file, save
the file, save file with different extension, word wrap, copy, paste, delete
and exit.

Test cases for notepad are asked in many testing interviews. Depending on
your level of experience, you’ll be asked feature specific test cases for
notepad. Depending on the operating system you use, the notepad
application will have different features and some additional or less
features.

Let’s assume the noteapp application that we are going to test here is
windows based “Notepad”. It has following options: create new file, save
the file, save file with different extension, word wrap, copy, paste, delete
and exit.

Generic Test Cases for Notepad

 Check if the data is saved after writing to the file.

 Check the functionality for the save as file.
 Check if the notepad allows same file name in the same file path.
 Check if the edits to the file are saved.
  Check the functionality of the close, maximize and minimize buttons.
 Check if the window for notepad can be re-sized.
 Check the default size of the notepad is based on last saved window size.
 Check if the clearing system cache has any difference in the size of the
notepad window after you open any file.

These were some of the common test cases but if you want to go
application specific test cases then you have to check each item in menu.

Test Case for New File Option

 Create a new file using CTRL+N hotkey.

 Create a new file using File> New menu option.
 Create a new file using Windows Icon+ Menu > Accessories > Notepad.

Test Case for Undo Option

 Click on Undo option in Edit Menu.

 Use CTRL+Z hotkey to undo the text changes.

Test Case for Cut Option

 Click on Cut option in Edit Menu

 Use CTRL+C hotkey to cut the text selected.
 Use cut option in edit menu without selecting any text.
 Use CTRL+C hotkey without selecting text.

Test Case for Paste Option

 Click on Paste option in Edit Menu

 Use CTRL+V hotkey to paste the text selected.
 Use Paste option in edit menu without selecting any text.
 Use CTRL+V hotkey without selecting text or area.

Test Cases for Save Option

 Save empty file.

 Save file with maximum text content.
 Save file with less than the maximum allowed to store in a file.
 Save the file on the desktop.
 Save the file with same file name that to of earlier saved file and choose
the same file path.
 Save the file with word wrapped and close it to open again after few
seconds.
 Save the file without word wrapped and close it to open again after few
seconds.
 Save the file from file menu.
 Save the file using CTRL+S hotkey.
 Save the file with ASCII character set.
 Save the file with UTF character set.
 Save the file with multiple enconding character set.
 Save the file with unicode endian character set.

Test Case for Exit Option

  Exit the application by clicking file>exit menu.
 Exit the application by using CTRL+X hotkey menu.
 Exit the application by using ALT+F4 system hotkey.

Some of the other common test cases for cross platform notepad
applications :

 Check if the find option exist for the notepad.

 Check if the navigation within text is possible with the arrow keys on
keypad.
 Check the default position of the cursor (before, after the saving file).
 Check if the notepad has find and replace functionality.

In the world of software testing, a Test Plan is like a well-constructed blueprint for a building; it

provides structure, direction, and clarity. For software testers, especially beginners, creating a

solid Test Plan is essential. This article is designed to be your guide, specifically tailored for

beginners, as we delve into the intricacies of Test Plans.

A Test Plan is a detailed document that outlines the scope, approach, resources, and schedule of

software testing. It’s a roadmap that ensures your testing activities are organized, efficient, and

effective. Below is a template for a common Test Plan.

1. Test Plan Identifier

 Unique ID for the test plan document (e.g., TP-Notepad-001).

2. Introduction

 Purpose: Describe the overall goal of the test plan. For example, "The purpose of this test plan
is to outline the testing strategy for the Notepad application, ensuring all functionalities work
as expected."
 Scope: Outline what features and functionalities of Notepad will be tested (e.g., file
operations, text formatting, search functionality, etc.).
 Objective: Ensure that Notepad performs consistently across all specified environments and
meets the user requirements.

3. Test Items

 List of Features/Components to be Tested:

o File operations (Create, Save, Save As, Open, etc.)
o Text editing (Cut, Copy, Paste, Undo, Redo, etc.)
o Search and replace functionality
o Format options (Word wrap, Font change)
o Printing
o Help and About dialogs
o Edge cases (e.g., opening large files, unsupported formats)
4. Features Not to Be Tested

 Specify any features or areas that are out of scope for testing. For example:
o External file type support beyond text files.
o Performance stress testing (if not included in the scope).

5. Test Strategy

 Testing Types:
o Functional Testing: To validate the main functionalities (file operations, text editing,
etc.).
o User Interface (UI) Testing: Ensure the UI is user-friendly, and all buttons, menus, and
icons work as expected.
o Usability Testing: To ensure ease of use and intuitive design.
o Regression Testing: To ensure that any new changes or fixes do not break existing
functionality.
o Performance Testing: To check how the application handles large files or multiple
tasks simultaneously.
 Testing Levels:
o Unit testing
o Integration testing
o System testing
o Acceptance testing

6. Test Approach

 Test Design Techniques: Specify how test cases will be derived, such as boundary value
analysis, equivalence partitioning, etc.
 Test Case Execution: Explain how test cases will be executed, in manual or automated modes.
 Entry Criteria: List the conditions that must be met before testing starts (e.g., a stable build of
Notepad is delivered).
 Exit Criteria: Conditions for ending the testing phase, such as:
o All critical test cases are executed.
o No high-priority defects remain open.

7. Test Environment

 Hardware Requirements: Specify the system configurations required for testing (e.g.,
minimum RAM, processor speed).
 Software Requirements: Operating system versions (Windows 10/11), any other software
dependencies (e.g., text editors or third-party libraries).
 Test Data: Indicate how test data will be prepared, such as sample text files for editing,
opening, and saving.

8. Test Schedule

 Provide a detailed timeline, including:

o Test plan review and approval dates.
o Test case design and review schedule.
o Test execution start and end dates.
 o Time allotted for defect resolution and re-testing.

9. Resource Planning

 Roles and Responsibilities:

o Test Lead: Responsible for overall test planning and monitoring.
o Testers: Responsible for designing and executing test cases.
o Developers: Responsible for fixing defects found during testing.
o Tools: List any tools being used (e.g., Jira for bug tracking, Selenium for automated
tests).

10. Risk and Contingencies

 Risks: List any known risks to the testing process (e.g., late delivery of builds, resource
constraints, or incomplete requirements).
 Mitigation Plans: Outline how these risks will be managed (e.g., resource reallocation, test
automation to save time).

11. Test Deliverables

 Documents to Be Produced:
o Test Plan
o Test Cases
o Test Scripts (if automated)
o Test Summary Reports
o Defect Reports

12. Approvals

 Include space for sign-off from key stakeholders, such as:

o Project Manager
o Test Manager
o Development Lead
o Quality Assurance Lead

This structure ensures that all aspects of the testing process are planned in advance, making it
easier to identify issues and track progress as the Notepad project moves through the testing
phase.

5.0 Actual Methodology Followed (Write stepwise work done, data collected and its
analysis (if any). The contribution of individual members may also be noted.)

1. Firstly Shravani Kulkarni and Akshaya Pawar decided to become team

members for our micro project. Then we selected our topic for micro project
hospital management system. Then we have gone through Software Engineering
syllabus and decided to work on use case diagram on hospital management
system.

2.Secondly information collected from books:

We collected information from various books listed as,
e. Software Engineering Using Technical publication
f. Software Engineering Prefer by Technical publication.
g. Software Engineering Prefer by Nirali Publication.

3.Information collected from web resources:

We collected information’s from various sites
a. www.google.com
b. www.geeksforgeeks.com
c. www.youtube.com

4.Designing use case diagram done by:

2. Shravani Kulkarni
3. Akshaya Pawar

5.Arranging of this work in appropriate manner and cross checking of the same
work was done

6. Preparation of report done by:

Akshaya Pawar
Shravani Kulkarni
This how we prepared our microproject in 6 weeks.

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

Sr. Name of Resource/Material Specification Qty. Remarks

No
1. LAPTOP ASUS 1

2. Software Engineering 4th SEM 1

Textbook

7.0 Outputs of the micro projects (Drawings of the prototype, drawing of survey,
Presentation of collected data, findings etc.)

8.0 Skill Developed/Learning outcome of this micro project

The learning outcome of creating an HMS (Hospital Management
System) use case diagram could include the following:

1. Understanding the different actors and their roles within the

hospital management system.
2. Identifying the various use cases or functionalities that the
system should provide.
3. Analyzing the interactions between the actors and the
system, and how they are linked.
4. Recognizing the different scenarios or situations in which the
system is used and how it responds.
5. Mapping the flow of information and actions within the
system to ensure efficient management of hospital processes.
6. Identifying potential improvements or optimizations for the
system by analyzing the use case relationships.
7. Gaining a comprehensive understanding of the overall
structure and functionality of the hospital management
system.
8. Enhancing communication and collaboration among
stakeholders by visually representing the system's
requirements and functionalities.
9. Facilitating the identification of potential risks or issues in the
system's design or implementation.
10. Providing a foundation for further system design and
development activities.
9.0 Applications of this micro project : -

Hospital Management System: A hospital management system

is used to manage various operations in a hospital, such as
patient registration, appointment scheduling, inventory
management, billing, and report generation. A use case diagram
can be used to represent the different actors involved, such as
doctors, nurses, administrators, and patients, and the various
tasks they perform within the system.

********