Not having installed any of the shale POMs lately (*-1.0.4-SNAPSHOT), things ran well after I installed those.

Looks good, this is exciting stuff!


--
James Mitchell
678.910.8017




On Sep 12, 2006, at 10:12 PM, Craig McClanahan wrote:

On 9/12/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:

On 9/11/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
>
<snip-entire-email/>

:-)

> PS: Now, on to getting the SCXML implementation up to date with the API
> changes ...
>
<snap/>

Should be more or less there now. I've created a test app for the
SCXML bits as well, all feedback on that is welcome.

Can someone please confirm the integration tests work, I'm out of time (and please also point me to the wiki / web page or the mvn command to
run those ;-)


First, ou'll need to have the cargo plugin properly configured for this to work (telling it where you have Tomcat installed). I've got the following
in my ~/.m2/settings.xml file:

 <profiles>
   <profile>
     <id>cargo-config</id>
     <properties>
       <cargo.container.home>/home/craigmcc/apache-tomcat-5.5.17
</cargo.container.home>
     </properties>
   </profile>
 </profiles>

 <activeProfiles>
   <activeProfile>cargo-config</activeProfile>
 </activeProfiles>

Then, it's just a matter of:

   cd shale-test-dialog2-scxml
   mvn -Pitest install

and it'll run both the unit tests (if any) and the integration tests. For the latter, the test case is set up to use Cargo to start Tomcat for you
automatically, run the tests in it, and then shut down.


BTW, in split frame mode, both frames point to the same child dialog
(popup) which probably needs a thought or two.


Yah, that's probably not the right thing to do.

But, as far as I can tell, everything in shale-test-dialog2-scxml seems to work fine ... including the integration tests. To avoid duplication, we
might want to think about using Maven profiles to let you use the same
application to test either implementation ... the only thing we should (in theory) need to duplicate for that is to have both sets of configuration resources installed in it. We'd likely still need the separate webapps to test any features that are unique to one implementation or the other, too.

-Rahul


Craig

Reply via email to