fix(geoprocessing): bring e2e test to valid state #184
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
|
This pull request is being automatically deployed with Vercel (learn more). marxan – ./app🔍 Inspect: https://vercel.com/vizzuality1/marxan/E3bthTWyaK1bBqXnd1kkZfNmzBWk marxan-storybook – ./app🔍 Inspect: https://vercel.com/vizzuality1/marxan-storybook/34qdzKJznMpHNgssgWg8mdnTzEdg |
aagm
approved these changes
May 14, 2021
hotzevzl
reviewed
May 14, 2021
| // TODO do actual verification & cleanup (table: planning_units_geom) after test | ||
| expect(value).toEqual([]); | ||
| }, | ||
| 10 * 1000, |
There was a problem hiding this comment.
this may still be just enough, and not always/in every instance - i'd up it even more
There was a problem hiding this comment.
🤷 hope 5x the above is enough ;)
fixed in 572b9b0
hotzevzl
approved these changes
May 14, 2021
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.
Substitute this line for a meaningful title for your changes
Overview
Please write a description. If the PR is hard to understand, provide a quick explanation of the code.
Designs
Link to the related design prototypes (if applicable)
Testing instructions
Please explain how to test the PR: ID of a dataset, steps to reach the feature, etc.
Feature relevant tickets
Link to the related task manager tickets
Checklist before submitting
develop.deploying to staging/production, please add brief testing instructions
to the deploy checklist (
docs/deployment-checklist.md)