Running Tests Asynchronously
In most Destroy All Software screencasts, the tests are run synchronously: the test process is forked from the editor and blocks the terminal. This screencast shows another option: running tests asynchronously in another split. First, we use tmux, which is a common approach. Then, we do it using Unix primitives: a named pipe to communicate between the two windows, and a shell script to manage the communication.