Fix should print warning about default namespace when running odo dev test when Dev Session does not start correctly#6848
Conversation
…v` test when Dev Session does not start correctly The goal of this test is to ensure that the warning message is displayed, so it does not matter if the Dev Session does not start correctly.
✅ Deploy Preview for odo-docusaurus-preview canceled.
|
|
Kudos, SonarCloud Quality Gate passed!
|
Unrelated test. /override OpenShift-Integration-tests/OpenShift-Integration-tests |
|
@rm3l: Overrode contexts on behalf of rm3l: OpenShift-Integration-tests/OpenShift-Integration-tests DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Unrelated test. /override windows-integration-test/Windows-test |
|
@rm3l: Overrode contexts on behalf of rm3l: windows-integration-test/Windows-test DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |








What type of PR is this:
/kind bug
/area testing
What does this PR do / why we need it:
The goal of this test is to ensure that the warning message is displayed when using the default namespace/project;
so it does not matter if the Dev Session does not start correctly (as can be the case in certain environments like OCP 4.14).
Which issue(s) this PR fixes:
Fixes #6847
PR acceptance criteria:
Unit test
Integration test
Documentation
How to test changes / Special notes to the reviewer: