● Title: Create a small web-based application by selecting relevant system environments/platforms and

programming languages. Narrate a concise Test Plan consisting of features to be tested and bug taxonomy.
Narrate scripts in order to perform regression tests. Identify the bugs using Selenium WebDriver and IDE and
generate test reports encompassing exploratory testing.

● Problem Definition: The goal of this project is to create a Todo List Application that allows users to manage
tasks and organize them efficiently. The application will also support role-based access control (admin, user).
The project involves automating tests using Selenium WebDriver to ensure the correct functioning of user
authentication, task creation, task management, and filtering tasks.

● Prepared By:

Shubham Kumar, BC238, BE COMP

Vishwatej Khot, BC234, BE COMP

● Prerequisite:
Knowledge of Python programming and Node.js, Basics of Selenium WebDriver and Selenium IDE

● Software Requirements:
○ Node.js
○ Python
○ MongoDB
○ Selenium Webdriver
○ VsCode

● Hardware Requirement:
○ Processor: Intel i5 or higher
○ RAM: 4 GB minimum
○ Internet Connection for web application deployment and testing

● Theory :
The Todo List Application is designed to help users manage tasks effectively, allowing them to create, edit,
delete, and filter tasks. The application also supports user authentication and role-based access, with admin
users being able to view other users’ progress. Automated testing will be performed using Selenium to ensure
the reliability of the system.
Testing Tool: Selenium

Selenium is a free (open-source) automated testing suite for web applications across different browsers
and platforms. It is quite similar to HP Quick Test Pro (QTP now UFT) only that Selenium focuses on
automating web-based applications. Testing done using the Selenium tool is usually referred as
Selenium Testing. Selenium is not just a single tool but a suite of software, each catering to different
testing needs of an organization. It has four components.
● Selenium Integrated Development Environment(IDE)
● Selenium Remote Control (RC)
● Web Driver
● Selenium Grid

Selenium IDE (Integrated Development Environment) is the simplest tool in the Selenium Suite. It is a
Firefox add-on that creates tests very quickly through its record- and-playback functionality. This feature
is similar to that of QTP. It is effortless to install and easy to learn. Because of its simplicity, Selenium
IDE should only be used as a prototyping tool, not an overall solution for developing and maintaining
complex test suites.

Though you will be able to use Selenium IDE without prior knowledge in programming, you should at
least be familiar with HTML, JavaScript, and the DOM (Document Object Model) to utilize this tool to its
full potential. Knowledge of JavaScript will be required when we get to the section about the Selenese
command "run Script."

Selenium IDE supports auto-complete mode when creating tests. This feature serves two purposes: It helps
the tester to enter commands more quickly.
It restricts the user from entering invalid commands.

The way to set up a Selenium 2.0 Java project is to use Maven. Maven will download the java bindings
(the Selenium 2.0 java client library) and all its dependencies, and will create the project for you, using a
maven pom.xml (project configuration) file. Once done, you can import the maven project into your
preferred IDE, IntelliJ IDEA or Eclipse.
Advantages of Selenium
i) It is an Open source Software.
ii) It supports various Operating environments (Windows, Linux, Mac etc…)
iii) It supports various browsers (IE, Mozilla Firefox, Chrome, safari, Opera etc…)
iv) It supports various programming environments (Java, Perl, Python, Ruby and PHP)
v) It supports parallel Test execution.
vi) It uses less Hardware resources.

Disadvantages of Selenium
i) It supports Web based Applications only.
ii) No reliable support from anybody.
iii) No centralized maintenance of Elements/objects
iv) Difficult to setup environment.
v) Difficult to use.
vi) Limited support for Image based testing.
vii) New features may not work properly.
viii) No other tool integration for test management & No built in Reporting facility

● Test Plan
INTRODUCTION
The purpose of the test plan is to outline the approach, scope, and methodology of testing the Todo List
Application. The testing will focus on user authentication, task creation, and task filtering
functionalities. Testing will be automated using Selenium WebDriver, and test reports will be generated
for each test case.

1 TEST STRATEGY
1.1 Scope of Testing
● Features to be tested: User login, task creation, task management, task filtering, user logout.
● Features not to be tested: External API calls, and system performance.
 1.1.1 Features to be tested

1.1.2 Feature not to be tested

● Browser Compatibility for Legacy Versions - Testing the platform on outdated browser versions
(e.g., Internet Explorer 10 or earlier) will not be included, as the focus is on modern, supported
browsers.
● Performance Under Extreme Load - The project is designed for small to medium-sized startups,
so testing for scalability with thousands of simultaneous users is outside the scope of this project.
● Integration with Third-Party Payment Systems - The platform does not involve any financial
transactions or payment gateways, so no testing will be performed for integration with payment
systems.
● Offline Functionality - Since this is a web-based application, there will be no testing for features
related to offline access or offline task management.
● Mobile App-Specific Testing - Although the platform is responsive, specific testing for mobile
app versions (native apps for iOS/Android) is not in the scope. Only web browser responsiveness
on mobile devices will be tested.

1.2 Test Type

In the project CRUD Todo List, there are 3 types of testing that should be conducted.
- Integration Testing (Individual software modules are combined and tested as a group)
- System Testing: Conducted on a complete, integrated system to evaluate the
system's compliance with its specified requirements
- Unit Testing- Testing of each module and component in the system
1.3 Risk and Issues

1.4 Test Logistics

1.4.1 Who will test?
Members of the team.
1.4.2 When will the test occur?
The tester will start the test execution when all the following inputs are ready
- Software is available for testing
- Test Specification is created
- Test Environment is built
- Enough human resources for testing

2 TEST OBJECTIVE
The test object in this project is the Todo List Application, designed to evaluate the core functionalities
of user authentication, task management, and role-based access control. The tests will verify if users can
securely sign up, log in, and manage their tasks, ensuring that all task-related actions, such as creating,
editing, deleting, and filtering tasks, work as expected. Additionally, the tests will confirm the correct
behavior of features like admin dashboards, task completion tracking, and role-specific access. By
validating these functionalities, the tests ensure the application meets both user expectations and system
requirements, promoting a seamless and secure user experience.

3 TEST CRITERIA
3.1 Suspension Criteria
If the team members report that there are 40% of test cases failed, suspend testing until
the development team fixes all the failed cases.

3.2 Exit Criteria

Specifies the criteria that denote a successful completion of a test phase
- Run rate is mandatory to be 100% unless a clear reason is given.
- Pass rate is 80%, achieving the pass rate is mandatory.
4 RESOURCE PLANNING
4.1 System Resource

4.2 Human Resource Planning

5 SCHEDULE & ESTIMATION

5.1 All project task and estimation

Schedule to complete these task

 TEST DELIVERABLES
Test deliverables are provided as below
7.1 Before testing phase
- Test plans document.
- Test cases documents
- Test Design specifications.
7.2 During the testing
- Test Tool
- Simulators.
- Test Data
- Test Trace-ability Matrix
- Error logs and execution logs.
7.3 After the testing cycles is over
- Test Results/reports
- Defect Report

● Test Report for Test Cases inclusive of Test Procedures for identified Test Scenarios.
Sr. No. Test Case Steps Expected Result Actual Status
Description Result

TC1 Dashboard Access the No tasks should be PASSED PASSED

without login dashboard page visible; page
— no tasks without logging should prompt for
visible in. login.

TC2 Successful Attempt to logout Redirection to the PASSED PASSED

logout from the login page should
redirection dashboard without occur.
being logged in.

TC3 Check page Load the admin Page title should PASSED PASSED
title (Admin) dashboard page. match the
expected value.

TC4 Admin Check for Admin-specific PASSED PASSED

dashboard presence of content should be
content admin-specific visible.
presence content on the
dashboard.

TC5 Successful Click the logout Redirection to the PASSED PASSED

logout button on the login page should
redirection admin dashboard. occur.
(Admin)

TC6 Check page Load the user Page title should PASSED PASSED
title (User) dashboard page. match the
expected value.

TC7 Dashboard Check for User-specific FAILED FAILED

content presence of user- content should be
presence specific content visible.
(User) on the dashboard.
TC8 Task form Check if the task Task creation form PASSED PASSED
presence creation form is should be present
displayed. and visible.

TC9 Task 'Task 1' Add "Task 1" Task "Task 1" PASSED PASSED
added using the task should be
form. successfully added
to the task list.

TC10 Task 'Task 2' Add "Task 2" Task "Task 2" PASSED PASSED
added using the task should be
form. successfully added
to the task list.

TC11 Task 'Task 3' Add "Task 3" Task "Task 3" PASSED PASSED
added using the task should be
form. successfully added
to the task list.

TC12 Task Mark a task as Task should be PASSED PASSED

completion completed. marked as
completed.

TC13 Task Uncheck a Task should be PASSED PASSED

unchecking previously marked as active
completed task. again.

TC14 Filter Use the filter to Only completed PASSED PASSED

completed display only tasks should be
tasks completed tasks. visible.

TC15 Filter active Use the filter to Only active tasks PASSED PASSED
tasks display only should be visible.
active tasks.
TC16 Filter all tasks Display all tasks; "Task 1" should be PASSED PASSED
— 'Task 1' "Task 1" should present in the list.
be visible.

TC17 Filter all tasks Display all tasks; "Task 2" should be PASSED PASSED
— 'Task 2' "Task 2" should present in the list.
be visible.

TC18 Filter all tasks Display all tasks; "Task 3" should be PASSED PASSED
— 'Task 3' "Task 3" should present in the list.
be visible.

TC19 Task editing Edit an existing Task should be FAILED FAILED

task (e.g., update updated
the task successfully.
description or
title).

TC20 Task deletion Delete an existing Task should be PASSED PASSED

task from the list. successfully
removed from the
task list.

TC21 Successful Click the logout Redirection to the PASSED PASSED

logout button on the user login page should
redirection dashboard. occur.
(User)

TC22 Verify form Check for the Username and PASSED PASSED
fields presence of password fields
(username/pas username and should be present
sword) password fields in and visible.
presence the login form.

TC23 Test Enter valid User should be PASSED PASSED

successful username and redirected to the
login password (from dashboard, and
signup.py) and token set in
submit. localStorage.
TC24 Verify the Count the The number of PASSED PASSED
number of navigation links navigation links
navigation in the header. should match the
links expected count.

TC25 Verify text of Check the text of Text of the first PASSED PASSED
the first the first navigation link
navigation navigation link. should match the
link expected value.

TC26 Verify text of Check the text of Text of the second PASSED PASSED
the second the second navigation link
navigation navigation link. should match the
link expected value.

TC27 Verify header Check the main Header text should PASSED PASSED
text header text match the
displayed on the expected value.
page.

TC28 Verify Check the Paragraph text PASSED PASSED

paragraph text paragraph text should match the
content displayed expected value.
on the page.

TC29 Verify list Count the number The number of list PASSED PASSED
items count of list items items should
displayed on the match the
page. expected count.

TC30 Verify text of Check the text of Text of the first PASSED PASSED
list item 1 the first list item. list item should
match the
expected value.

TC31 Verify text of Check the text of Text of the second PASSED PASSED
list item 2 the second list list item should
item. match the
expected value.
TC32 Verify text of Check the text of Text of the third PASSED PASSED
list item 3 the third list item. list item should
match the
expected value.

TC33 Verify footer Check the footer Footer text should PASSED PASSED
text text displayed at match the
the bottom of the expected value.
page.

TC34 Check signup Load the signup Page title should PASSED PASSED
page title page. contain "Signup".

TC35 Check signup Load the signup Signup form PASSED PASSED
form presence page and check should be present
for the presence and visible.
of the signup
form.

TC36 Verify form Check for the All fields should PASSED PASSED
fields presence of be present and
presence username, visible.
(username, password, and
password, confirm password
confirm fields in the
password) signup form.

TC37 Test Enter a new User should be PASSED PASSED

successful username and successfully
signup password, registered.
confirm the
password, and
submit the form.

TC38 Redirection to After successful User should be PASSED PASSED

login page signup, check if redirected to the
after the user is login page.
successful redirected to the
signup login page.
TC39 Test signup Try signing up An alert with the PASSED PASSED
with existing with a username message
username that already exists "Username already
in the system. exists" should be
shown.

TC40 Test signup Submit signup An alert with the PASSED PASSED
with missing form with valid message
username passwords but "Username is
leave the required" should
username field be shown.
empty.

TC41 Test signup Submit signup An alert with the PASSED PASSED
with missing form with a valid message
password username but "Password is
leave the required" should
password field be shown.
empty.

TC42 Test signup Submit signup An alert with the PASSED PASSED
with missing form with a valid message "Confirm
confirm username and password is
password password but required" should
leave the confirm be shown.
password field
empty.

TC43 Test signup Submit signup An alert with the PASSED PASSED
with form with a valid message
mismatched username but with "Passwords do not
passwords non-matching match" should be
passwords in the shown.
password and
confirm password
fields.
TC44 Check login Load the login Page title should PASSED PASSED
page title page. contain "Login".
SCREENSHOTS - (User Interface & Testing Output results)