If you haven't alerady, go take a look at "Perl Testing, A Developer's Notebook (Langworth & chromatic), particularly the last chapter ("Testing Everything Else"). There are several tools and tricks that can be applied to testing non-Perl code. Basically, you can treat your C++ as a black box, and wrap it in an eval-block. For a given stimulus, you have an expected response, that you can code for (by examining $@, any temporary files that get written, databases modified, etc.) in a Test::More test harness.
If this were me confronted with this project, I'd strongly consider going down the 'Test' path in parallel with the 'Automation' path. There will be enough cross-talk between the two to make this a very useful approach. The Test path will give you the means to determine and report your C++ code in action, which the Automation path can use to make go/stop and fix/nogo decisions.
----
I Go Back to Sleep, Now.
OGB
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
