RE: Every failure leads to an error

[David Lemieux (QC/EMC)]

Hi,

Thanks for checking on my problem.

I was calling a SessionBean in other test in the same class. Maybe that's it.
I stripped everything that might be useful.
Here is the whole file.

I deleted everything matching *log* in my server directory before deploying the app.
Here are included everything matching *log* after I ran this single test. 
If there is supposed to be anything else, I don't know where to find it.

/*****************************************/
package YYYY.applications.sampleapplication;

import junit.framework.AssertionFailedError;
import junit.framework.Test;

import org.apache.cactus.ServletTestCase;
import org.apache.cactus.ServletTestSuite;

public class TestHello extends ServletTestCase{

        public TestHello(String theName){
                super(theName);
        }
        
        //      For the test to be executable
        public static void main(String[] theArgs){
                junit.swingui.TestRunner.main(new String[] 
{TestHello.class.getName()});
        }
        
        public static Test suite(){
                ServletTestSuite suite = new ServletTestSuite();
                suite.addTestSuite(TestHello.class);
                return suite;
        }

         
        public void testShouldNotBeSuccess(){
                        assertTrue("This was predictable",false);
        }
}
/*****************************************/

Session bean code :
I don't see anything that could match the server side output, but... maybe in the 
generated classes
/*****************************************/
public class HelloEJBBean implements SessionBean {
        // The current counter is our conversational state.
        public String message;
        //
        // Business methods
        //
        
        /**
        * Counts up
        */
        public String sayHello() {
                
                return message;
        }
        
        public String getName(){
                String Name="David";
                
                return Name;
        }
        //
        // EJB-required methods
        //
        public void ejbCreate() throws CreateException {
                this.message = "Hi, what is your name?";
//              System.out.println("ejbCreate()");
        }
        public void ejbRemove() {
//              System.out.println("ejbRemove()");
        }
        public void ejbActivate() {
//              System.out.println("ejbActivate()");
        }
        public void ejbPassivate() {
//              System.out.println("ejbPassivate()");
        }
        public void setSessionContext(SessionContext ctx) {
        }
}
/*****************************************/
David

-----Original Message-----
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Friday, October 31, 2003 2:48 PM
To: 'Cactus Users List'
Subject: RE: Every failure leads to an error


Hi David,

I've tested your use case and Cactus correctly returns a failure for me.
The stack trace you're showing is very strange. It is output from the
server side (as is proved by the fact that AbstractWebTestCaller.doTest
is called). However, the Cactus framework do NOT output anything to the
console on the server side.

Thus, I believe the test you have executed is NOT the one you're showing
us:

        public void testShouldShowFailure(){
                        assertTrue("This was predictable",false);
        }

Could that be true? :-)

Thanks
-Vincent





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