Christopher Hiller

@craigtaub if you want to look at this, please assign to yourself

to be clear: LoopBack team is at IBM and the TypeScript team is the TypeScript team. 😄

The LB team doesn't want this _per se_; it's a means to an end. Quoting @bajtos: > A watch mode that's using code coverage to determine which tests to re-run...

I've looked at `node-tap`'s implementation, and it seems the information we need is generated by `nyc` and placed into a JSON file, which we can then read to determine which...

..._and_ we could add an option (e.g., `--changed`) which would check this file and only re-run affected tests--no watch mode necessary.

--changed would theoretically work w CI, assuming you cache the cache file 🙂

this is not going to be easy

sorry, butt-closed this one yargs has support for this via `.env()` which we _should_ be able to leverage.

in my experience, it's never that easy, but I wish you luck regardless 😅

@craigtaub Your example is _not_ a problem. writing that JS another way: ```js done(); throw new Error(); done(); ``` You wouldn't expect the second `done()` to be called 😄 @feckertson...