Skip to content

Fix flaky integration tests #142

@kostis-codefresh

Description

@kostis-codefresh

The current integration tests are based on timeouts. Several times, either locally or in GitHub action they fail without any changes in the code.

This makes regression testing impossible as it is tough to validate brand new features.

Other problems with the e2e tests

  • code duplication among all tests
  • Passing everything as unstructured data, resulting in more verbose code
  • No clear assertions on what the test checks
  • No logs that show what actually went wrong when a test fails.

Metadata

Metadata

Labels

testingUnit/Integration tests

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions