I have't tested the client side of things so I can't comment much on that.
Others in our group have used a Mock Object architecture to test our Turbine
Action classes.  

I am using cactus with WlS 6.1 testing EJB's ok.  No wrappers around
anything on cactus has been needed for me. As far as what to do to
successfully run tests, I've found it's always best to start at the
beginning.
        - Create a new wls domain - testdomain perhaps
        - create a hello world ejb which has maybe one method returning a
string. no database or other stuff to complicate things.
        - write a cactus test class for that ejb.
        - build and deploy your helloworld ejb to your testdomain. create a
very empty cactified war which includes only your HelloWorldTest.class.
        - decide easiest way to run the tests.  getting cactus to start and
stop the servers takes some setup. 
                you can manually start/stop them, and run through the
browser, but you'll need to merge in the ServletTestrunner stuff (I haven't
looked at latest nightlies to see if that's included yet by default).  
                or, you can manually start/stop them and use an ant task to
run the tests.  here's part of a target i use for testing through ant:

    <cactus fork="yes" warfile="${internet.deploy.dir}/test.war"
printsummary="withOutAndErr">
      <formatter type="xml" />
      <classpath>
        <path refid="weblogic.classpath" />
        <pathelement location="${base.webapp.web-inf.classes}" />
      </classpath>
      <containerset>
        <generic name="${internet.server.name}"
port="${internet.domain.port}" />
      </containerset>
      <batchtest todir="${internet.deploy.dir}/testResults">
        <fileset dir="${base.webapp.web-inf.classes}">
          <include name="**/EventSubmit*Test.class" />
        </fileset>
      </batchtest>

        later you can add start/stop targets and use the runservertests to
run your tests against any wls domain, but i think there's too many things
that can go wrong with trying to implement all that to try and debug the
environment.  

good luck with your testing!

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, November 12, 2003 10:26 AM
> To: Cactus Users List
> Subject: Cactus with weblogic 6.1
> 
> 
> 
> Has anyone tried using Cactus with Weblogic 6.1 ? Did you 
> have to write a
> wrapper around the ServletRedirector class?? I am unable to 
> get my tests to
> start..
> 
> I have followed the setup documentation in the jakarta cactus 
> site, but I
> got lost in all the information there. Can someone help with a list of
> things to do before being able to run the tests correctly?
> 
> We use the MVC framework (MVCSoft) for the client side of our 
> application.
> Velocity pages talking to Action Beans talking to the EJBs. How can I
> isolate unit tests for the client side ( Velocity --> 
> ActionBeans) from my
> server ( EJB- session/entity) unit tests, using Cactus??
> 
> Thanks,
> NP
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
> ---
> Incoming mail is certified Virus Free.
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.532 / Virus Database: 326 - Release Date: 10/27/2003
>  
> 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.532 / Virus Database: 326 - Release Date: 10/27/2003
 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to