feat(testing/unstable): add it.todo test.todo and describe.todo API

[eryue0220]

This pr is to solve #5711 to add new todo api for test suite methods.

[kt3k]

We have policy to add new features as unstable APIs first. https://github.com/denoland/std/blob/main/.github/CONTRIBUTING.md#suggesting-a-new-feature

Can you create a new file unstable_bdd.ts, re-export API from bdd.ts in there, and add these new APIs in unstable_bdd.ts?

[eryue0220]

We have policy to add new features as unstable APIs first. https://github.com/denoland/std/blob/main/.github/CONTRIBUTING.md#suggesting-a-new-feature

Can you create a new file unstable_bdd.ts, re-export API from bdd.ts in there, and add these new APIs in unstable_bdd.ts?

Sure, I'll update.

[eryue0220]

@kt3k It seems there has a little problem, the describe.todo and test.todo are static method, if move them into another file, then the calling format will become like the following code:

import { describe } from "@std/testing/bdd"
import "@std/testing/unstable-bdd"

// then we can call `describe.todo`
describe.todo(/* function params */);

[kt3k]

How about re-exporting all bdd APIs from unstable-bdd with additional APIs added?

import { describe } from "@std/testing/unstable-bdd"

// then we can call `describe.todo`
describe.todo(/* function params */);

[eryue0220]

How about re-exporting all bdd APIs from unstable-bdd with additional APIs added?

import { describe } from "@std/testing/unstable-bdd"

// then we can call `describe.todo`
describe.todo(/* function params */);

Ohh, that's right

[eryue0220]

How about re-exporting all bdd APIs from unstable-bdd with additional APIs added?

import { describe } from "@std/testing/unstable-bdd"

// then we can call `describe.todo`
describe.todo(/* function params */);

It seems not working, according to the ci, this will throw an error:

TS2440 [ERROR]: Import declaration conflicts with local declaration of 'describe'.

[eryue0220]

Or rename the describe to unstable_describe?

[kt3k]

@eryue0220 I resolved the type errors in unstable_bdd.ts. Can you continue on other part? (I couldn't figure out the fixes for assertMinimumDescribeOptions and assertMinimumItOptions)

[eryue0220]

@eryue0220 I resolved the type errors in unstable_bdd.ts. Can you continue on other part? (I couldn't figure out the fixes for assertMinimumDescribeOptions and assertMinimumItOptions)

Sure, because the params has a bit difference, one (assertMinimumItOptions) is access an array of fns, and the other is not.

[codecov]

Codecov Report

❌ Patch coverage is 82.30769% with 23 lines in your changes missing coverage. Please review.
✅ Project coverage is 94.11%. Comparing base (709c93b) to head (a07cd09).
⚠️ Report is 33 commits behind head on main.

Files with missing lines	Patch %	Lines
testing/_test_helpers.ts	80.00%	23 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6712      +/-   ##
==========================================
- Coverage   94.15%   94.11%   -0.04%     
==========================================
  Files         587      588       +1     
  Lines       42467    42597     +130     
  Branches     6702     6702              
==========================================
+ Hits        39984    40091     +107     
- Misses       2434     2457      +23     
  Partials       49       49              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[kt3k]

Sorry for the delay in review!

LGTM!