Testing A Rules Engine (Jess)
Does anyone have experience testing a rules engine? I am currently testing a rules engine developed in Jess, and am having issues with coming up with how to approach the testing.
The rules engine is essentially a logging engine. As the logging for different message (xml) types is different per client, and configurable (even in production) I am having issues defining where/what to test. Any assistance on defining the boundaries of my testing would be appriciated.
Re: Testing A Rules Engine (Jess)
Hmmm...last time I tested an "expert system" (more years ago than I like to remember), all I recall is spending a lot of time going through documentation and source code to identify every rule, then coming up with manual test cases that would, together, fire every one of the rules at one point or another. Not the most enjoyable thing I ever had to do, though seeing the system in action was pretty cool.
So now the notion hits me, could you write a Jess script that would derive test cases for your Jess AUT? And if you like recurssion, it could therefore tell you how to test itself, too. [img]images/icons/smile.gif[/img]
[i]...Sound trumpets! Every trumpet in the host! / Sixty thousand, on these words, sound, so high the mountains sound, and the valleys resound.</i] (The Song of Roland)