Skip to content

Commit 86ed945

Browse files
chore(minutes): add 12 Jan 2026 (#3)
1 parent 18fc4c4 commit 86ed945

File tree

1 file changed

+34
-0
lines changed

1 file changed

+34
-0
lines changed
Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
# 12 January 2026
2+
3+
## Attendees
4+
5+
* Alex Vespa [@vespa7](https://github.com/vespa7)
6+
* Jacob Smith [@JakobJingleheimer](https://github.com/JakobJingleheimer) (chair)
7+
* Jordan Harband [@ljharb](https://github.com/ljharb)
8+
* Moshe Atlow [@MoLow](https://github.com/MoLow)
9+
* Pietro Marchini [@pmarchini](https://github.com/pmarchini)
10+
* Vas Sudanagunta [@vassudanagunta](https://github.com/vassudanagunta)
11+
12+
## Topics
13+
14+
* New team repo https://github.com/nodejs/test-runner
15+
* Team Kanban: https://github.com/orgs/nodejs/projects/14
16+
* Name for "expect failure": https://github.com/nodejs/test-runner/discussions/1
17+
* Jacob proposed `flaky`, per https://github.com/nodejs/test-runner/discussions/1#discussioncomment-15468740
18+
19+
## Outcomes
20+
21+
* "Expect failure" feature:
22+
* Consensus reached for name: `expectFailure".
23+
* Widespread agreement on feature behaviour and use-cases.
24+
* Assertion inversion is perhaps not the targeted audience, but there no reason to get in its way. Documentation (likely a Learn article) may call out that use-case, but it's generally accepted to be not the focus.
25+
* Consensus that `flaky` is a desired feature and general agreement on its behaviour/scope.
26+
27+
## Todos
28+
29+
* Need review (@nodejs/test-runner):
30+
* https://github.com/nodejs/node/pull/56490
31+
* https://github.com/nodejs/node/pull/59732
32+
* https://github.com/nodejs/node/pull/59700
33+
* Write feature proposal (@JakobJingleheimer) for `flaky`
34+
* @JakobJingleheimer to support @vespa7 on implementation

0 commit comments

Comments
 (0)