We're Testing Your Patience...

Testing Tools

The hosts discuss various testing tools, highlighting their favorite ones. Joe Zack mentions DotCover, a JetBrains product, which he appreciates for its visual representation of code coverage. He explains how it highlights tested code in green and untested code in red, making it easier to identify gaps 1.

You can see the code coverage from like a bar graph percentage kind of point of view. But what's also cool, too, is it's almost like running a highlighter over your monitor.

--- Joe Zack

Alan Underwood also shares his recent experience with the Microsoft Sculpt Ergonomic Keyboard, praising its comfort despite some minor drawbacks 1.

   

Unit Test Structure

Joe elaborates on structuring unit tests, referencing Phil Haack's method of creating a test class for each method and separate test methods for different scenarios. He combines this with Roy Osherove's naming convention, which includes the method under test, the scenario, and the expected result 2.

You name it so that it's method under test scenario, expected results. So in the add method that I mentioned, I might have the add test class like Phil hack had suggested, but one of the methods might be named something like add valid integers returns valid integer as the name.

--- Joe Zack

This approach provides clarity for future developers, making it easier to understand what each test is verifying 2.