You are viewing a plain text version of this content. The canonical link for it is here.
Posted to cactus-user@jakarta.apache.org by Luiz-Otavio Zorzella <zo...@codaware.com> on 2003/04/03 02:29:20 UTC

Help: Running Cactus tests makes redeployment required

Hi,

I'm new to Cactus testing, but I managed to write a test file that 
extends CactusStrutsTestCase and write a simple test against my 
application. I've managed to package that in the war in my ear file, 
deploy it to my jboss 3.0.6 server and run the tests, both from the 
servlet and from ant. The URL for the servlet and the ant targets are 
presented in the end of the email.

Everything works fine, except that, after I test my app (from either 
ServletTestRunner or ant), if I try to use it, all the pages come blank. 
No exceptions or errors are displayed in the log (with debug enabled) 
and the only solution is to redeploy.

Is this normal (i.e. you need to redeploy after testing), or am I 
missing something?

Thanks a lot!

Zorzella

URL:

http://myserver:8080/myapp/ServletTestRunner?suite=com.mycompany.junit.TestStrutsUI&xsl=data/junit-noframes.xsl


ant target:

    <target name="testUI">
        <junit printsummary="yes" haltonfailure="yes" haltonerror="yes"
             fork="yes">
	     <formatter type="plain" usefile="false"/>
	     <test name="${struts.test.class.name}"/>
	     <classpath refid="struts.test.classpath" />	
        </junit>
    </target>




Re: Help: Running Cactus tests makes redeployment required

Posted by Luiz-Otavio Zorzella <zo...@codaware.com>.
Vincent,

I will certainly do it (after I find the address to subscribe to their 
list).

Is there any other -- more stable -- option for JUnit testing a Struts 
application? Can Cactus be used for that without the StrutsTestCase shell?

Zorzella

Vincent Massol wrote:
> Hi,
> 
> That looks like a bug to me. So far I've counted 3 persons reporting
> this problem. AFAIK, this is a StrutsTestCase issue as it has only been
> reported by persons using StrutsTestCase. Maybe you should report it to
> the StrutsTestCase mailing-list/forum?
> 
> Thanks
> -Vincent
> 
> 
>>-----Original Message-----
>>From: Luiz-Otavio Zorzella [mailto:zorzella@codaware.com]
>>Sent: 03 April 2003 02:29
>>To: cactus-user@jakarta.apache.org
>>Subject: Help: Running Cactus tests makes redeployment required
>>
>>Hi,
>>
>>I'm new to Cactus testing, but I managed to write a test file that
>>extends CactusStrutsTestCase and write a simple test against my
>>application. I've managed to package that in the war in my ear file,
>>deploy it to my jboss 3.0.6 server and run the tests, both from the
>>servlet and from ant. The URL for the servlet and the ant targets are
>>presented in the end of the email.
>>
>>Everything works fine, except that, after I test my app (from either
>>ServletTestRunner or ant), if I try to use it, all the pages come
> 
> blank.
> 
>>No exceptions or errors are displayed in the log (with debug enabled)
>>and the only solution is to redeploy.
>>
>>Is this normal (i.e. you need to redeploy after testing), or am I
>>missing something?
>>
>>Thanks a lot!
>>
>>Zorzella
>>
>>URL:
>>
>>
> 
> http://myserver:8080/myapp/ServletTestRunner?suite=com.mycompany.junit.T
> es
> 
>>tStrutsUI&xsl=data/junit-noframes.xsl
>>
>>
>>ant target:
>>
>>    <target name="testUI">
>>        <junit printsummary="yes" haltonfailure="yes"
> 
> haltonerror="yes"
> 
>>             fork="yes">
>>	     <formatter type="plain" usefile="false"/>
>>	     <test name="${struts.test.class.name}"/>
>>	     <classpath refid="struts.test.classpath" />
>>        </junit>
>>    </target>
>>
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: cactus-user-help@jakarta.apache.org
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org
> 



RE: Help: Running Cactus tests makes redeployment required

Posted by Vincent Massol <vm...@pivolis.com>.
Hi,

That looks like a bug to me. So far I've counted 3 persons reporting
this problem. AFAIK, this is a StrutsTestCase issue as it has only been
reported by persons using StrutsTestCase. Maybe you should report it to
the StrutsTestCase mailing-list/forum?

Thanks
-Vincent

> -----Original Message-----
> From: Luiz-Otavio Zorzella [mailto:zorzella@codaware.com]
> Sent: 03 April 2003 02:29
> To: cactus-user@jakarta.apache.org
> Subject: Help: Running Cactus tests makes redeployment required
> 
> Hi,
> 
> I'm new to Cactus testing, but I managed to write a test file that
> extends CactusStrutsTestCase and write a simple test against my
> application. I've managed to package that in the war in my ear file,
> deploy it to my jboss 3.0.6 server and run the tests, both from the
> servlet and from ant. The URL for the servlet and the ant targets are
> presented in the end of the email.
> 
> Everything works fine, except that, after I test my app (from either
> ServletTestRunner or ant), if I try to use it, all the pages come
blank.
> No exceptions or errors are displayed in the log (with debug enabled)
> and the only solution is to redeploy.
> 
> Is this normal (i.e. you need to redeploy after testing), or am I
> missing something?
> 
> Thanks a lot!
> 
> Zorzella
> 
> URL:
> 
>
http://myserver:8080/myapp/ServletTestRunner?suite=com.mycompany.junit.T
es
> tStrutsUI&xsl=data/junit-noframes.xsl
> 
> 
> ant target:
> 
>     <target name="testUI">
>         <junit printsummary="yes" haltonfailure="yes"
haltonerror="yes"
>              fork="yes">
> 	     <formatter type="plain" usefile="false"/>
> 	     <test name="${struts.test.class.name}"/>
> 	     <classpath refid="struts.test.classpath" />
>         </junit>
>     </target>
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cactus-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: cactus-user-help@jakarta.apache.org