E2E Automation Test Plan

Goal:

1. To prevent manual QA performing repetitive testing for important features in Identifi application.

2. To ensure that identifi feature were not affected with the latest update.

3. To give the team more time on challenging task.

4. To improve accuracy of the application.

5. To increase Test coverage.

Scope:

Answers which part of the system requires E2E automation

Environment to test:

• Dev Environment : Local environment

Testing types we are going to use:

• Regression testing

• Sanity testing

Features included in the Regression test:

• Owner

  1. Login

  2. Signup

  3. Activity Feed

     1. Filter-feed

     2. Personal-view feed

     3. pin-post

  4. Calendar

  5. Directory

  6. Getting Started

  7. Settings

     1. Boost Settings

     2. Calendar Settings

     3. Company Settings

     4. Daily Review Settings

     5. Personal Settings

     6. Employee Settings

        1. Employee List

        2. Employee Profile

        3. Manage Employee

  8. Holidays

  9. Events

• User

  1. Activity Feed

     • Bookmark

       1. Bookmark

       2. Bookmark widget

     b. Filter feed

     c. Personal view feed

     d. view pin post

  2. Boost

  3. Calendar

  4. Dashboard

     1. Company-tab

     2. Daily review

     3. Direct report tab

     4. header

     5. Metrics

     6. Mood entry

     7. Follow/Unfollow

     8. Personal tab

        1. comment-react

        2. Personal tab

  5. Holidays

  6. Events

Features included in the Sanity test:

• Login

• Member

  1. Activity Feed

  2. Activity navigation panel

  3. Directory

  4. Getting Started

  5. Bookmark & Pin post

  6. Dashboard

     1. Company tab

     2. Dashboard

  7. Notification

  8. Profile menu

  9. Setting

  10. Calendar

  11. Holidays

  12. Events

• Owner

  1. Activity navigation panel

  2. Bookmark & Pin post

  3. Employee profile

  4. Notification

  5. Personal view feed

  6. Activity feed

  7. Boost

  8. Daily Review

  9. Dashboard

  10. Settings

  11. Comment & Reaction

  12. Leaves

  13. Holiday

  14. Events

  15. Celebration

Entry Criteria

What are the things needed before starting E2E automation testing.

1. Test automation tools

   1. E2E test suite Cypress version installed

   2. Test Git mono repository

   3. Testing reports and Analytics

2. Stable project environment build where the test runs

   1. Local test environment for Dev build

   2. Production test environment for QA

3. Test case documents

   1. PASSED test cases

   2. Testing type tags for each test cases (Regression or Sanity)

   3. Identified test cases that can be automated

4. Manpower

   1. Test Automation Engineers

Exit Criteria

What are the things to expect after writing of End to End test.

1. All test cases for Regression test defined in the scope are with automation script.

2. All test cases for Prod Sanity test defined in the scope are with automation scirpt.

3. Regression scheduled test run for Dev environment

4. CI setup for E2E test is done

5. Slack command trigger to run Sanity test automation

6. Slack command trigger to run Regression test automation

7. Slack notification for the Test reports and status results.

Identifi test needs for maintenance for UI updates and new features in the product