In this series of articles I argue that "black box" testing is insufficient to validate a networked application. Such a program has two ends that take inputs and provide outputs: one is its public API, but the other is its communication over the network. Only by treating it as a black pipe can we test both surfaces.
Traditional "black box" testing can't fully validate MongoDB clients and other connected applications. Here's a convenient way to test the whole program.
The second "black pipe testing" article: testing PyMongo with MockupDB.
The third "black pipe testing" article: testing libmongoc with MockupDB, a wire protocol server written in Python.
The fourth "black pipe testing" article: testing the MongoDB C Driver with mock_server_t.
Fourth in my "black pipe testing" series. How do you test your MongoDB application's reaction to database failures, hangs, and disconnects?
Black pipe testing does not replace other kinds of tests, but there are two scenarios where it shines.