Skip to content
This repository has been archived by the owner on Dec 21, 2023. It is now read-only.

Selenium E2E Tests for Bridge #4142

Closed
3 of 4 tasks
laneli opened this issue May 20, 2021 · 2 comments · Fixed by #4233 or #4239
Closed
3 of 4 tasks

Selenium E2E Tests for Bridge #4142

laneli opened this issue May 20, 2021 · 2 comments · Fixed by #4233 or #4239
Assignees
Labels
bridge.2.0 Bridge Version 2 type:chore Provides value to the (dev) team

Comments

@laneli
Copy link
Contributor

laneli commented May 20, 2021

Action Item

As keptn is growing and complexity is getting bigger we should introduce E2E tests (powered by Selenium) to tackle these challenges.
First step would be to introduce Selenium and get it running on the CI.

Definition of Done

  • Selenium is added
  • The tests are running in the CI
  • In the E2E test the sequence screen is opened and a screenshot taken
  • OPTIONAL: A drill down in the sequence screen is made to the first task in the sequence and a screenshot taken

⏳ This Action Item is timeboxed to 1.5 days.

@laneli laneli added type:chore Provides value to the (dev) team bridge.2.0 Bridge Version 2 labels May 20, 2021
@johannes-b johannes-b added this to the 0.9.0 (Bridge) milestone May 21, 2021
@johannes-b johannes-b added the ready-for-refinement Issue is relevant for the next backlog refinment label May 21, 2021
@johannes-b johannes-b added this to Ready for refinement in Refinement board May 21, 2021
@johannes-b johannes-b moved this from Ready for refinement to Refined and prioritized (Bridge) in Refinement board May 21, 2021
@warber warber removed this from Refined and prioritized (Bridge) in Refinement board May 21, 2021
@warber warber added this to To do in Sprint 220 [21/5 - 4/6] via automation May 21, 2021
@johannes-b johannes-b added next-sprint Items that should be discussed and implemented in the next sprint and removed ready-for-refinement Issue is relevant for the next backlog refinment labels May 21, 2021
@christian-kreuzberger-dtx christian-kreuzberger-dtx moved this from To do to In progress in Sprint 220 [21/5 - 4/6] Jun 1, 2021
@johannes-b johannes-b removed the next-sprint Items that should be discussed and implemented in the next sprint label Jun 1, 2021
christian-kreuzberger-dtx added a commit that referenced this issue Jun 2, 2021
Signed-off-by: Christian Kreuzberger <christian.kreuzberger@dynatrace.com>
@christian-kreuzberger-dtx christian-kreuzberger-dtx linked a pull request Jun 2, 2021 that will close this issue
@laneli
Copy link
Contributor Author

laneli commented Jun 2, 2021

I added an additional case that opens the user menu, clicks on "Copy to clipboard" for the api key and checks if it equals the api key retrieved from kubectl.

christian-kreuzberger-dtx added a commit that referenced this issue Jun 2, 2021
Signed-off-by: Christian Kreuzberger <christian.kreuzberger@dynatrace.com>
christian-kreuzberger-dtx added a commit that referenced this issue Jun 2, 2021
@christian-kreuzberger-dtx christian-kreuzberger-dtx moved this from In progress to Done in Sprint 220 [21/5 - 4/6] Jun 2, 2021
@laneli laneli linked a pull request Jun 7, 2021 that will close this issue
@laneli
Copy link
Contributor Author

laneli commented Jun 7, 2021

Also please note that we now use build in protractor instead of Selenium

@laneli laneli moved this from Done to Ready for review in Sprint 220 [21/5 - 4/6] Jun 7, 2021
@laneli laneli reopened this Jun 7, 2021
@laneli laneli moved this from Ready for review to Done in Sprint 220 [21/5 - 4/6] Jun 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bridge.2.0 Bridge Version 2 type:chore Provides value to the (dev) team
Projects
No open projects
3 participants