Steven Silvester

We have a `testutils` [package](https://github.com/jupyterlab/jupyterlab/tree/master/testutils) that has among other things: - A JS wrapper for a Jupyter [Server](https://github.com/jupyterlab/jupyterlab/blob/b0a1ca62628a0b450ecec483c2f7aca6457d3b32/testutils/src/start_jupyter_server.ts#L34) - Mock objects for [Kernels](https://github.com/jupyterlab/jupyterlab/blob/b0a1ca62628a0b450ecec483c2f7aca6457d3b32/testutils/src/mock.ts#L153) etc. - Utilities for working with [notebooks](https://github.com/jupyterlab/jupyterlab/blob/master/testutils/src/notebook-utils.ts)...

Sounds good, what time is good for you on Wednesday? I don't have anything until the Notebook meeting at 1530 UTC.

Just catching up on this thread, I support a JEP to make this a Jupyter project. It could live in its own org like [xeus](https://github.com/jupyter/enhancement-proposals/pull/44).

Ah, good call out, thanks!

#809 fixes the typing

#809 is merged, but there's now a conflict.

Server 2.0.1 has a fix for that, I kicked the build to see if we pick it up.

Nope, it must be taking a while to propagate.

I think I need to start from a new PR, the merge resolve is too messy.

We still have a check for an existing kernel [here](https://github.com/jupyter/jupyter_client/blob/7db82906096de3465a8b85f012d471ae4156eebe/jupyter_client/manager.py#L593). @Zsailer what do you think of adding a ready wait there?