Josh's team has an offshore group that "helps" with development tasks. Since they often provide code that doesn't do what it's supposed to do, they've started mandating unit test coverage. So, for the first round, they did do exactly what Josh's team asked - the offshore group provided 75% unit test coverage across all classes...and 0 assertions.

So, Josh's team explained what assertions were, and how they worked, and why they're important, and specifically that there needed to be more of them.

A while later, the offshore team made their changes and sent back a few hundred unit tests that followed this pattern: 

Object o = new Object();
o.setName('[OBJECT NAME HERE]');
assertEquals('[OBJECT NAME HERE]', o.getName());

// ... remainder of unit test follows.  With no more assertions.

On the bright side, Josh's team can be assured that the setters and getters of a handful of sporadic, random objects work perfectly.

[Advertisement] BuildMaster allows you to create a self-service release management platform that allows different teams to manage their applications. Explore how!