0% found this document useful (0 votes)
114 views4 pages

pr9 Test Plan

The document outlines a test plan for Microsoft's Notepad application to ensure its functionality, performance and security meet quality standards by testing on various Windows platforms and covering areas like usability, printing and security with roles defined for management and execution.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
114 views4 pages

pr9 Test Plan

The document outlines a test plan for Microsoft's Notepad application to ensure its functionality, performance and security meet quality standards by testing on various Windows platforms and covering areas like usability, printing and security with roles defined for management and execution.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 4

Test Plan for Microsoft's Notepad Application

1. Introduction

This Test Plan outlines the testing strategy for Microsoft's Notepad Application, a basic text editor
widely used on Windows operating systems. The objective is to ensure the application's
functionality, performance, and security meet the specified quality standards.

2. Scope

The scope of this test plan covers testing Microsoft's Notepad Application on Windows platforms,
focusing on core functionalities.

3. In Scope

- Functional Testing
- Usability Testing
- Page setup option testing
- User Interface Testing
- Word wrap option testing
- Printing Functionality Testing

4. Out of Scope

- Advanced text processing features (e.g., macros, advanced search and replace)
- Integration with other Microsoft applications (e.g., Word)

5. Quality Objectives

- Ensure 99.9% application uptime.


- Identify and resolve security vulnerabilities.
- Achieve a basic level of performance for text editing and printing operations. - Ensure a
consistent and user-friendly interface.
6. Roles and Responsibilities

- Test Manager: Overall test strategy, planning, and coordination.


- Test Lead: Test case design and execution.
- Test Analysts: Test case execution, defect reporting, and verification. - Developers: Cooperation
in fixing defects and providing test data.

7. Test Methodology

- Agile methodology (Scrum)


- Manual testing approach (due to Notepad's simplicity)

8. Overview

The testing process will involve multiple test levels, including functional, usability, security, and
performance testing. Defect triage, suspension criteria, and resumption requirements will be defined
to ensure a systematic and efficient testing process.

9. Test Levels

1. Functional Testing
2. Usability Testing
3. Security Testing
4. Performance Testing
10. Bug Triage

Defects will be prioritized and classified as follows:

- Critical: Application crashes, major functionality issues.


- High: Critical functionality issues, and security vulnerabilities.
- Medium: Non-critical functionality issues. - Low: Minor issues, cosmetic defects.

11. Suspension Criteria and Resumption Requirements

Testing may be suspended if:

- Critical defects are discovered.


- Test environment becomes unstable. - Resource constraints arise.

Testing will resume when:

- Critical defects are resolved.


- The environment stabilizes.
- Resources become available.

12. Test Completeness

Testing will be considered complete when:

- All test cases are executed.


- All critical and high-priority defects are resolved.
- Performance and security tests meet the defined criteria.

13. Test Deliverables

- Test Plan
- Test Cases
- Test Execution Reports
- Defect Reports
- Test Summary Report 14. Resource and

Environment Needs

Resources required:

- Testers with Windows expertise


- Windows machines with various versions (e.g., Windows 7, 10, 11) - Test data (text files of
various sizes and formats)

Environment:

- Test environment similar to the Windows production environment


15. Testing Tools

- Microsoft Test Manager (MTM) for test case management


- Bug tracking tool (e.g., JIRA, TFS) for defect management

16. Test Environment

- Operating Systems: Windows 7, Windows 10, Windows 11


- Browsers: Not applicable
- Hardware: Various Windows-compatible machines
- Network: Not applicable

17. Terms/Acronyms

- UI: User Interface


- MTM: Microsoft Test Manager
- TFS: Team Foundation Server

You might also like