68a032a734
Clock manipulation seems not reliable in component tests. This blog post does a great job of explaining it: https://dockyard.com/blog/2018/04/18/bending-time-in-ember-tests Sadly, we don't have all the "recent" ember test helpers and can't use things like `getSettledState()`. For now this pattern seems the most reliable and easy to apply, albeit not great. Note if you wish to reproduce the current timeout, the following command should do it: `QUNIT_SEED=215263717493121190480103670124734840282 rake qunit:test` |
||
|---|---|---|
| .. | ||
| actions-summary-test.js | ||
| avatar-flair-test.js | ||
| button-test.js | ||
| default-notification-item-test.js | ||
| hamburger-menu-test.js | ||
| header-test.js | ||
| home-logo-test.js | ||
| post-links-test.js | ||
| post-menu-test.js | ||
| post-stream-test.js | ||
| post-test.js | ||
| poster-name-test.js | ||
| quick-access-item-test.js | ||
| small-user-list-test.js | ||
| software-update-prompt-test.js | ||
| topic-admin-menu-test.js | ||
| topic-participant-test.js | ||
| topic-status-test.js | ||
| user-menu-test.js | ||
| widget-dropdown-test.js | ||
| widget-test.js | ||