Adding some starting points for testing the controller #18
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
|
Looks pretty good. I'll take some time to check it out soon. |
|
I've written a related blog post on getting these tests up and running. |
dsyer
added a commit
that referenced
this pull request
Jan 5, 2015
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.
How do you feel about including some starting points for unit and integration testing to the guide?
It took me a few hours and much googling of blogs to figure out how to do this in one of my own applications so I believe it would be useful to include some notes on how to test Spring Boot Web applications at the end of the guide. I've made my changes to the 'complete' project.
I can't seem to get gradle to work in my environment so
complete/build.gradlemay not be quite right.