Upgrading rails-dom-testing 1 to 2
Breaking1.0.9 → 2.3.0Breaking4Platform1New4Changed10Fixed3Other1
BreakingUpgrade verdict
4 breaking changes and a platform requirement change.
In plain terms
- The old assert_tag test helper is gone, so tests that still use it will fail.
- Passing a block to an assertion that expects zero elements now fails with an error instead of being silently ignored.
- Invalid ranges or count limits now raise an error instead of being accepted.
- If a CSS selector has a syntax error, the library now reports the error instead of quietly ignoring the check with a warning.
Must act Top 4 of 5 that need code or config changes
Ruby requirement changed in 2.2.0: >= 0 → >= 2.5.0.
Adds minitest >= 0.
Drops rails-deprecated_sanitizer.
Moves activesupport < 5.0, >= 4.2.0 → >= 5.0.0, nokogiri ~> 1.6 → >= 1.6. Your build may pick other versions.
What you must change
Breaking4
Removes the deprecated
assert_tag assertion.assert_tagRaises an error when a block is given to a zero element assertion.
Raises an error when given an invalid Range or invalid :minimum and :maximum values.
:minimum:maximumRaises Nokogiri CSS syntax errors instead of skipping the assertion and outputting a deprecation warning.
Platform1
Adds Ruby 2.3 support.