You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@struts.apache.org by "David M. Karr" <dm...@earthlink.net> on 2003/03/10 02:43:10 UTC
How to debug problem in TestDynaActionForm class?
I just decided to start looking at the unit tests, in order to look into
updating the Struts-EL test cases.
After just doing an update, and executing "test.tomcat.41" (with Tomcat-4.1.18
on Win2k), I get the following (I added a "println" of the form property, just
in case):
-------------
Testsuite: org.apache.struts.action.TestDynaActionForm
Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 0.391 sec
------------- Standard Output ---------------
stringProperty[This is a string]
------------- ---------------- ---------------
------------- Standard Error -----------------
Mar 9, 2003 4:26:32 PM org.apache.struts.util.PropertyMessageResources <init>
INFO: Initializing, config='org.apache.struts.util.LocalStrings', returnNull=true
------------- ---------------- ---------------
Testcase: testBeanCreate took 0.381 sec
Caused an ERROR
junit.framework.Assert.assertEquals(Ljava/lang/String;Ljava/lang/String;Ljava/lang/String;)V
at org.apache.struts.action.TestDynaActionForm.testBeanCreate(TestDynaActionForm.java:217)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
-------------
So, I'm first trying to understand why this failing, but I'd also like to be
able to set up my debugger so that I can look at these issues a little closer.
My basic problem is that I can't figure out which "java" command line to change
to add the "-Xdebug" flag (and others). For this, I thought it might be the
"java" task in the "start.tomcat.41" target in the "build-tests.xml" script.
This doesn't appear to be it, however, as my breakpoints in the test class go
unbroken, even though it hit my added println statement.
I know it got to the "java" command line that I changed, because it paused,
waiting for a debugger to connect to it. Once I had my debugger connect, it
went on, but it never hit my breakpoints in the test class.
--
===================================================================
David M. Karr ; Java/J2EE/XML/Unix/C++
dmkarr@earthlink.net ; SCJP; SCWCD
---------------------------------------------------------------------
To unsubscribe, e-mail: struts-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: struts-dev-help@jakarta.apache.org