Beefy Boxes and Bandwidth Generously Provided by pair Networks
There's more than one way to do things
 
PerlMonks  

comment on

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

Dear Master Monks,
I have a web application I need to test, and wanted some advice before I start writing. I have two ideas that follow;

1. Custom Module:

  • Contains all the functions I would like to test e.g. uploads, logging in, navigation etc.
  • Tested via simple ok tests with Test::Simple or if it gets a bit more complicated, via Test::More
  • Seperate program that uses this module to run the tests
  • Create Module with Module::Starter

2. Perl Test files:

  • Each .t is a test for a feature of the web application
  • Seperate program that calls prove to run them all

I have recently bought Perl Testing: A Developer's Notebook and Perl Best Practices, so they will probably help me out on the finer points ;-)

I think that maybe 1. would be the best way to go, as it would be a proper module, easier to manage, but might duplicate testing, i.e. testing the test functions. But then again, you can't test enough.

I will probably be using a bit of WWW::Mechanize and HTTP::Recorder to start me off.

I know a lot of Monks would have been in the same situation as me at some point, so if one of you kind souls would put me on the right path, I would be very grateful.

Thanks,
Gavin.

Walking the road to enlightenment... I found a penguin and a camel on the way.....
Fancy a yourname@perl.me.uk? Just ask!!!

In reply to Application Testing: Custom Module or Perl Test Files? by ghenry

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 imbibing at the Monastery: (4)
As of 2024-04-24 07:58 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found