Skip to content

CI - E2E Tests are run and unnecessarily mandatory on changes that should not #1607

@fluentcrafter

Description

@fluentcrafter

Description

E2E tests rules should be fine-tuned to be required when they effectively deliver value, otherwise they cost money and time without any benefit.

Example PR that could not be merged because e2e tests were required but don't deliver value

Motivation

  • time saving on the CI
  • cost saving

Tasks

  • Review and Adjust e2e tests

Acceptance criteria

  • e2e are not triggered nor required by changes that won't be covered by the e2e stack.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions