Hi,

As I'm getting more familiar with the whole QA infrastructure
I was looking at http://qa.perl.org/ to check what people
would see if they used this as a starting point to learn about
perl module testing.

A few days ago I got a pull request for one of my modules from
someone new to perl testing.
He showed what he did:
    find ./t -maxdepth 1 -type f | while read file; do echo $file; perl -I ./lib 
$file; done |& less

Of course that does the job but knowing `prove` would have helped ;-)

On qa.perl.org there's lots of information - most is kind of hidden
in the wiki which you will find behind a small link at the bottom of the
page. (Honestly, who of you did know that this wiki existed?)

But the last change there was April 2013. And we all know that
wikis are great for saving informations very fast and easy, but they tend
to scatter unless you put a lot of work into tidying, categorizing.

Also I think a starting page could give a quick overview of the
various themes around QA, maybe with a graph.
Andreas Koenig pointed me to http://www.cpan.org/misc/ZCAN.html where I could
find a graph from 2002.

Ideally you would go from there to te pages you're searching for.

Examples:
I'm a new module author - point to basic module setup tutorial (not
totally QA related)
I'm a module author and want to start writing tests - point to basic
testing steps.
I want to be a CPAN smoker - ...
I'm just a user of a module and want to know about the infrastructure.

I would be willing to put a little work into this and are happy about
suggestions and help.
One question is:
Should we keep the wiki and tidy it up?
Or should we rather use github to edit the site?
https://github.com/perlorg/perlweb/tree/master/docs/qa
The advantage of a wiki is that anyone can sign up and edit easily.
It has builtin search functionality.
On the other hand it's PHP but do we have something similar in Perl?

Also we should ask the wiki hoster/maintainer if we can keep on using it.

Thanks for your time,
tina

Reply via email to