Mark Proctor wrote:
fixed!!! You have the global static variable that is being set by one
test setUp, this is then set incorrectly for all tests. For now I added
a setUp to FtpLetContainerTestTemplate:
protected void setUp() throws Exception {
MockFtplet.callback = new MockFtpletCallBack();
MockFtplet.callback.returnValue = FtpletEnum.RET_DEFAULT;
}
Thanks, patch applied at rev 488161.
However this seems rather fragile, so hopefully someone can refactor
this unit test to make it more robust.
The funny callback construction exists so that it's possible to run some
other tests where the ftplet is setup using the properties
configuration. I will likely change these tests soon as one can soon
(haven't commited all the changes yet) set up the Ftplet from Java instead.
/niklas
