Hi Dag, It is more an issue of documentation of how quality assurance is done for Perl. Our procedures for QA require that when doing QA on a model or program we have created (my ultimate goal), any software used by that program must also have gone through a sufficiently rigorous QA process. For other programs I have been able to find documentation on their QA program that includes standard practices, problem reporting, code control, records management, etc. They also have documentation describing the V&V tests performed with tolerances and results outlined.
I understand that an open source product works differently than a product developed by a single entity, but I have no way to get my QA Manager to sign off on use of Perl without some documentation for the QA practices used. I personally believe that the testing done on Perl is far more extensive than on most software, but I need to be able to prove that with documents...this is my problem. Thanks, Tracy Radel Nuclear Engineer SHINE Medical Technologies tracy.ra...@shinemed.com From: Dag Rowe [mailto:r...@pythian.com] Sent: Wednesday, July 31, 2013 3:20 PM To: Shlomi Fish Cc: Tracy Radel; perl-qa@perl.org Subject: Re: QA for Perl Hi Tracy, QA on the install of Perl Can you clarify your intent? Shlomi has given a solution to confirm that the perl.exe binary passes its unit tests. This can be extended to library modules, you can confirm they are working as the developer intended by running the unit tests at install time. However, I'm wondering if your question is more about configuration management. Are you looking to confirm that you have the same library modules and module versions, when you have a test run of your script? If so, one option is setting up a private cpan mirror for installations of Perl, and Perl dependencies, where you organization can control the versions of the modules. You would then know that a QA run of your script version x.x, using versioned modules X, Y, and Z passed. This should confirm the script's functionality as the customer intends to use it. You can also look at Pinto and Carton on metacpan.org<http://metacpan.org> for dependency management. Other options: enforce minimum versions with Perl use statements in the code, or enforce versions in makefiles at deploy time. Hope that helps, Dag Rowe QA Analyst, Team Lead Pythian - Love your data On 31 July 2013 12:49, Shlomi Fish <shlo...@shlomifish.org<mailto:shlo...@shlomifish.org>> wrote: Hi Tracy, On Wed, 31 Jul 2013 15:29:18 +0000 Tracy Radel <tracy.ra...@shinemed.com<mailto:tracy.ra...@shinemed.com>> wrote: > Hello, > I'm looking for information on quality assurance documentation for basic > Perl. I am trying to do QA on a Perl script that we wrote, but before I can > do this I need to do QA on the install of Perl. I've been searching for > hours online and cannot find QA or V&V documents for Perl. Do any of you > know where I might find this documentation, if it exists? If not, do you > know how other companies have dealt with QA for the installation of Perl? > The perl core (= the Perl 5 implementation) contains a comprehensive test suite, that contains over half-a-million (> 500,000) test assertions for testing perl on the host system. To run it, build perl and type "make test". I'm not sure what's the easy way to run it on a perl binary that was already installed to the system, but it should be doable. Make sure you run the test suite of the version that corresponds to the version of perl that you installed. Hope it helps. Regards, Shlomi Fish > Thanks, > > Tracy Radel > Nuclear Engineer > SHINE Medical Technologies > tracy.ra...@shinemed.com<mailto:tracy.ra...@shinemed.com> -- ----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ Selina Mandrake - The Slayer (Buffy parody) - http://shlom.in/selina I feel much better, now that I've given up hope. - Ashleigh Brilliant Please reply to list if it's a mailing list post - http://shlom.in/reply . --
