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.

Sign up for GitHub

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

Jump to bottom

[Test Case] - Get Started guides - Deploy and expose a microservice #15615

Open
Disper opened this issue Sep 23, 2022 · 0 comments
Open

[Test Case] - Get Started guides - Deploy and expose a microservice #15615

Disper opened this issue Sep 23, 2022 · 0 comments
Assignees
@strekm
Labels
area/documentation Issues or PRs related to documentation kind/missing-test Categorizes issue or PR as related to missing automated tests for scenario. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. test-case

Comments

@Disper
Copy link
Member

Disper commented Sep 23, 2022

Summary

The purpose of the test is to make sure that Deploy and expose a microservice part of Get Started guides is up to date and working properly.

Test Steps

  1. Download the kubeconfig from Kyma.
  2. Go through the Deploy and expose a microservice and make sure it's up to date and working properly.

CAUTION: Remember to test BOTH PATHS - CLI and Kyma Dashboard ❗ Just because one is working doesn't necessarily mean the other must be too. There might be new UI changes that haven't been accounted for, or some backend case that was not implemented in the UI, or a bug/typo in a CLI command, and so on.

Expected Results
The tutorials are up to date and working properly.
@Disper Disper added area/documentation Issues or PRs related to documentation test-case lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. labels Sep 23, 2022
@Disper Disper mentioned this issue Sep 23, 2022
Open
@strekm strekm added the kind/missing-test Categorizes issue or PR as related to missing automated tests for scenario. label Sep 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@strekm strekm

Labels
area/documentation Issues or PRs related to documentation kind/missing-test Categorizes issue or PR as related to missing automated tests for scenario. lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. test-case
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Disper @strekm