bdd testing it.todo

[hesxenon]

Is your feature request related to a problem? Please describe.

I'm currently in the process of migrating some of my libraries to deno and noticed that it.todo and describe.todo are not available (yet). I really like to specify my requirements ahead of time because doing so helps me see when I have too many "open" cases that are not yet tested.

Describe the solution you'd like

.todo functions should allow me to specify test cases without providing an implementation. Running deno test with .todo tests or suites should output the tests that are still todo in a group at the end to aid reading the test results.

Describe alternatives you've considered

using it.skip with a noop implementation. But that doesn't show me which tests are actually being skipped and which are still todo.

[eryue0220]

I would try to solve this.

[WWRS]

Deno's it tests use Deno.test internally, so matching Jest's behavior here might require changing Deno.test.

Considering https://github.com/denoland/deno/pull/29222 just merged, I would say it's worth opening an issue in that repo.

[eryue0220]

@WWRS Great, I'll open another PR to support this change.