Hello Andrey. > No. Normal testing setup includes all steps to prepare testing environment. > And normally, when you test database interaction, you use mocked database > driver, so no actual database is necessary.
Sounds like you have an interesting setup. I'm glad it works for you. However, that will not work for my use case. This is not a "Normal testing setup". We do rapid iterations and a lot of automated testing, so the process has to be quick and also use an actual database which has been prepopulated with test data and will also process that data and add new data during the testing. On Tue, Jul 10, 2018 at 2:23 PM, Andrey Repin <[email protected]> wrote: > Greetings, Tony P! > >>> Then run a dedicated database container. Don't create problems for yourself, >>> and you won't have to solve them. > >> Creating problems for myself -- story of my life haha. XD You are >> absolutely right though. >> However, about using a dedicated database container, I didn't want to >> do it that way because I want the testing of my web applications to be >> somewhat seamless and not require any configuration changes. The goal >> is to test the web apps AS-IS without any changes to the code by >> quickly running a script (so it will be automated). Does that make >> sense? > > No. Normal testing setup includes all steps to prepare testing environment. > And normally, when you test database interaction, you use mocked database > driver, so no actual database is necessary. > > > -- > With best regards, > Andrey Repin > Tuesday, July 10, 2018 21:22:09 > > Sorry for my terrible english... > > _______________________________________________ > lxc-users mailing list > [email protected] > http://lists.linuxcontainers.org/listinfo/lxc-users _______________________________________________ lxc-users mailing list [email protected] http://lists.linuxcontainers.org/listinfo/lxc-users
