Your explanation sounds very straightforward to me where it ends at this point. I would imagine you want to confirm that when certain different lists are presented on the inputs, you get sane SQL as the output.
Start with the simplest possible input list, and confirm that the correct SQL comes out, using tests of course. Start to make your lists more complex and confirm that as you do that, your queries keep pace. Do that as far as you can.
When you start to run out of steam there, try the web interface controls and see what other combinations and permutations you can think of for the inputs, and make sure that they produce the right SQL.
You might be able to use SQL::Abstract to reduce the complexity of some of this code -- but I would hold off doing that until you're re-writing this code based on the work you've done building the test suite.
Sounds like fun -- good luck!
Alex / talexb / Toronto
Team website: Forex Chart Monkey, Forex Technical Analysis and Pickpocket Prevention
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds
In reply to Re: Inheriting Bullsh!t
by talexb
in thread Inheriting Bullsh!t
by alaska.saedelere
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |