Generate a tests file #1172
Merged
Generate a tests file #1172
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
fortmarek
approved these changes
Mar 31, 2020
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.
Short description 📝
I recently changed the template that gets generated with
tuist initso that it leverages the helpers that are generated. Those helpers define for each framework 2 targets, one with the source, and the other one with the tests.Since I forgot to update the template to generate a tests file, running
tuist generateon the project scaffolded withtuist scaffold framework MyFrameworkresults in warnings because the tests target contains no files.This PR fixes that by extending the template to generate an empty test case. I added an acceptance test to make sure that the generated tests target is testable.