Vadim Demedes

It seems that this library is meant to be used in browser and adapting it for Ink would be a complicated task. @lucasconstantino If you need something like this, I'd...

> This will flush out any interdependencies per test. I believe it is already being done, as we start all tests at the same time and running them in parallel....

Hmm, wasn't `.always` supposed to serve this exact same purpose? To always run the clean up task, regardless of previous failure? Perhaps it's worth fixing the existing modifier, instead of...

I think `--no-cleanup` may be a wrong way to approach this issue. I agree with this statement of @sholladay: > I don't see the logic in skipping .afterEach when a...

Yeah... Looks like there's no win-win solution at the moment for this.

I think it has some potential as a feature request. Something like `describe` in mocha. At the moment, we'd like to merge currently open PRs and do a complete cleanup/refactoring,...

Here's a recap of all proposed APIs, I think it'll make it easier to pick a winner and continue the discussion. #### 1. `test.group()` with nesting by @novemberborn ``` js...

@sotojuan Good point, totally agree. I think we should make `t` extendable with custom methods (assertions). Was thinking to create a separate module for `t.jsxEqual()`, would be nice to make...

@odigity section "Custom Assertions" in readme is actually related to using 3rd-party assertion libraries, like [expect](https://github.com/mjackson/expect) or [chai](https://github.com/chaijs/chai), not extending `t` with custom assertions. I understand the confusion, I think...

> Cleanup code should be in the after/afterEach hooks, so why not run them when tests are cancelled? Exactly what should be done. I imagine sending "abort" event to forked...