Paul, if you are interested in speeding up your tests for either Bun or Jest you might be interested in checking out my latest project. At Brisk we keep pre-built workers for your project in our infrastructure so there is no build time that eats in to your test time. This also means there isn't as much of a concurrency penalty that you get with traditional CI services (scaling up to 30 workers only to spend 30 times as long on building). So we use lots of concurrency (usually around 60 workers) for really really fast tests. I'd love to hear your thoughts. https://brisktest.com/
Interesting, just checked it out. In this case I need to build and run a local (Rust) dev server in the background while the tests run, does Brisk support that?
So if I understand correctly by local you mean on the test runner? So at the beginning you build your CI env and you start a local web server. Then later on when you are running the tests they hit the local web server (on the runner) during the tests?
We do support this yes. With what we call background jobs. Each test runner also comes with a dedicated docker server for running additional services (db, etc). It’s an experimental/new feature though and I haven’t properly figured out how to charge for it.
In the happy case while the worker isn’t running tests the background job should be consuming very little resources.. but we can’t rely on that (and also some people will inevitably try to mine crypto) so figuring out how to make sure the workers aren’t hogging the cpu between test runs has prevented me from broadcasting the existence of the feature, it is there though.
Comments
Paul, if you are interested in speeding up your tests for either Bun or Jest you might be interested in checking out my latest project. At Brisk we keep pre-built workers for your project in our infrastructure so there is no build time that eats in to your test time. This also means there isn't as much of a concurrency penalty that you get with traditional CI services (scaling up to 30 workers only to spend 30 times as long on building). So we use lots of concurrency (usually around 60 workers) for really really fast tests. I'd love to hear your thoughts. https://brisktest.com/
Interesting, just checked it out. In this case I need to build and run a local (Rust) dev server in the background while the tests run, does Brisk support that?
So if I understand correctly by local you mean on the test runner? So at the beginning you build your CI env and you start a local web server. Then later on when you are running the tests they hit the local web server (on the runner) during the tests?
We do support this yes. With what we call background jobs. Each test runner also comes with a dedicated docker server for running additional services (db, etc). It’s an experimental/new feature though and I haven’t properly figured out how to charge for it.
In the happy case while the worker isn’t running tests the background job should be consuming very little resources.. but we can’t rely on that (and also some people will inevitably try to mine crypto) so figuring out how to make sure the workers aren’t hogging the cpu between test runs has prevented me from broadcasting the existence of the feature, it is there though.
Brisk works really well, we’ve had a lot of success since we switched. I wonder if it works with Bun?
It should do, can you point me to an example repo for a bun app and I’ll try it out.