Test plan

Calculator 2.0

General information
Customer Calculator 2.0
Created by (Author) Dubouskaya Darya
Preparation date 12.09.2023
Version of document 1.0
Status In progress

Revision history
Version Description Author Date Approved by
Author Date

1
Summary
1. Introduction ............................................................................................................................ 3
2. Background ............................................................................................................................ 3
3. Purpose.................................................................................................................................. 3
4. Scope ...................................................................................................................................... 3
4.1 In-Scope ........................................................................................................................... 3
4.2 Out-of-scope .................................................................................................................... 3
5. Work plan............................................................................................................................... 4
6. Test strategy ........................................................................................................................... 4
6.1 Bug Reports ..................................................................................................................... 5
7. Recourses ............................................................................................................................... 5
8. The criteria of quality............................................................................................................. 6
9. Risks....................................................................................................................................... 6
10. Test documentation .............................................................................................................. 6
11. Responsibilities of test team members ................................................................................. 7

2
 1. Introduction
This document describes the methods and procedures that will be used by the X
team in the functional and non-functional testing process of the ‘Calculator’ 2.0
application developed for the company Y employees. It is meant to be used as a
manual during testing works. It describes the procedure of the testing process.
The test plan is intended for project managers, product developers, and QA
engineers. The testing activities aim to check the functions and features of a
product developed for OS Windows 7-10 latest builds.

2. Background
‘Calculator’ application is developed for employees of company ‘Y’. Suppose
that they will use it in their daily work to make all calculations. The application
will be installed on all corporate computers.d

3. Purpose
This Test Plan document for the ‘Calculator’ 2.0 supports the following
objectives:
● Identify existing project information and software components to be tested.
● Recommendation and description of the testing strategies to be employed.
● Identify required resources and provide a test effort estimate
● List the test project deliverable elements.
The results of test execution will be sent to the customer as reports. All found
bugs will be tracked using the Jira app.

4. Scope

4.1 In-Scope
1. Downloading of the application (Windows 7-10 last builds);
2. Launching the application (Windows 7-10 last builds);
3. System specification (App language, size, format);
4. Functional specification for engineer and simple modes(Work of all buttons;
input from physical keyboard, work of all mathematical functions for negative,
positive, decimal numbers; switch between modes);
5. GUI checking (Keyboard layout, I/O field, user guide);
6. Usability checking
Detailed information may be found in the ‘Calculator requirements’ document
(link)

4.2 Out-of-scope
1. Work application at other OS and other builds of Windows;

3
2. Full-screen mode;
3. ‘Calculator’ V1.0;
4. Automated testing;
5. System specifications.

5. Work plan
1. Test plan preparation
2. Test plan approval
3. Test Cases preparation
4. Functional and non-functional testing
5. Bugs reporting
6. Checking that bugs were fixed (retesting)
7. Final testing
8. Final report preparation

6. Test strategy

The objective of functional testing is to make sure that the whole

‘Calculator 2.0 application works according to the requirements (link), and that
no significant errors appear in the application.
Execute each use case, use-case flow, or function, using valid and invalid
data, to verify the following: ● The expected results occur when valid data is
used.
● The appropriate error or warning messages are
displayed when invalid data is used.
● Each rule is properly applied.

Entry criteria:
o The application construction is completed.
o The test engineers are dedicated.
o Necessary devices, instruments, and other equipment are acquired.
o The test environment is prepared, and the application is released to
the test environment.

Completion criteria:
o All the planned tests are performed.
o There are no blocker errors.
o 100% of the errors of high priority and severity are fixed.
o The test results are evaluated, discussed, and approved.
o Final requirements coverage by tests must be 90% or more.

4
 Suspension criteria:
If team members report that 40% of test cases failed or at least one blocker, the
testing would be suspended before developers fix all failed cases.

Test method:
• Manual testing.
The main testing types that would be executed:
• Functional Testing (Smoke, Critical path, Extended)
• UI Testing
• Usability Testing
• Regression testing
• Retesting
6.1 Bug reports

Bug reports are created to provide the development team and project managers
with exhaustive information about the defects discovered. They must help
determine the causes of the errors and correct them.
Each report provides the following information about the defect:
• Identification number;
• Number of requirements connected with the bug;
• summary, which is a short description of the problem;
• location of the defect in the software product;
• steps to reproduce the error;
• severity of the defect;
• additional information about the defect in the form of attached screenshots
or video records.
7. Recourses
Tools:
Bug tracking system Jira
Test cases Azure
Screenshots and video capture Snagit

Test documentation: Google Drive> Calculator 2.0.

Devices: Laptop Xiaomi (Windows 10(Home));
Desktop computer (Windows 7, 10).

5
 Virtual machine ‘Docer’ where the app’s work may be checked on OS
Windows 7-10 latest builds.
Time: 10 working days;
Budget: According to agreements.

8. The criteria of quality

The product should operate according to the requirements and the
functional specifications. The product should not contain critical and blocking
defects in the final version of the project.
• Full access to the cloud storage is provided to the team;
• Requirements editing is finished and blocked;
• Software is available for testing;
• The deadlines are met;
• There are no last-moment failures and agreements.

9. Risks
• changes and modifications of the software product that were not planned and
discussed with the test team beforehand;
• changes in the software requirements that were not discussed with the test
team beforehand;
• delays in correcting/fixing errors;
• delays in delivering new builds to the test team;
• absence of members of the test team.
10. Test documentation
Test documentation: Google Drive> Calculator 2.0.
Type Responsible Frequency Method of delivery
person
Test plan QA lead Once testing starts Test_plan_calculator
Google Drive
Test cases QA lead, testers Before testing Jira app(..)
starts, but may be
modified during
testing
Bug report QA lead, testers For each found bug Azure app(..)
Final test QA lead After finishing Test_report_Calcilator
report testing Google Drive

6
 11. Responsibilities of test team members
Role Responsibilities
Project manager Managing the whole testing process. Providing all the
needed resources for the testing activities.
QA lead Managing the QA team from a technical perspective.
Analyzing the tasks and distributing them between team
members.
Communicating with the client team and discussing all
issues, providing
recommendations before an update or release.
Experience in participation in different SDLC models like
Agile, Scrum, Kanban,
Sequential, Iterative, and Incremental.
Creating test documentation, including test cases, test
plans, etc.
Proposing best practices and tools for a project.
Tester 1 QA process/logging found errors in the approved bug-
tracking system.
Tester 2 QA process/logging found errors in the approved bug-
tracking system.

Testing schedule
Task Name 12.09- 14.09 15.09 18.09- 21.09- 25.09 26.09
13.09 20.09 22.09
Test plan QA lead, tester
preparation
Test plan Project
approval manager

Test Cases tester 1, tester 2

preparation
Functional tester 1,
and non- tester 2
functional
testing
Bugs tester 1,
reporting tester 2

Checking tester 1,
that bugs tester 2,

7
were fixed
(retesting)
Final testing Tester 1,2
QA lead
Final report QA lead
preparation