Its long been known that the closer your documentation is to the code it documents, the more likely it will be kept up to date and the more accurate it will be. Perl has POD for this purpose, allowing us to intermingle docs and code as we please. But what about tests? Shouldn't a test be close to the code it’s testing?

Pod::Tests and the accompanying pod2test squeeze one more feature out of POD by allowing tests to be embedded right next to the code its testing and the documentation its validating! As an added bonus, it’s also possible to test example code in your documentation. And with no performance penalties!

We'll show how this was pulled off, how it is used in concert with traditional tests, how it is made to work *without* Pod::Tests installed, and how it makes the unglamorous job of writing tests a bit more palatable than licking all the bathrooms in Grand Central Station.