One of the hardest problems in writing automated programmer tests is isolation: simulating the environment in which a unit exists in production, in order to precisely (and efficiently) put it through its paces.
In this module, we'll address several types of isolation: from the concurrent thread-scheduling system, from IO and the filesystem, and more.
There was a problem reporting this post.
Please confirm you want to block this member.
You will no longer be able to:
Please allow a few minutes for this process to complete.