[AF-45] Allow test files when publishing the gem #46
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
ricardopacheco
added
type:bug
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.
Issue number: resolves #45
Summary 🔴
Although unnecessary to run in a production environment, in the integration with the API, factories are used to test the data on the endpoints. Therefore, from version
0.8.10onwards, the test files will be available when publishing the gem.Proposed / Possible solution 🔴
Configure the auction_fun_core.gemspec file so that in the files option (spec.files) it no longer ignores the tests directory (specs).
How to test 👮♂️
Update the gem core version in the API and check it in the test suite in CI.
Risks / Impacts 🔴
Requirements for deployment 🔴