Skip to content

refactor(test): use more specific checks in check-tsconfig spec#398

Merged
ezolenko merged 1 commit into
ezolenko:masterfrom
agilgur5:refactor-test-check-tsconfig
Aug 19, 2022
Merged

refactor(test): use more specific checks in check-tsconfig spec#398
ezolenko merged 1 commit into
ezolenko:masterfrom
agilgur5:refactor-test-check-tsconfig

Conversation

@agilgur5

@agilgur5 agilgur5 commented Jul 23, 2022

Copy link
Copy Markdown
Collaborator

Summary

Be more precise with the checks in check-tsconfig.spec.ts and reorder things a bit

Details

  • toBeFalsy() was a bit imprecise and always felt as such, especially since checkTsConfig returns void

    • so instead check that it doesn't throw, which matches the test intent
  • reorder the tests a bit to match existing test style: non-errors first, then errors

    • and separating into two different test blocks parallelizes them as well
  • also add an ES2020 check as well

- `toBeFalsy()` was a bit imprecise and always felt as such, especially since `checkTsConfig` returns `void`
  - so instead check that it doesn't throw, which matches the test _intent_

- reorder the tests a bit to match existing test style: non-errors first, then errors
  - and separating into two different test blocks parallelizes them as well

- also add an ES2020 check as well (follow-up to eb1dd17)
@agilgur5 agilgur5 added kind: internal Changes only affect the internals, and _not_ the public API or external-facing docs scope: tests Tests could be improved. Or changes that only affect tests labels Jul 23, 2022
@ezolenko ezolenko merged commit 576558e into ezolenko:master Aug 19, 2022
@agilgur5 agilgur5 deleted the refactor-test-check-tsconfig branch July 2, 2023 21:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind: internal Changes only affect the internals, and _not_ the public API or external-facing docs scope: tests Tests could be improved. Or changes that only affect tests

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants