[DO NOT MERGE] test: fix Dashboard path - #323
Closed
MattiaSarti wants to merge 1 commit into
Closed
Conversation
Contributor
🤖 Backport labels populatedLabels to this pull request were added automatically by the When the PR is merged, backport PRs according to the labels will be automatically created. To skip the backport creation, remove any unneeded labels before merging the PR. |
github-actions
Bot
added
the
Libraries: Out of sync
MattiaSarti
changed the title
Contributor
Author
|
Closed as only used to showcase the bug. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request fixes the Dashboard path validated in integration tests.
note: the first commit was just to make sure that paths that do not exist do make tests fail, because the path previously used was to the Volumes web app, and tests were successfully passing despite the Volumes web app not being deployed, probably because the UI page for Volumes was actually there, even if empty, giving a successful yet empty response (without the tests checking for HTML content)