Effective Testing - Show What's Important, Hide the Rest
What we include in a test is as important as what we leave out. Having the right amount of information helps us understand what the test is doing at a glance.
Read on →
What we include in a test is as important as what we leave out. Having the right amount of information helps us understand what the test is doing at a glance.
Read on →
Flaky tests are those that randomly fail for no apparent reason. If you have a flaky test, you might re-run it, over and over, until it succeeds. If you have a couple of them, the chances of all passing at the same time are slim, so maybe you ignore the failures. You know, just this one time… Soon enough, you’re not paying attention to failures on this test suite. Congratulations! Your tests are now worthless.
Read on →
Using expressive assertions can help us figure out why a test fails without having to go through the code.
Read on →
One way to make sure your tests are readable is to have them all adhere to the same structure.
Read on →
Picking good test names can help us identify what’s wrong with our code when something fails.
Read on →
 This week I needed to test a class that depended on a method from an static class. I saw we were using [PowerMock][1] and thought to myself: “Well this sounds pretty common, I bet it’s easy to accomplish”. But of course I ran into half a dozen issues before I was able to make it work. Here’s my two cents to make your experience easier than mine.
Read on →