Tales from the AntiTestingSide - Master Debugger

Confrontation
Came across a unit test with 2 lines of code. It was the only test in the entire suite. The first line of the test code created an instance of a class. The second line called the Execute() method on that instance. How did this test pass with no Assert methods? Easy. Set a breakpoint on the Execute() method and step through the code.

Ultimatum
Immediately I deleted the lines of code. Banished as if it were pr0n that accidentally popped up while checking out a technology site.

Moral
I'm not sure if I'd want to do the whole debugging a method to inspect code that I've never seen before. In this scenario I wrote a new test and continued on from there. One that actually did something.