It's fine for me
On 10/02/2009, at 6:01 AM, John Casey wrote:
Actually, it looks like the properties are coming out wrong.
It looks for:
assertEquals( "1", props.getProperty( "stringParams" ) );
assertEquals( "test", props.getProperty( "stringParams.0" ) );
assertEquals( null, props.getProperty( "stringParams.1" ) );
and I have:
[...]
stringParams.1=test
stringParams=2
stringParams.0=test
[...]
Again, I'm not sure what this signifies (yet), or why it should be
different.
John Casey wrote:
Hi,
I was wondering whether others have seen failures in this
integration test (MNG-4023). It's failing consistently on my
machine, and I'm simply calling the bootstrap with integration
tests as follows:
ant with-its
I haven't dug into this too far, but it looks like the log.txt file
(the build itself) is clean...so it must be the assumptions checked
in the JUnit testcase that are failing. The tests are still running
here for a change I'm working on related to MNG-3023, so I can't
check the suite surefire output file yet.
Does anyone know anything about this test?
-john
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
--
Brett Porter
[email protected]
http://blogs.exist.com/bporter/
