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

How do we exercise browser tests in the pipeline #841

Closed
diversemix opened this issue May 4, 2020 · 2 comments
Closed

How do we exercise browser tests in the pipeline #841

diversemix opened this issue May 4, 2020 · 2 comments
Assignees
Milestone

Comments

@diversemix
Copy link
Contributor

diversemix commented May 4, 2020

Depending on #839 ... this will determine how the tests are run and which tools are used.

From this decision we will need to create tickets for infrastructure and any scripts/actions to run the tests in the way chosen. This will affect the pipelines for the umbrella repo and the staging pipeline.

@diversemix diversemix added this to the Release milestone May 4, 2020
@erkannt erkannt self-assigned this May 5, 2020
@erkannt
Copy link
Contributor

erkannt commented May 7, 2020

  • succeeded in running nightwatch from within a container with chrome-webdriver
  • testcafe already provides such an image

Ergo: we can probably package our tests into such a container and use it for testing in umbrella, staging and production.

  • k8s has definitions for container based jobs
  • helm has a hooks for test or parts to run after a release
  • how to tie a browsertest-container into automated releases, monitoring, logging and alerting will require further discovery

@erkannt erkannt mentioned this issue May 7, 2020
4 tasks
@erkannt
Copy link
Contributor

erkannt commented May 7, 2020

Created #865 and #867

@erkannt erkannt closed this as completed May 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants