On Feb 21, 2006, at 2:00 PM, Prasad Kashyap wrote:
True. The itests setup (infrastructure) which was broken by the move
has been restored. Itests can now be plugged in and run
successfully. While some of the old itests pass successfully, some of
them fail. The ones that fail are the ones that depended on the
default-datasource.
Around last Thu, I learnt from Dain (on the IRC) that he'd be
creating a new default datasource to get those tests to pass too. I
don't know what the ETA on that is.
Dain, is that something you'd get to in the next week (guessing not
with the config changes)?
Prasad, do you know which test suites pass and which fail? If we
could figure that out we could comment out the ones that fail and get
the itests running as part of the build again. They're commented out
now cause they cause the build to fail, which is bad news as someone
will just break the infrastructure again without knowing it.
Especially with all the maven2 conversion stuff going on.
Thanks,
-David
On 2/21/06, David Blevins <[EMAIL PROTECTED]> wrote:
On Jan 29, 2006, at 6:12 AM, Prasad Kashyap wrote:
I would like to propose the following test strategy.
1. Fix existing openejb itests such that they can be reintegrated
back
into the builds.
On Feb 9, 2006, at 9:10 AM, Prasad Kashyap wrote:
I have completed items 1 and 3 of the test strategy outlined above.
With that we now have the geronimo-deployment-plugin in maven 2.
Doesn't seem like item 1 was ever really checked off the list. I
just noticed the itests are still broken because of the whole default
database issue.
Where did we leave off on how to get them running again? I remember
some chatter on whether or not there should be a default database,
etc. But I also remember some IRC talk about just adding a connector
to the itests to make them run.
-David
