feat(circus): added each to failing tests

CHANGELOG.md

@@ -3,6 +3,7 @@
 ### Features
 
 - `[expect]` [**BREAKING**] Differentiate between `MatcherContext` `MatcherUtils` and `MatcherState` types ([#13141](https://github.com/facebook/jest/pull/13141))
+- `[jest-circus]` Add `each` for failing tests ([#13142](https://github.com/facebook/jest/pull/13142)). It adds this functionality on top of previously added `failing` feature in ([#12610](https://github.com/facebook/jest/pull/12610)).
 - `[jest-config]` [**BREAKING**] Make `snapshotFormat` default to `escapeString: false` and `printBasicPrototype: false` ([#13036](https://github.com/facebook/jest/pull/13036))
 - `[jest-environment-jsdom]` [**BREAKING**] Upgrade to `jsdom@20` ([#13037](https://github.com/facebook/jest/pull/13037), [#13058](https://github.com/facebook/jest/pull/13058))
 - `[@jest/globals]` Add `jest.Mocked`, `jest.MockedClass`, `jest.MockedFunction` and `jest.MockedObject` utility types ([#12727](https://github.com/facebook/jest/pull/12727))

docs/GlobalAPI.md

@@ -735,17 +735,11 @@ test.each`
 
 Also under the alias: `it.failing(name, fn, timeout)`
 
-:::note
-
-This is only available with the default [jest-circus](https://github.com/facebook/jest/tree/main/packages/jest-circus) runner.
-
-:::
+> Note: This is only available with the default [jest-circus](https://github.com/facebook/jest/tree/main/packages/jest-circus) runner.
 
 Use `test.failing` when you are writing a test and expecting it to fail. These tests will behave the other way normal tests do. If `failing` test will throw any errors then it will pass. If it does not throw it will fail.
 
-:::tip
-
-You can use this type of tests i.e. when writing code in a BDD way. In that case the tests will not show up as failing until they pass. Then you can just remove the `failing` modifier to make them pass.
+> Tip: You can use this type of tests i.e. when writing code in a BDD way. In that case the tests will not show up as failing until they pass. Then you can just remove the `failing` modifier to make them pass.
 
 It can also be a nice way to contribute failing tests to a project, even if you don't know how to fix the bug.
 
@@ -763,6 +757,22 @@ test.failing('it is equal', () => {
 });
 ```
 
+### `test.failing.each(name, fn, timeout)`
+
+We can also run multiple tests at once by adding `each` after `failing`.
+
+Example:
+
+```js
+test.failing.each([
+    {a: 1, b: 1, expected: 2},
+    {a: 1, b: 2, expected: 3},
+    {a: 2, b: 1, expected: 3},
+  ])('.add($a, $b)', ({a, b, expected}) => {
+    expect(a + b).toBe(expected);
+  });
+```
+
 ### `test.only.failing(name, fn, timeout)`
 
 Also under the aliases: `it.only.failing(name, fn, timeout)`, `fit.failing(name, fn, timeout)`