You can use JUnit, create a session, insert facts, call fireXY(),... Asserting the correct result may
be done by inspecting the WM or listening to events or whatever your app suggests.
-W


On 12 November 2010 11:45, Ayush <ayush.vatsyayan@alcatel-lucent.com> wrote:

oh yes Thanks this rule will solve my problem.

I'm wondering is there any way I can actually verify the business logic of
my rules. I'd read about drools-verifier but I've not found enough
information for it to be used with drl. I want that  in some way I can check
the business logic from java classes?
--
View this message in context: http://drools-java-rules-engine.46999.n3.nabble.com/Removing-facts-from-statefulknowledgeSession-s-memory-tp1875795p1888151.html
Sent from the Drools - User mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users