<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:Tahoma;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:#606420;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:Arial;
color:windowtext;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink="#606420">
<div class=Section1>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Hi,<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>We are using Drools 3.0.6 using a test-driven approach.
This works really well in allowing us to get good test coverage around our
rules and to create those rules rather easily. However, as the number of tests
grows, the execution speed of the test suite in our Continous Integration
environment is taking longer and longer (expected, I know).<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>We’ve broken our rules out into separate .drl files
and try to test them in isolation by instantiating a new WorkingMemory in the setup
method of each test and then setting the WorkingMemory variable to null in the tearDown
method.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Is there a way to re-use the WorkingMemory object such that
we don’t have to create a new one, at the start of a test, and have it
garbage-collected, at the end? How are others doing similar things? Our goal
is to reduce the execution time of our testsuite.</span></font><strong><b><font
face=Tahoma><span style='font-family:Tahoma'><o:p></o:p></span></font></b></strong></p>
<p class=MsoNormal><strong><b><font size=2 face=Tahoma><span style='font-size:
10.0pt;font-family:Tahoma'><o:p> </o:p></span></font></b></strong></p>
<p class=MsoNormal><strong><b><font size=2 face=Tahoma><span style='font-size:
10.0pt;font-family:Tahoma;font-weight:normal'>Thanks for any and all replies.<o:p></o:p></span></font></b></strong></p>
<p class=MsoNormal><strong><b><font size=2 face=Tahoma><span style='font-size:
10.0pt;font-family:Tahoma;font-weight:normal'><o:p> </o:p></span></font></b></strong></p>
<p class=MsoNormal><strong><b><font size=2 face=Tahoma><span style='font-size:
10.0pt;font-family:Tahoma;font-weight:normal'>John</span></font></b></strong><o:p></o:p></p>
<p class=MsoNormal><font size=2 face=Tahoma><o:p> </o:p></font></p>
</div>
</body>
</html>