Skip to content

README.md

Latest commit

 

History

History
48 lines (39 loc) · 1.96 KB

README.md

File metadata and controls

48 lines (39 loc) · 1.96 KB

Task Master Automated Testing

Overview

This respository contains automated tests for Task Master, a to-do web application. Selenium is used as an automation tool, tests are run in JUnit framework and project follows Page Object Model (POM) design pattern.

The purpose of this project is to provide extensible automated tests for validating the proper functionality of the app, assessing and prioritising the risk factors in testing according to formal requirements, business context and app history.

Prerequisites

Before running the tests, ensure you have the following:

  • JAVA JDK 8+
  • Maven
  • Access to the Task Master application (check app's documentation for setup)

Frameworks and tools used in the project:

  • Selenium 4.35.0
  • JUnit 5.9.1
  • Maven 17

Running the tests

  1. Clone this repository
  2. Open Windows PowerShell, Command Prompt or a terminal
  3. Navigate to the project's root folder (where pom.xml is located)
  4. Run mvn test

Identified risks

According to previous application history, the following risks were identified:

  • Data security, GDPR compliance
  • Achieving high test coverage
  • Creating clear developer documentation
  • Intuitive and responsive UI
  • Credentials validation
  • Login/session handling failures
  • CRUD tasks

Identified bugs

The automated tests revealed the following bugs:

  • Duplicate usernames are allowed during registration
  • Header elements are cut off on desktop and mobile screen sizes.

Check the documentation for more info on the bugs: https://pmate00.atlassian.net/jira/software/c/projects/WHAT/summary

Notes

  • Some risks require manual or grey-box verification (password encryption, account deletion, developer documentation etc.)
  • Automated tests focus on functional testing, CRUD operations, user validation, and UI behavior.
  • Tests are organized according to user stories and risk priority, following a risk-based testing approach.
  • Page Object Model design pattern is used to organise the automation code.