[make:crud] Ensure the generated functional tests run in MakerBundle's CI #1774
+7
−4
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
…run in MakerBundle CI
Contributor
|
I believe it's good for now to mark tests as incomplete, for two reasons:
But yes, moving them at the end of the method is good for the CI! |
tcoch
approved these changes
Jan 13, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
In order to ensure there is no regression in the generated test case (#1773), they must be run in MakerBundle's CI.
The
markTestIncompletecall stops the execution by throwing and exception. Skipping all the test body. By moving this call at the end of the method, the tests are fully run.I even wonder if marking tests as incomplete serves any purpose.
For reference, this was added in #307, this point was not discussed.