Re: [Apiman-dev] APIMAN-549 - Can't add a plugin when using postgres

On Jul 16, 2015, at 7:16 AM, Eric Wittmann <eric.wittmann(a)redhat.com&gt; wrote: OK I haven't started on this yet - but I've thought a bit about it. I won't be able to get to DB work until tomorrow as it turns out. However, here are some thoughts about this topic. :) I think it will be challenging to get the full suite of unit tests working against a database because the unit test framework assumes that each test runs against an empty DB. There are some other seeding pre-reqs as well. It's not impossible to get all that working against a real database, obviously. But in an effort to get something out sooner rather than later, I'm going to look at using the FullTestSuite (as you noted). This test is designed to run as a smoke test against a real system, pre-configured only with the standard default data set. We can add some additional tests to it to increase its coverage, something we want to do anyway. It should suffice until we rethink the overall unit testing approach. -Eric > On 7/15/2015 11:50 PM, Brandon Gaisford wrote: > Eric, > > I spent a couple hours this afternoon trying to update io.apiman.manager.test.server.ManagerApiTestServer to use an external Postgres database to run the maven tests against. I wasn’t successful and ran out of time today. I’m currently stuck as JPA is throwing “Transaction not active” errors. I was hoping I could get this done today and help with the testing/validation effort against the new DDLs, but unfortunately not. Sorry dude, I tried. I’ll pick it up again tomorrow as I have time unless you come up with a better approach. > > Laters, > > Brandon > > > _______________________________________________ > Apiman-dev mailing list > Apiman-dev(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/apiman-dev >