Some of my better test suites are the ones where I've structured the tests along the same lines as the module documentation. So for each section of the documentation, there's a test file with a similar name.
]]>BTW the quality of tests could also be improved by showing tests more prominently in metacpan. Given a start page of a release, such as Moops one needs to manually browse to directory t/. There should be a more readable test documentation page that automatically lists all tests with their purpose. Modules have a short name and description in the NAME section of their POD. One could extract the short description of a test from the PURPOSE section of each test, right?
]]>Also, for what it's worth, given that many projects are under at least two levels deep in the hierarchy, I'm much happier with my current structure (https://github.com/frioux/DBIx-Class-Helpers/tree/master/t) instead of using extra bogus hierarchy layers in tests (https://github.com/frioux/DBIx-Class-Helpers/tree/routine/t/).
]]>WRT my community experience, there are always two ends in a communication and they can be both wrong, mine included (as it often happens). My personal experience was rather bad and this is a reason why I would personally think twice before using the framework outside its "institutional" goal.
@David: I hope that was a funny side effect for you :) Reading old (experience-wise, not age-wise) Perlers like you and Aristotle argue always sounds like Mom and Dad yelling at each other, but it's life. Aristotle's criticism probably helped make XML::Tiny better, which is a good thing anyway (hubris at work?!?) - thank you both :)
]]>While this has always been a goal of the Mojo namespace, perhaps we haven't been clear/loud enough about it. We have made several changes in our documentation to reflect this, most prominently and explicitly in our official mission statement seen here at http://mojolicious.org/perldoc/Mojolicious/Guides/Contributing#Mission-statement but also sprinkled elsewhere.
]]>Thank you very much.
Jim Keenan
%C
didn't exist when I wrote the above.
On a laptop only used by me, I was using /tmp/
(it avoids need to know your username to put in the config), but for shared computers it isn't a good idea.
Then once it's going, we could hook in to things more to get better data. I mentioned the example of cpan downloads.
]]>