Skip to content
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.

tests: Clean up t.throws() and async usage #1159

Merged
merged 1 commit into from
Oct 9, 2018
Merged

tests: Clean up t.throws() and async usage #1159

merged 1 commit into from
Oct 9, 2018

Conversation

edmorley
Copy link
Member

@edmorley edmorley commented Oct 9, 2018

  • The error message can be checked by t.throws() itself, so no need for a separate assertion for that afterwards.
  • We were marking several tests as async that were actually not.

* The error message can be checked by `t.throws()` itself, so no
  need for a separate assertion for that afterwards.
* We were marking several tests as async that were actually not.
@edmorley edmorley self-assigned this Oct 9, 2018
@edmorley edmorley merged commit 76ac4e2 into neutrinojs:master Oct 9, 2018
@edmorley edmorley deleted the tests-cleanup branch October 9, 2018 11:47
edmorley added a commit that referenced this pull request Oct 9, 2018
* An error is now shown when using the `links` HTML option without
  also specifying a custom template, so that users affected by #1049
  know what changes they need to make. See:
  #1129 (comment)
* The migration guide now recommends regenerating the lockfiles.
* The migration section about supported Node.js versions has been made
  clearer. See:
  #1129 (comment)
* The `neutrino` bin script error message now mentions `test` being
  removed, includes `--mode` for the inspect example, and uses the
  correct URL for the migration guide.
* The `minify.image` option deprecation error message no longer refers
  to `@neutrinojs/image-minify`, since it was removed. I've linked
  to the issue since it gives more background as to why compile-time
  minification is not recommended.
* The `hotEntries` option deprecation check now always occurs, and not
  only when `options.hot` is enabled. A test has also been added.
* Cleans up a few more `t.throws()` usages (missed in #1159).
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

Successfully merging this pull request may close these issues.

1 participant