Re: [openstack-dev] [Murano] Should we run tests on all supported database engines?

2015-03-05 Thread Andrew Pashkin
Why do we need that, by the way? REST API tests will cover database access, and database is not used for anything else than API anyway. Additional DB layer will bring additional complexity which we will consume time to maintain it. So if we do not know why exactly we need such layer, I think we

Re: [openstack-dev] [Murano] Should we run tests on all supported database engines?

2015-03-02 Thread Serg Melikyan
Hi Andrew, I think we should isolate DB access layer and test this layer extensively on MySQL PostgreSQL. On Mon, Mar 2, 2015 at 6:57 PM, Andrew Pashkin apash...@mirantis.com wrote: There is a bug: https://bugs.launchpad.net/murano/+bug/1419743 It's about that search on packages is failing

[openstack-dev] [Murano] Should we run tests on all supported database engines?

2015-03-02 Thread Andrew Pashkin
There is a bug: https://bugs.launchpad.net/murano/+bug/1419743 It's about that search on packages is failing if use Postgres as DB backend. The fix is pretty easy there, but how this bug should be tested? I see such options: 1) Run all tests for all DBs that we support. 2) Run some tests for

Re: [openstack-dev] [Murano] Should we run tests on all supported database engines?

2015-03-02 Thread Andrew Pashkin
What kind of layer do you mean? Right now we have some kind of isolation in the form of separate functions for DB lookups. For example for this case its murano.db.catalog.api.package_search [1]. [1]