TEST PLAN

TODOIST

ChangeLog

Version Change Date By Description

1.0 21-Sep-2020 Ankit Kumar Created the Test plan document

with the necessary details
1 INTRODUCTION........................................................................................................................................2
1.1 SCOPE.................................................................................................................................................2
1.1.1 In Scope....................................................................................................................................2
1.1.2 Out of Scope.............................................................................................................................2
1.2 QUALITY OBJECTIVE........................................................................................................................ 2
1.3 ROLES AND RESPONSIBILITIES............................................................................................................. 2
2 TEST METHODOLOGY...............................................................................................................................3
2.1 OVERVIEW.................................................................................................................................... 3
2.2 TEST LEVELS.................................................................................................................................. 3
2.3 BUG TRIAGE.................................................................................................................................. 3
2.4 SUSPENSION CRITERIA AND RESUMPTION REQUIREMENTS.........................................................................3
2.5 TEST COMPLETENESS....................................................................................................................... 4
3 TEST DELIVERABLES.................................................................................................................................4

4 RESOURCE & ENVIRONMENT NEEDS......................................................................................................4

4.1 TESTING TOOLS.............................................................................................................................. 4
4.2 TEST ENVIRONMENT........................................................................................................................ 4
5 Terms/Acronyms......................................................................................................................................5

1
1 Introduction
Brief introduction of the test strategies, process, workflow and methodologies used for the project

1.1 Scope

1.1.1 In Scope

 Scope defines the features, functional or non-functional requirements of the software that will
be tested
 Test such as Addition, update, delete, completion of tasks
 Syncronization of tasks among Todoista nd google calendar
 Addition, update and delete of the Projects

1.1.2 Out of Scope

 Testing the tasks sync with other tools similar to Google calendar.
 Testing on the windows 10 application

1.2 Quality Objective

 Ensure the Todoist conforms to functional and non-functional requirements regarding the
syncing to google calendar
 Bugs/issues are identified and fixed before go live
 To make sure critical defects are removed before the next levels of testing can start.

1.3 Roles and Responsibilities

Detail description of the Roles and responsibilities of different team members like
 QA Analyst – Analyze the functional requirement, prepare test scenarios, test cases, execute test cases
and reports
 Test Manager – Review and approve the test scenario documents and reports
 Developers – Defect Triage and fixing
 Installation Team - Preparation of the environment and facilitate the equipment and hardware support

2
2 Test Methodology
2.1 Overview

Iterative Model will be followed for this testing. Because as soon as iteration is completed, the entire
system is subjected to testing. Feedback from testing is immediately available and is incorporated in the
next cycle. The testing time required in successive iteration will be reduced based on the experience
gained from past iterations.

2.2 Test Levels

Test Levels define the Types of Testing to be executed on the Application Under Test (AUT). The
Testing Levels primarily depends on the scope of the project, time and budget constraints.

 Sanity
PURPOSE: The purpose of this test is to make sure critical defects are removed before the next
levels of testing can start.
SCOPE: First level navigation, dealer and admin modules
TESTERS: Testing team.
METHOD: Sanity is carried out in the application without any test scripts
and documentation to ensure the application is ready for the Functional Testing

 Functional Test
PURPOSE: Functional testing will be performed to check the functions of application. The
functional testing is carried out by feeding the input and validates the output from the
application.
Scope: The below excel sheet details about the scope of Functional test. Note: The scope is
high level due to changes in the requirement.
Functional Test will be composed for Manual as well as Automation Testing

 API Testing
PURPOSE: To test API and make sure critical defects are removed related to the core
functionalities
SCOPE: Add todos, Rename and update todo and Complete
TESTERS: Testing team.
METHOD: API testing will be done using the Postman tool by sending the request and verify the
responses

 Automation Testing

3
 PURPOSE: To test the major features of the the application and make sure critical defects are
removed related to the core
SCOPE: Add todos, Rename and update todo and Complete
TESTERS: Testing team.
METHOD: Automation testing will be carried out using Selenium webdriver

2.3 Bug Triage

The goal of the triage is to

 To define the type of resolution for each bug

 To prioritize bugs and determine a schedule for all “To Be Fixed Bugs’.

2.4 Suspension Criteria and Resumption Requirements

Suspension criteria define the criteria to be used to suspend all or part of the testing procedure while
Resumption criteria determine when testing can resume after it has been suspended

2.5 Test Completeness

Criterias to check Test Completeness would be
 100% test coverage
 All API cases, Manual & Automated Test cases executed
 All open bugs are fixed or will be fixed in next release

3 Test Deliverables

S. No. Deliverable Name Author Reviewer

Project Manager/ Business
1 Test Plan Test Lead Analyst’s
Functional Test
2 Scenarios and Cases Test Team Business Analyst’s Sign off
3 Logging Defects Test Team Test Lead/ Programming Lead
Daily/weekly status Test Team/ Test
4 report Lead Test Lead/ Project Manager
5 Test Closure report Test Lead Project Manager

4
4 Resource & Environment Needs

4.1 Testing Tools

 Requirements Tracking Tool – QC / qTest / JIRA

 Bug Tracking Tool – QC / Test Rail / JIRA
 Automation Tools – Selenium Web-driver, Log4j, TestNG
 API Testing Tool - Postman

4.2 Test Environment

Following software’s are required in addition to client-specific software.

 Windows 8 and above

 Office 2013 and above
 MS Exchange, etc.

4.3 Test Effort Estimate

Document will list out all the activities that have to be performed by the QA team and estimates
how many man-hours each activity is going to take

5 Risks
 Some test scenarios are not redily automable such as automating the Google Claendar. As
google account is having automation detection mechanism which restrict user to login.
 Scenarios related to the notification triggering on mobile are not automable.
 Same google account should be used to sign up to Todoist else the testing will not be conclusive

5
6 Terms/Acronyms
Make a mention of any terms or acronyms used in the project

TERM/ACRONYM DEFINITION
API Application Program Interface
AUT Application Under Test