derby v0.10.29 Release Notes
Release Date: 2020-06-24 // over 4 years ago-
🛠 Bugfixes
- #583 - Fix a
Component#destroy
error when no components on the page use bindings. (@ericyhwang)- The fixed issue should have only affected very small test cases, since most real Derby apps will have at least one
{{...}}
binding.
- The fixed issue should have only affected very small test cases, since most real Derby apps will have at least one
⚡️ test-util updates
- ✅ #583 -
ComponentHarness
now tracks the pages it creates, and theDomTestRunner
then uses that to destroy the created pages in anafterEach
. (@ericyhwang)
- #583 - Fix a
Previous changes from v0.10.28
-
✅ #581 - Improve test-utils assertions (@ericyhwang)
- In failure messages, state whether it was the HTML or DOM rendering that failed.
- This makes it easier to debug test failures.
.to.render()
- Compare DOM rendering to the HTML before components'create()
methods are called.- This fixes an issue where the assertion was improperly failing when a component modified its DOM in
create()
.
- This fixes an issue where the assertion was improperly failing when a component modified its DOM in
- Normalize HTML before comparisons.
- This fixes an issue where
.to.render()
assertions would fail when templates used HTML entities like
.
- This fixes an issue where
- In failure messages, state whether it was the HTML or DOM rendering that failed.