fix(e2e): Don't write to restricted flows.data column in permission tests
#2500
Conversation
This file contains 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
DafyddLlyr
force-pushed
the
dp/fix-e2e-flows-data-permission
branch
from
1db98f9 to
6137d88
Compare
|
Removed vultr server and associated DNS entries |
jessicamcinchak
approved these changes
Nov 30, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes failing regression test - https://github.com/theopensystemslab/planx-new/commit/70baf93a4a47de8f125ea0925c70a4438cf98863/checks
Cause - This PR (#2488) restricted access to the
flows.datacolumn but E2E tests were not updated accordingly.🚀 Regression tests re-running against this PR here - https://github.com/theopensystemslab/planx-new/actions/runs/7044336391
Update: Regression tests passed ✅