Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

False positives in namespaces e2e-tests and Flakiness in pods e2e-tests #2927

Open
adwait-godbole opened this issue Feb 19, 2025 · 1 comment
Labels
bug Something isn't working CI Issue related to CI e2e-tests End to end tests

Comments

@adwait-godbole
Copy link
Contributor

adwait-godbole commented Feb 19, 2025

I downloaded multiple e2e-tests-report artifacts from main branch GitHub Actions runs of build-container.yml workflow for e.g. one of them is this one and observed that in all the reports the namespaces test showed the below report (indicating a false positive)

Image

and the pods test showed the below report (indicating a flakiness)

Image

I think this is the same issue that I was trying to highlight in this comment of mine on an on-going PR involving e2e-tests where I uploaded the below UI which I was seeing on performing a manual e2e-tests setup (as it is being done in the build-container.yml CI workflow) rather than using the minikube addon .

Image

I think the current way we are setting up our e2e-tests environment in the build-container.yml CI workflow using kubernetes-headlamp-ci.yaml manifest is introducing too many plugins that are causing the UI to look very much different than an ideal scenario with just for e.g. a single pod-counter plugin.
The current implementation of these 2 tests is not matching up with the UI that is being rendered.

To Reproduce

Steps to reproduce the bug:
Perform a manual setup of the e2e-tests following build-container.yml workflow instead of using the minikube addon and visit the Headlamp UI and then try running these 2 tests on your local.

Environment (please provide info about your environment):

CI Workflow / Local e2e-tests Setup

Are you able to fix this issue?

[Yes (I can propose a PR after having a discussion with the maintainers about how to proceed for a fix)]

@adwait-godbole adwait-godbole added the bug Something isn't working label Feb 19, 2025
@dosubot dosubot bot added CI Issue related to CI e2e-tests End to end tests labels Feb 19, 2025
@adwait-godbole
Copy link
Contributor Author

Also the current implementation of the podsPage e2e-test involves creating and deleting a pod. However, again when I tried to do a manual e2e-test setup, I observed that the delete button on the Pod detail page is just a placeholder with some random text on its tooltip and does not perform any delete action as such. So again, this would also need to be considered / fixed while thinking about how to proceed with a solution for the issue as a whole.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working CI Issue related to CI e2e-tests End to end tests
Projects
Development

No branches or pull requests

1 participant