Re^5: RFC - Documentation Review

In general, if you don't want to test something, change the test; don't change the code to avoid the test.

See Test::Pod::Coverage. There's an example using also_private. There's also a link to Pod::Coverage with lots more examples of how to avoid needing to document subroutines.

— Ken

Comment on Re^5: RFC - Documentation Review Download Code

Replies are listed 'Best First'.
Re^6: RFC - Documentation Review by Bod (Parson) on Jun 05, 2023 at 08:47 UTC
In general, if you don't want to test something, change the test; don't change the code to avoid the test. Yes that makes sense. But in this case, your previous reply made me realise that `test` is a private ^* method and should be marked as such. It will also be removed when I have cured the bug which it is there to debug. So will not be in the production release of the module ^* private in the sense than only me and my test code will use it, not private in that it is only called from within the module.	[reply] [d/l]

Replies are listed 'Best First'.

Re^6: RFC - Documentation Review
by Bod (Parson) on Jun 05, 2023 at 08:47 UTC

In general, if you don't want to test something, change the test; don't change the code to avoid the test.

Yes that makes sense.
But in this case, your previous reply made me realise that test is a private ^* method and should be marked as such. It will also be removed when I have cured the bug which it is there to debug. So will not be in the production release of the module

^* private in the sense than only me and my test code will use it, not private in that it is only called from within the module.

[reply]
[d/l]