Test Environment

Testing Tools

Testcafe for E2E (Regression, Smoke and Targeted Feature Tests)

Jmeter for Performance Tests

Pact for Integration/Contract Tests

Browser Matrix

Browser

Version

Priority

Chrome

1.2.3.4

HIGH

Firefox

1.3

HIGH

Firefox

1.0

HIGH

IE11

2.3

MEDIUM

We won’t do Snapshot, Layout Tests at the moment, maybe in 6 months we need to revisit that. Create ticket XXX on the backlog to investigate.

We won’t use BDD for the E2E tests as the team agreed that there is no need for it.

Release Control

  1. PR Created → Unit Test
  2. Merged to Master and Deployed to Dev → Integration Tests
  3. Deploy to QA → Exploratory and E2E Tests
  4. Deploy to Prod → Smoke Tests

Risk Analysis

We are going to use Pairwise as a technique to combine different scenarios trying to cover as maximum as possible, but it is impossible to test all the 100 different combinations of the requirements, so we will do a risk analysis focusing on getting the most used and most critical ones and added them to the regression pack.

Review And Approvals

QAs and Devs are going to review the PRs, not only the test automation ones but also the developers. Ensuring that we are covering the max number of test cases not only on the UI and API level, but also on the Unit and Integration levels.

We will make sure we can cover most of the cases during the Unit and Integration and reduce the scope of the scenarios for the E2E scenarios.

POs and BAs will be reviewing the features during demos after the development is done and after QA is done in case there is a need to approve/reject some issue found.