My favorites | Sign in
Project Home Downloads Source
READ-ONLY: This project has been archived. For more information see this post.
Search
for
  Advanced search   Search tips   Subscriptions
Issue 37: problem with ant runner
1 person starred this issue and may be notified of changes. Back to list
Status:  Fixed
Owner:  virtix
Closed:  Jun 2010


 
Project Member Reported by marc.es...@gmail.com, Dec 23, 2007
I'm not really sure what exactly is the problem, but i'm seeing several:

1) the TimeStamp when I run the tests is wrong. sometimes when I run it,
the timestamp is a half hour behind. Sometimes, it's a few minutes fast. 

2) it looks to me like some tests are running multiple times, or else i'm
getting weirdo cached results or something. for example, when I run it it
gives me 5 total tests and 1 error in the "runner" package, even though
there are only 4 tests. When I run that test from the browser (aka not in
ant), everything runs fine and i get 4 successes, no errors.
 

Now, I did remove the "html" directory from subversion because it was
causing too many problems. but it still seems like there's some weirdo test
caching going on.
Dec 23, 2007
Project Member #1 marc.es...@gmail.com
Ah, I see the problem with #2: it's not that the tests are running twice, it's that
the component name isn't in there and so it appears that it's running twice. but
really what  i'm seeing is a same-named method from two different components.

Bill... can you put the component name in front of the method name?

the timestamp problem still exists
Dec 23, 2007
Project Member #2 marc.es...@gmail.com
found the problem with the time formatting. it was using dateformat(now(),"mm/dd/yy
hh:mm:ss") but that won't work. you need to use timeformat as well. i remember fixing
this in the browser results a long time ago, although i noticed i didn't fix it in
the title tag and thus the time in the title didn't match the time in the tests
themselves.

i fixed it in both XMLTestResult and JUnitXMLTestResult, and now everything is fine
with the times.

so...

only outstanding thing is to clarify what tests go with what functions in the junit
xml result 
Dec 23, 2007
Project Member #3 marc.es...@gmail.com
I think I see the problem now. I'm wondering if in order to get this to work
properly, there will need to be a testsuite file for every test, not just for every
directory. when i look at the junit output, it does appear that that's how it's done.
ugggg.

you up for that?
Jun 30, 2010
Project Member #4 virtix
old
Status: Fixed
Cc: -marc.esher

Powered by Google Project Hosting