Hopefully, most of your core functionality is in modules and abstracted from the presentation. If so, you can do a lot of testing without worring about pretending you're a browser.
As far as adding tests to an existing codebase, In addition to the book mentioned above, Perl Medic has a decent section.
When I've been in a similar situation, I've tried to add the simplest test(s) possible without changing the existing code at all, and then slowly re-factored the code to make it more test friendly (if needed) while keeping the original tests in place to verify nothing's been broken. Usually when I'm up against code without tests, I didn't write it, so you may be a step ahead in that regard.
-
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.
|
