Remove non-Rails-5 features from controller spec scaffold #1689
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.
Fixes #1605 by removing all expectations for assigns and templates rendered from the controller specs generated for scaffolds. Sample generated spec below.
They feel a big lethargic because all that’s being specified for a lot of the methods now is only that they return HTTP success—but I believe that’s all there is to specify for them in a vanilla Rails 5 install.
A few other things we could consider:
rails-controller-testing
gem.rails-controller-testing
gem), and generating the appropriate expectations then. That would significantly increase the complexity of the controller spec template.Happy to take this PR any direction y’all would like—let me know how I can help!
Here’s a sample of the generated spec, which passes once I take care of the skips: