-
Port all our old e2e tests to e2e_new using the new test framework, then rename the directory e2e_new to e2e.
Steps:
* [x] Add KafkaSink resource (like https://github.com/knative/eventing/tree/m…
-
**User Story**
In order to make sure that OSM is working as expected, we need to make sure that we test it thoroughly with every PR merge. That's why we need a proper infrastructure where we can build…
-
adding/updating auto e2e test cases for https://github.com/longhorn/longhorn/issues/8643 if they can be automated
cc @longhorn/qa
-
adding/updating auto e2e test cases for https://github.com/longhorn/longhorn/issues/9089 if they can be automated
cc @longhorn/qa
-
/kind failing-test
/area testing
**What steps did you take and what happened:**
E2E tests for CSIMigration is failing after [CAPI bump to v1.5.0](#4390). This needs to be fixed. The test is curre…
-
adding/updating auto e2e test cases for https://github.com/longhorn/longhorn/issues/8601 if they can be automated
cc @longhorn/qa
-
### CI Test Type
Acceptance
### Stacktrace
```shell
-> Failed [ Took 50.807 seconds ]
Failures:
1. Exploration Creator should draft, discard and publish the changes
Message:
Error: Element …
Vir-8 updated
2 weeks ago
-
The e2e is part of the main module which creates unnecessary dependencies. Make e2e a separate module to remove this. Update Makefile (and other scripts) that interact with e2e.
-
[maas.io e2e test failed](https://github.com/canonical/maas.io/actions/runs/11363459778) for the main branch.
-
**What happened**:
Currently, all e2e test on Arm64 platform is running on k8s 1.28 which is EOF.
**What you expected to happen**:
We need to update the kind-1.28 provider to the latest version.