Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

comment on

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

Sounds like you don't want to go with the traditional methods of testing (of which volumes and volumes have been published). Here's my .02 non-traditional approach:

for users finding something wrong: have good logging - don't depend on the users for 100%. Write decent well formatted and consistent error messages so log parsing will be easier.

for missing features: have a good user feedback mechanism - have a "report problem/suggest feature" link on each page. Also make sure the copy "leads" the users to use the link (don't bury it - at least not in the begginning).

How to make it faster. Combine the logging with good timing stats. You should have an inkling of where your bottlenecks will be (database calls, transforming xml, etc). Start logging those hotspots to generate some stats. Maybe they are bottlenecks, maybe not - you'll need some historical data to let you know what's normal and what's not.

I think if you have consistent well thought out logging (that includes having the mail go to some alias with a canned subject) you should have the foundation necessary to programmaticaly monitor the health of your app.

-derby


In reply to Re: How do I test a CGI program properly? by derby
in thread How do I test a CGI program properly? by ajt

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 meditating upon the Monastery: (6)
As of 2024-03-28 08:51 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found