in reply to Re^2: Careful with Test::Pod::Coverage
in thread Careful with Test::Pod::Coverage
Some tests are not there just to ensure that things are working, but rather to ensure the user that the author did take his time to do things properly.Running a test doesn't say anything more than that the author managed to write code that produced output in the form:
If you want to know the author did things properly, you'd run your tests, not the authors.print 1..3 ok 1 ok 2 ok 3
I, for one, enjoy seeing that the author took the time to make sure he was documenting every single function in his code.I'd rather see a manual page that documents the API. Not every function belongs to the API - the more complex a functionality is that a module delivers, the lower the ratio of API functions vs total number of functions will be. Documenting functions belongs in source code comments. POD is user documentation.
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re^4: Careful with Test::Pod::Coverage
by tirwhan (Abbot) on Nov 14, 2005 at 11:11 UTC | |
|
Re^4: Careful with Test::Pod::Coverage
by demerphq (Chancellor) on Nov 14, 2005 at 11:37 UTC |