v0.10.31

• #595 - test-utils .to.render assertion: Reset page/component state between each render pass (@ericyhwang)
  • This solely changes test util code and should have zero effect on production code.

v0.10.30

• #593 - Fix typo in changeImmediate listener for event.passed (@ericyhwang)
  • This fixes an issue using derby <= 0.10.29 with [email protected], where highlighting some bound text and typing over it (replacing it) causes the cursor to jump to the end of the input field.

v0.10.29

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.

test-util updates

• #583 - ComponentHarness now tracks the pages it creates, and the DomTestRunner then uses that to destroy the created pages in an afterEach. (@ericyhwang)

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().
• Normalize HTML before comparisons.
  • This fixes an issue where .to.render() assertions would fail when templates used HTML entities like  .

v0.10.27

• #576 - Fix ShareDB "Invalid or unknown message" warnings when using auto-refresh (@IAkumaI, @ericyhwang)
  • Auto-refresh is generally only used in development environments

v0.10.26

• #574 - In domTestRunner, add support for passing JSDOM options (@ericyhwang)

v0.10.11

• #560 - fix: Fix auto-refresh for views and styles when running multiple Derby apps in a single Node server (@IAkumaI)