Skip to content

spike acceptance test lifecycle based on playwright #3520

Open
@enekofb

Description

As part of https://www.notion.so/weaveworks/Rehabilitate-Weave-GitOps-Enterprise-testing-4c5b4d8fe52547e587f12fea9c91263c?pvs=4

And to follow up to #3280

We want to keep building the understanding of whether Playwright is the right solution for weave gitops enterprise acceptance or e2e layer.

Therefore we want to evaluate the solution against the existing one in the following three journeys:

Add New Test

As dev,
Given I have a new feature to deliver
I want to understand the journey for adding a new test to the playwright test suite
So It could be part of the it

Regression Test

As dev,
Given i have added my test to the playwright test case
I want the playwright acceptance test to be running for each commit into main.
So I could ensure that my feature is available for any new change

Troubleshooting a failing Test

As dev,
Given a playwright test case has failed during CI
I want to understand what the troubleshooting journey looks like and tooling available
So i could fix the failing test

Acceptance Criteria

It would be great a doc with the example that covers:

  • how to achieve the previous scenarios
  • how this solution compares to our existing setup with pro/cons against the problems that we are trying to improve
  • Based on the comparison a recommendation whether go / no go that we could share with a wider group

Metadata

Assignees

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions