Run a subset of e2e tests on test environment UI #2332
Labels
enhancement
New feature or request
Comments
DeltaMichael
pushed a commit
that referenced
this issue
Jul 10, 2023
Why? #2332 This issue has been resolved, so we can re-enable stable tagging for the frontend. The change lets us use our CI/CD pipeline to deliver updates to the frontend and quickstart-vdk with sufficient release confidence. What? Enable stable tagging for the frontend docker image. This lets us deliver updates for the frontend as part of quickstart-vdk. Note: The stable tag is pulled each time quickstart-vdk is restarted and the helm chart it uses re-deployed How was this tested? The stable tagging job ran as part of the CI before, we just didn't have sufficient testing around the frontend image, so we disabled it. We use the same script for tagging with latest, so it should be fine. What kind of change is this? Feature/non-breaking Signed-off-by: Dilyan Marinov <mdilyan@vmware.com>
DeltaMichael
added a commit
that referenced
this issue
Jul 11, 2023
## Why? #2332 This issue has been resolved, so we can re-enable stable tagging for the frontend. The change lets us use our CI/CD pipeline to deliver updates to the frontend and quickstart-vdk with sufficient release confidence. ## What? Enable stable tagging for the frontend docker image. This lets us deliver updates for the frontend as part of quickstart-vdk. Note: The stable tag is pulled each time quickstart-vdk is restarted and the helm chart it uses re-deployed ## How was this tested? The stable tagging job ran as part of the CI before, we just didn't have sufficient testing around the frontend image, so we disabled it. We use the same script for tagging with latest, so it should be fine. ## What kind of change is this? Feature/non-breaking Signed-off-by: Dilyan Marinov <mdilyan@vmware.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the feature request? What problem does it solve?
The current flow of testing and releasing the frontend is as follows:
On every merge to main:
Build and test data-pipelines and shared packages and push them to npm registry
Build the UI docker image and tag with latest
Deploy the UI docker image to test environment
Ping UI with vdk-heartbeat
Tag UI docker image as stable
The amount of testing in step 4 is insufficient to detect breaking changes in the frontend image. Ideally, we should run a subset of the e2e tests on the UI in the test environment before we tag it as stable
The subset should exclude all tests related to explore page and the widgets component.
Suggested solution
Can be done by executing cypress tests. Using one of the following libraries to run the equivalent smoke tests in vdk-heartbeat is also a viable solution.
https://pypi.org/project/robotframework/
https://pypi.org/project/PyAutoGUI/
https://docs.pylenium.io/
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: