test_runner: export describe and it - #43420
Conversation
describe and itdescribe and it
|
I would love to recieve initial feedback, before I start working on tests and documentation |
|
Initial feedback is positive :) @nodejs/test_runner |
|
cc @Linkgoron |
e9ea260 to
6a8249e
Compare
|
@cjihrig can you please take a look? |
6a8249e to
561565d
Compare
aduh95
left a comment
There was a problem hiding this comment.
I think we would need to also update the docs.
|
@benjamingr AFAIK this pr is ready for review and landing, if you can please review and ping whom you think might be relevant |
|
@nodejs/build can someone with access to the build machines take a look at the failure? |
this seems to be broken for a while https://ci.nodejs.org/job/node-cross-compile/ |
|
FYI,@richardlau is investigating the node-cross-compile failure. I created a issue for this: nodejs/build#2977 |
|
Landed in e2225ba 🎉 |
PR-URL: nodejs/node#43420 Refs: nodejs/node#43415 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
PR-URL: nodejs/node#43420 Refs: nodejs/node#43415 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
PR-URL: nodejs/node#43420 Refs: nodejs/node#43415 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
PR-URL: nodejs/node#43420 Refs: nodejs/node#43415 Reviewed-By: Benjamin Gruenbaum <benjamingr@gmail.com>
Refs: #43415
also, once #43403 is handled - it can probably be a good idea to implement/export a top-level implementation of
before,beforeEach,after,afterEachwhere the parent test is found usingexecutionAsyncId- the same way it is done in this PR