Beefy Boxes and Bandwidth Generously Provided by pair Networks
Do you know where your variables are?
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
All tests revolve about the same thing: you have a piece of functionality (often a subroutine, but it could also be an operator or a program). You give whatever you are testing some known input, and you check whether the output is what you expect it is. If there's a difference, the test fails. As for a templating system, you can do several things. You could consider the template to be part of the product to test, which means you need to modify the tests if you change the template. Or you consider the templates to be input. Which means you probably have to multiply the number of tests with a factor X, and your tests have to be very generic. Or you could have two sets of test: one for the template you are using (meaning you need to change those tests if the template changes) and another set of tests for the functionality, using several different templates as input. I'd go for the last option - it's more work, but it covers things best.
I'm just confused, I guess what I'm really looking for is "real world" examples of tests for complex things, things you can just test by calling a function and comparing it's output to a constant.
Don't get the impression that writing tests for complex things is easy. It might in some cases, but it often isn't. For some projects, I spend more than 80% of the time on writing the test cases.

Abigail


In reply to Re: Yet another meditation on testing by Abigail-II
in thread Yet another meditation on testing by BUU

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 avoiding work at the Monastery: (10)
As of 2024-03-28 12:06 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found