chore: Replace catch
with assert.rejects|throws
in tests (part 3 of 3)
#3661
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes: #3426
Note: This is part 3 of 3, so the issue is done after this merges. There's some tests that weren't converted, for various reasons, detailed in each PR.
#minor
Description
We has some awkward usage of
That I converted to
Note
There's a commit with a bunch of no-op linting fixes. I recommend mostly reviewing the other one. However, I accidentally committed some no-op changes to
skillDialog.test.js
. sorry.I skipped a LOT of tests in
botframework-streaming
because:chai
, which doesn't handlerejects()
withoutchai-as-promised
rejects()
and are handled better/easier with the existing try/catch