Somehow this problem is by design
Indeed.
but I wonder if there is a way to avoid this.
My favourite solution is to make the script such a shallow and simple wrapper around a module (and put all the logic into the module) that it doesn't really need any testing. Consider 
#!/usr/bin/perl
use NaServer qw(run);
run(@ARGV);

[download]

And then do all the testing on NaServer::run instead. Since it's located in a module, you just use it once in the test script, apply the monkey patching you need, and just test as usual.

Other solution:

1) put a package YourPackage; in front of the string you eval, and after the run clean the namespace with an appropriate CPAN module

2) just as 1), but use a separate package name for each run, thus avoidng name collisions.

Perl 6 - links to (nearly) everything that is Perl 6.

In reply to Re: string-eval code more than once by moritz
in thread string-eval code more than once by LANTI

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.