feat(test): add table tests for new extension workflow #6296
Conversation
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
paulrosca-snyk
force-pushed
the
feat(test)/new-extension-table-tests
branch
3 times, most recently
from
310861f to
fe040e7
Compare
paulrosca-snyk
force-pushed
the
feat(test)/new-extension-table-tests
branch
from
fe040e7 to
408b979
Compare
| env, | ||
| }); | ||
|
|
||
| if (code != 0) { |
Contributor
There was a problem hiding this comment.
Suggestion: Do you want to extend and re-use this, instead of having the following code block the tests?
Contributor
There was a problem hiding this comment.
Nevermind, I just see that it is only copied
PeterSchafer
approved these changes
Nov 11, 2025
Contributor
PeterSchafer
left a comment
PeterSchafer
left a comment
There was a problem hiding this comment.
nitpick: this is probably not a feat, consider using chore. Feat are used for user facing changes.
nicarl
force-pushed
the
feat(test)/new-extension-table-tests
branch
from
408b979 to
d84e30f
Compare
nicarl
force-pushed
the
feat(test)/new-extension-table-tests
branch
from
d84e30f to
3e76ece
Compare
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.
Pull Request Submission Checklist
are release-note ready, emphasizing
what was changed, not how.
What does this PR do?
Bumps
cli-extension-os-flowsandcli-extension-dep-graphto the latest versions, in order to fix any discrepancies in the output, compared to the legacy CLI.Wraps the
snyk testtests in user journey table tests, with only the legacy workflow test enabled. The go workflow implementation will be enabled in a following PR, alongside with enabling the feature flags required to access it, on the cli testing org.Where should the reviewer start?
How should this be manually tested?
What's the product update that needs to be communicated to CLI users?
N/A