CHI-3534 - Set up integration test - NZ #3728
Open
+158
−1
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
stephenhand
approved these changes
Dec 2, 2025
Collaborator
stephenhand
left a comment
stephenhand
left a comment
There was a problem hiding this comment.
Minor naming q, otherwise it looks good
| "event": "noMatch" | ||
| }, | ||
| { | ||
| "next": "f_end_integration_test", |
Collaborator
There was a problem hiding this comment.
f_end_integration_test - this might have been a typo in my original example, there's no reason to prefix the name of that step with 'f_' (unless there is?)
Contributor
Author
There was a problem hiding this comment.
There's an attempt to standardise the naming of studio widgets, so that's where this comes from - I think Humairaa is busy on updating all studio flows
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.
Description
Checklist
Other Related Issues
None
Verification steps
AFTER YOU MERGE
You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P