I think that I have to agree with you ;-)

On the other hand, those test cases designed by the author can only be considered as unit test cases. It must then pass UAT (User Acceptance Testing).

Now talk about UAT, the author of the module shall never influence, not to say design, the UAT test cases. But I understand that as an open forum, each tester (I remember they had/have this role for CPAN) only has very limited amount of time to commit, as everybody has their day time job to do. Think about the numbers of CPAN modules people submit all the time, the idea of having formal UAT is also defeated.

Even if there would be a UAT, the quality of the UAT is again a question, as those people who do the UAT for a module may never use it in their real life, and they don't really care (the level they care is much lower than your real users, who do the UAT and will have to live with the bugs they missed ;-).

Now you are end up with doing the UAT yourself. But for well known modules, the situation is quite different, as lots of people used them before you, which means that lots of people have done UAT for you already.


In reply to Re: Re: A good lesson on Tie (through a negative example) by pg
in thread A good lesson on Tie (through a negative example) by pg

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.