Test suite cleanup and refactor #4
Merged
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
danguita
force-pushed
the
support/test-suite-cleanup
branch
from
61d79c5
to
a4d2443
Compare
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.
What does this PR do?
Sets up the Minitest based test suite by removing any unused dependencies and configuration options. Also it's adding a sample test stack to provide some guidance on coming features.
How should this be manually tested?
Run the entire test suite to get the following output:
$ script/test SiteTest test_valid PASS (0.06s) HomePageTest test_greeting SKIP (0.10s) MetaWelcomeControllerTest test_index PASS (0.07s) Finished in 0.24872s 3 tests, 3 assertions, 0 failures, 0 errors, 1 skipsThe skipped test case was intended.