configureFailPoint for driver tests
What changes in configureFailPoint for driver tests compared with MongoDB and what your application has to do.
This difference is of the Extension kind.
What MongoDB does
configureFailPoint only exists with enableTestCommands=1.
What TeselaDB does
The same: configureFailPoint with failCommand only exists if you start with --setParameter enableTestCommands=1, off by default.
What your application has to do
Nothing in production. Turn it on only to run the specification tests of a driver.