JUnit reporting has a bug

Hi Sebastian,

thanks for this.. you are not the only one with this issue but unfortunately I have not yet succeeded in reproducing it.. is there are any way I could run these tests against a server of yours to see if I get the same error?

regards,

/Ole
eviware.com

Hi!

I am suspecting this is a classpath-related issue.. did you install 2.5.1 over the 2.5 installation or into a seperate folder?

There is an updated nightly build which changes some of the dependencies, could you please try that (in a seperate folder) to see if it helps?

Thanks!

regards,

/Ole
eviware.com

>did you install 2.5.1 over the 2.5 installation or into a seperate folder?

New folder everytime I install a new version.

>There is an updated nightly build which changes some of the dependencies, >could you please try that (in a seperate folder) to see if it helps?

Just tried the 13-Feb-2009 build and I get less errors when running it. Still get these though:

SystemId Unknown; Line #831; Column #84; java.lang.IllegalArgumentException: argument type mismatch
SystemId Unknown; Line #831; Column #84; java.lang.NullPointerException

The resulting JUnit report is still missing several pages. When i click to get the details of a test, it just show me a blank page.
I've attached the usuals ;

Hi Sebastian,

ok, there is a new build up using the "older" xalan libraries that were in 2.5, could you have a go and let me know ?

thanks in advance!

/Ole
eviware.com

I tried the new build and there was no change.

I made a new project against a public webservice to show that it's not an issue with out own webservices.
You will probably be able to reproduce the issue with the Shakespeare project that I have attached.

Btw, I'm using

c:\dev\tls\soapui\soapui-pro-2.5.1 13-Feb-2009 1423\bin>java -version
java version "1.6.0_11"
Java(TM) SE Runtime Environment (build 1.6.0_11-b03)
Java HotSpot(TM) Client VM (build 11.0-b16, mixed mode, sharing)

and your binary version. if it works well for you, then that could that be the difference we're experiencing.

I've attached the "usual suspects"

Hi Sebastian,

I think this is fixed now, reason was a missing dependency that kicked in in certain reports. Please try the latest nightly-build and let me know how it works for you.

Sorry for the inconvenience.

regards!

/Ole
eviware.com

Hi Ole,

It works great in the 16-Feb-2009 version!

Thanks for fixing it

Best regards,

Sebastian

Hi Sebastian!

Thanks for your feedback, sorry for the trouble with this..

regards!

/Ole
eviware.com

Just for your info:

The non-pro version of the 16-feb build still has the error. I assume that they're using the same codebase... So im'wondering why.

Hi!

how do you mean? The non-pro version does not have this reporting built in!?

regards!

/Ole
eviware.com!