Update minitest 5.18.0 → 5.22.2 (minor) #28
Closed
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ minitest (5.18.0 → 5.22.2) · Repo · Changelog
Release Notes
5.22.2 (from changelog)
5.22.1 (from changelog)
5.22.0 (from changelog)
5.21.2 (from changelog)
5.21.1 (from changelog)
5.21.0 (from changelog)
5.20.0 (from changelog)
5.19.0 (from changelog)
5.18.1 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 45 commits:
prepped for release
- Third time's a charm? Remember: 'ensure' is almost always the wrong way to go.
prepped for release
- Don't exit non-zero if no tests ran and no filter (aka, the test file is empty).
prepped for release
+ Added "did you mean" output if your --name filter matches nothing. (tenderlove)
- Big cleanup of test filtering. Much prettier / more functional.
- Fix situation where Assertion#location can't find the location. (pftg)
prepped for release
- Fixed bug in Minitest::Compress#compress formatting w/ nested patterns. Now recurses properly.
prepped for release
- Rails' default backtrace filter can't currently work with caller_locations, so reverting back to caller.
prepped for release
+ Added Minitest::Compress#compress and added it to UnexpectedError
+ Filter failure backtraces using backtrace_filter before calculating location. (thomasmarshall)
better
+ Added ability to initialize BacktraceFilter w/ custom regexp.
Add changelog link to README and gem specification. (mattbrictson)
Fix rdoc to prevent wrong links and wrong quotes (stomar)
+ Output relative paths for all failures/errors/backtraces
+ Refactored location information in assertions, now using locations.
+ Make BacktraceFilter#filter compatible with locations (still compares strings).
- Drop undocumented bt arg in #skip. Dunno why that ever happened, prolly for testing?
Remove some long dead assertions and allow for assert_allocations in test_class_asserts_match_refutes.
emacs not so stupid anymore
+ Optimized Assertion#location ~30%.
+ Added --quiet flag to skip ProgressReporter (prints the dots). Minor speedup.
+ Add include_all kw arg to assert_respond_to and refute_respond_to.
- Fix mock to work with ruby debugger enabled. (keithlayne)
+ Removed thread and mutex_m dependencies. (hsbt, eregon)
prepped for release
+ Optionally allow autorun exit hook to remain active in forked child. (casperisfine)
Fixed skip messages for non-forking systems. (casperisfine)
prepped for release
+ Add metadata lazy accessor to Runnable / Result. (matteeyah)
- Minitest::TestTask enthusiastically added itself to default. (ParadoxV5)
+ Only load minitest/unit (aka ancient MiniTest compatibility layer) if ENV["MT_COMPAT"]
Replace 'MiniTest' with 'Minitest' in example code. (sambostock)
prepped for release
Removed 2.6 from CI.
- Avoid extra string allocations when filtering tests. (tenderlove)
- Only mention deprecated ENV['N'] if it is an integer string.
- Push up test_order to Minitest::Runnable to fix minitest/hell. (koic)
Use minitest organization in links (hsbt)
updated dates / versions in rails faq
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands