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

frontend: quickstart-vdk operability tests using cypress #2359

Merged
merged 1 commit into from
Jul 10, 2023

Conversation

DeltaMichael
Copy link
Contributor

@DeltaMichael DeltaMichael commented Jul 5, 2023

Why?

We test that the docker image is starting correctly, but we don't actually test that the frontend is operational. This has resulted in docker images where the docker image starts, but the frontend is not operational with no way of detecting the problem.

What?

  • Move regular e2e tests into their own directory
  • Introduce quickstart-smoke script
  • Create basic cypress smoke test for the frontend
  • Run smoke test after deployment to test environment

How was this tested?

Ran quickstart-vdk locally and ran cypress against frontend CI on localhost:8092

Ran smoke tests and e2e tests in CI https://gitlab.com/vmware-analytics/versatile-data-kit/-/pipelines/921430730

What kind of change is this?

Feature/non-breaking

@DeltaMichael DeltaMichael force-pushed the person/mdilyan/quickstart-vdk-operability-tests branch from 3ac3909 to 5d7479a Compare July 5, 2023 09:28
@DeltaMichael DeltaMichael marked this pull request as draft July 5, 2023 09:28
@DeltaMichael DeltaMichael force-pushed the person/mdilyan/quickstart-vdk-operability-tests branch 4 times, most recently from 314d15f to dc1cb3a Compare July 5, 2023 11:48
@DeltaMichael DeltaMichael marked this pull request as ready for review July 5, 2023 11:51
Why?

We test that the docker image is starting correctly,
but we don't actually test that the frontend is operational.
This has resulted in docker images where the docker image
starts, but the frontend is not operational with no way
of detecting the problem.

What?

- Move regular e2e tests into their own directory
- Deployment to test environment now depends on e2e tests running
successfully beforehand
- Introduce quickstart-smoke script
- Create basic cypress smoke test for the frontend
- Run smoke test after deployment to test environment

How was this tested?

Ran quickstart-vdk locally and ran cypress against frontend
CI

What kind of change is this?

Feature/non-breaking

Signed-off-by: Dilyan Marinov <[email protected]>
@DeltaMichael
Copy link
Contributor Author

Follow-up ticket #2365

@DeltaMichael DeltaMichael merged commit b608cbd into main Jul 10, 2023
@DeltaMichael DeltaMichael deleted the person/mdilyan/quickstart-vdk-operability-tests branch July 10, 2023 09:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants