Automation Practice Test Plan

Description:

The Automation Practice website is a full-fledged website built for automation practice purposes.

This project aims to showcase the test process used on Automation Practice including the creation of test documentation, such as user stories and the different test types and test cases derived from them, including e2e, functional, performance, accessibility and visual tests.

It implements all such tests cases using the Cypress testing framework.

Testing Process:

In order to do a thorough testing of the functionality present in the Automation Practice website these steps have been taken:

1. Create an account on the application
2. Do exploratory testing / use the application as an user would
3. Divide the app into different buckets of functionality
4. Prioritize buckets of functionality depending on risk
5. Create User Stories for each of the buckets of functionality
6. Create Test Cases for each of the User Stories
7. Create detailed test cases in a spreadsheet
8. Create automated test scripts from detailed test cases (only high prio)

1. Create an account on the application: (DONE)

2. Do exploratory testing / use the application as an user would: (DONE)

3. Divide the app into different buckets of functionality: (DONE)

The following buckets of functionality have been indentified:

• Main Page
• Authentication
• My Account
• Contact Us
• Search
• Catalogue
• Shopping Cart
• Product Detail Page(PDP)
• Checkout
• Subscribe
• Footer

4. Prioritize buckets of functionality depening on risk: (DONE)

High prio

• Checkout
• Shopping Cart
• Product Detail Page(PDP)
• Authentication
• Catalogue
• Search

Low prio

• My Account
• Contact Us
• Subscribe
• Main Page
• Footer

5. Create User Stories for each of the buckets of functionality: (DONE)

Each bucket of functionality will be made of a Description where the specific functionality is described, followed by User Stories of such functinality.

These in turn are compromised of at least as many Test Cases derived from them.

In the wiki lists these test case names can be found beneath the user story they belong to.

Each test case name will represent a test case in a spreadsheet(complete with test data, test steps and expected and actual resutls) AND a test script in a test suit(complete with test data, automated test steps and test assertions).

Buckets of functionality can then be broken down the following way:

• Bucket of functionality:

  • User Stories:

    • Test cases (spreadsheet):

      • Test data
      • Test steps
      • Expected and actual results

    • Test scripts (code):

      • Test data
      • Automated test steps
      • Automated test assertions

You can click on the links below. Each bucket of functionality will link to their own wiki page, where their description, user stories and test case names are displayed. At the bottom of each wiki page there are links to both the spreadsheet test cases and the test scripts representing them.

High Prio Buckets

• Checkout:

  • Shopping Cart
  • Sign In
  • Address
  • Shipping
  • Payment

• Shopping Cart

• Product Detail Page

• Authentication

• Catalogue

• Search

Low Prio Buckets

• My Account

• Contact Us

• Subscribe

• Main Page

• Footer

Features:

• Equivalence partitioning tests
• Boundary value analysis tests
• UI functional tests
• Accessibility tests (pending)
• Responsiveness tests (pending)
• Visual tests (pending)

Uses

• Cypress