Test plan For Notepad

Index
1. INTRODUCTION
2. BUSINESS BACKGROUND
3. TEST OBJECTIVES
4. SCOPE
5. TEST TYPES IDENTIFIED
6. PROBLEMS PERCEIVED
7. ARCHITECTURE
8. ENVIRONMENT
9. FUNCTIONALITY
[Link]
[Link]
[Link] TEAM ORGANIZATION
[Link]
[Link] MANAGEMENT
 Test plan

1. Introduction
This test plan is designed to:
 Describe the approach used by tester during testing.
 Organize and implement the test process.
 Describe the testing strategy and steps.

2. Business Background
 The following product is from Microsoft Corporation.
 It is a product from Microsoft windows 10 which is licensed under
Microsoft Software License Terms to the respective user.
 Following project is available by paid genuine windows 10.

3. Test Objectives
The Objective of this assessment was to check and validate the overall
functionality of the software as per the described requirements. This includes
the functions like smooth error free typing and other create, edit, and open,
save, functions.

4. Scope
As per objectives, the initial scope is to check all
Major/minor functionalities of the ‘Notepad’ software.
Inclusions:
a. Firstly for testing will be done after development so the black box testing
will be done.
b. The ‘Notepad’ itself will be used for testing.
c. The latest version of notepad is used.
Exclusions:

a. The testing approach like white box testing will not be used, because the
‘Notepad’ software is already developed.
b. Since some testing can only be done during the development process but
this software is already developed by Microsoft so some testing like Unit
testing, Integration testing, System testing cannot be done.

5. Test type identified

The software is already developed so the testing like smoke testing is
possible on it. The Black Box Testing can be implemented on this
project/product. Reason of black box testing is we cannot interfere with the
internal structure of the product, because it is already developed.
After this still the acceptance testing, usability testing, UI testing,
performance testing can be used for software.

6. Problems Perceived
a. Test cases were challenging to design while unclear functional
specifications.
b. It was difficult to identify all possible inputs in limited testing time.
c. It was difficult to identify all possible inputs in limited amount of time.
As result making test case can be slow and difficult.
d. It was difficult to identify tricky inputs because of the test cases are not
developed based on specification.
e. There might be some errors in some internal structure or any logic which
cannot found now by our black box testing.

7. Architecture
The notepad consist of many functionalities and modules, following is the
architecture of the ‘Notepad’ in block diagram format.
8. Environment
The following project was tested in Windows operating system as it is
made by Microsoft Windows. Except that no other special tools or
framework were used for the testing.

9. Functionality
Sr. no. Scenarios

1. Verify user can open any existing file in notepad.

2. Verify that file formats not permitted by notepad cannot be

loaded.
 3. Verify that file formats not permitted by notepad and don’t
corrupt the application.
4. Verify user can append text to any file and save the file.

5. Verify user can select, copy and paste any text.

6. Verify user can select, cut and paste any text.

7. Verify user can remove text by using backspace and delete

key.

 Risk Identified & Mitigation Planned

-No risk or defects was found after the execution of the test cases.
-Since no risk is found, there is no potential need of testing.

 Test strategy
 Scope:
• Reviewing documents, approving documents and carrying out tests
are done by testers, Pratiksha Jadhav

Test activities Done by Timeline

Analyzing module Pratiksha Jadhav 5 Dec 2022

Creating test case Pratiksha Jadhav 5 Dec 2022
Executing test case Sakshi Shinde 6 Dec 2022
Reviewing test results Sakshi Shinde 6 Dec 2022

 Test approach
• Process of testing:
The first individual module was taken for testing and analyzed. The
module was reviewed and specifications were noted. According to the
main functionality of the module test cases were created and executed.
The output was acknowledged and its status was updated in test cases.
• Roles and responsibilities of each team member
 1. Pratiksha Jadhav: Analyzing the module and the specifications
of the product.
2. Pratiksha Jadhav: Creating the test cases as per the
requirements and the specifications of the modules.
3. Sakshi Shinde: Executing the test cases provided by team
members and getting the results.
4. Sakshi Shinde: Reviewing the test results and setting a status in
test cases either pass or fail.
• Type of testing:
The functionality testing was done on this module.
• Testing approach used:
The analytical approach was used for the testing. No extra special
automation tools were used in testing, whole testing is done manually.

 Test Environment
Windows operating system was used, any version of windows can be
used. For setup, the ‘Notepad’ is used as it is already installed in
windows. There was no need of backup so nothing for backup was used.
 Testing tools:
For testing no special tools were used, only single ‘Notepad’ was
used.
 Risk analysis.
No risk or defects were found.
 Review
All these activities are reviewed and signed off by the team members.
Everything in this module was perfect and fine. No risks, defects or
bugs were found.

10. Security
Sr. no. Scenarios

1. Verify if user can edit text files in notepad after enabling the
‘Read only’ option.
 2. Verify how many users can access files if the file is
accessible for the root user only.
3. Verify if the contents of file are readable after encrypting it.

4. Verify if user can open file in notepad after changing its

visibility and permissions.

 Risk Identified & Mitigation Planned

-No risk or defects was found after the execution of the test cases.
-Since no risk is found, there is no potential need of testing.
 Test strategy
 Scope:
• Reviewing documents, approving documents and carrying out tests
are done by testers, Sami Bhadgaonkar, Maaj Bhadgaonkar and
Atharv Sultanpure.
Test activities Done by Timeline

Analyzing module Pratiksha Jadhav 7 Dec 2022

Creating test case Pratiksha Jadhav 7 Dec 2022
Executing test case Sakshi Shinde 8 Dec 2022
Reviewing test results Sakshi Shinde 8 Dec 2022

 Test approach
• Process of testing:
The first individual module was taken for testing and analyzed. The
module was reviewed and specifications were noted. According to the
main functionality of the module test cases were created and executed.
The output was acknowledged and its status was updated in test cases.
• Roles and responsibilities of each team member
1. Pratiksha Jadhav: Analyzing the module and the specifications
of the product.
2. Pratiksha Jadhav: Creating the test cases as per the
requirements and the specifications of the modules.
 3. Sakshi Shinde: Executing the test cases provided by team
members and getting the results.
4. Sakshi Shinde: Reviewing the test results and setting a status in
test cases either pass or fail.
• Type of testing:
The security testing was done on this module.
• Testing approach used:
The analytical approach was used for the testing. No extra special
automation tools were used in testing, whole testing is done manually.

11. Usability
Sr. no. Scenarios

1. Verify if text typed by user is accurately displayed on

screen.
2. Verify user can remove text by using backspace and delete
key.
3. Verify user can select, copy and paste any text.

4. Verify user can select, cut and paste any text.

5. Verify is user can cut text without selecting.

5. Verify is user can copy text without selecting.

6. Verify if user can undo any activity on the screen by

pressing ‘ctrl+Z’
 Risk Identified & Mitigation Planned
-No risk or defects was found after the execution of the test cases.
-Since no risk is found, there is no potential need of testing.
 Test strategy
 Scope:
• Reviewing documents, approving documents and carrying out tests
are done by testers, Pratiksha Jadhav, Sakshi Shinde
 Test activities Done by Timeline

Analyzing module Pratiksha Jadhav 9 Dec 2022

Creating test case Pratiksha Jadhav 9 Dec 2022
Executing test case Sakshi Shinde 10 Dec 2022
Reviewing test results Sakshi Shinde 10 Dec 2022

 Test approach
• Process of testing:
The first individual module was taken for testing and analyzed. The
module was reviewed and specifications were noted. According to the
main functionality of the module test cases were created and executed.
The output was acknowledged and its status was updated in test cases.
• Roles and responsibilities of each team member
1. Pratiksha Jadhav: Analyzing the module and the specifications
of the product.
2. Pratiksha Jadhav: Creating the test cases as per the
requirements and the specifications of the modules.
3. Sakshi Shinde: Executing the test cases provided by team
members and getting the results.
4. Pratiksha Jadhav: Reviewing the test results and setting a status
in test cases either pass or fail.
• Type of testing:
The Usability testing was done on this module.
• Testing approach used:
The analytical approach was used for the testing. No extra special
automation tools were used in testing, whole testing is done manually.
12. Test team organization
Our test team is of four members,
1. Pratiksha Jadhav
2. Sakshi Shinde
 13. Schedule
The testing should start from day 1 December 2022 to 10 December 2022
by following specified schedule.

Sr. Testing activity Activity done by Task Task

No. started completed
1. Gathering the information Pratiksha Jadhav 1 Dec 2022 2 Dec 2022
and specification of product. Sakshi Shinde

2. Planning the test and test Pratiksha Jadhav 2 Dec 2022 4 Dec 2022
strategy. Sakshi Shinde

3. Test case development Pratiksha Jadhav 4 Dec 2022 6 Dec 2022

Sakshi Shinde

4. Test environment setup Pratiksha Jadhav 6 Dec 2022 6 Dec 2022

Sakshi Shinde

5. Test case execution Pratiksha Jadhav 7 Dec 2022 9 Dec 2022

Sakshi Shinde

6. Results Review Pratiksha Jadhav 9 Dec 2022 10 Dec 2022

Sakshi Shinde

7. Test Closure Pratiksha Jadhav 10 Dec 10 Dec 2022

Sakshi Shinde 2022
14. Configuration Management
Following software and hardware configurations will be used in testing,

Sr. no. Name Quantity Status

1. Computer system, AMD Athlon 1 used

processor, 6gb ddr2 ram (4+2),
64x bit OS.
2. Microsoft Windows 10 1 used
3. Notepad Version 21H2 - used

4. Microsoft Excel 2010 - used

5. Microsoft Word 2010 - used