Sean Reilly

We've been running a private Rails Beta (thanks to everyone who has given us awesome feedback). It's time now to open up access to the general public. Our private beta users mostly use rspec so that is the default setup at the moment. However Minitest also works fine. Current beta

We've been running a private Python Beta for a while now and it's time to release it into the wild. Our private beta users mostly use pytest so that is the default setup at the moment. Combined with pytest-split (which comes pre-installed on the image) we have a really simple

“If I would have asked people what they wanted, they would have said faster horses.” Something Henry Ford never said, but it’s fun to pretend he did. What does it mean? That prospective users of your product can’t conceive of the innovation you are creating and would just

To verify that our code works before we commit it. Why not just commit and wait for the CI to tell us if we passed or failed? Because it is slow and interrupts developer momentum. This combination of slowness and interruption to your flow is extremely costly for productivity. Here

Brisk is a new way of running your tests from your terminal. It makes running your tests from your local machine extremely fast. When you run your tests with Brisk we sync your development directory and distribute your tests among our remote workers streaming the results back into your terminal.

A lot of people are confused about the difference between the various types of tests that you can write. There is a lot of overlap in definitions, terminology and abstractions so we are going to keep things simple here and just define the two most basic types of test, Unit

Running test suites has become so slow and unwieldy that nobody runs them locally anymore. Running your test suite locally takes a large quantity of time, turns your computer into a hot mess, renders it completely unusable or all of the above. It doesn't have to be this way. Enter