Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??

OK, there might have been a misunderstanding here. And that was my fault, because I didn't specify my requirements and background in detail. I will give some additional details, but I will have to limit it to a high-level overview:

The plan is to use a Perl-based test harness to support the QA and DEV groups of a large company with automated tests. There's something like this in place already, but it has limitations, which is why we're redesigning parts of it. In our environment we have a server running our product and multiple clients accessing this server. This is why we're already using Expect and will most likely also do so in the future. The server itself is not written in Perl, so we're not trying to test Perl code, but the different features of the server instead. This will include functional, error recovery, stress and other tests.

I don't want to go into all the details, because this will become too much to post here. Which doesn't mean that we're not looking into those details ourselves. Here I just wanted to see if others know about CPAN modules I should start looking at, which I might have missed so far. There were a few good tips already, but more are certainly appreciated.


In reply to Re^4: Writing a Test Harness by elTriberium
in thread Writing a Test Harness by elTriberium

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



  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or How to display code and escape characters are good places to start.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others scrutinizing the Monastery: (5)
As of 2024-04-18 01:41 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found