On Mon, Feb 27, 2017 at 4:02 AM, Atira Odhner <aodhner@pivotal.io> wrote:
> Cool, we already have a task about proper teardown and a couple other things
> in our backlog. we'll probably get to it in the next day or so. I'll take a
> look at the other stuff.
Thanks.
> Also, regarding speed, even without the app startup time, end to end tests
> are always going to be relatively slow. We definitely want to make sure that
> the time it takes to run the tests does not grow to where it is a deterrent
> to running them.
Right - I expect them to be slower, but 1.5+ minutes per test (with 5
DB servers - we're soon going to have 10+) is not going to work. I
want to get us to the point where we're doing test driven development,
with the aim of always having the tree in a releasable state.
> There are a variety of things we can do to help address that as our suite
> grows. For instance, we could consider parallelizing the tests, making
> setup and teardown more efficient, combining related tests, or even
> breaking the tests into suites and running only some of them locally by
> default.
> Since we only have a couple feature tests so far the speed hasn't really
> felt like an issue for me yet, but I understand it may be different if you
> are trying to run in a variety of configurations.
I'm looking ahead to where we want to be. I don't want the test suite
to become a source of technical debt.
> Out of curiosity, what is the goal in supporting multiple python versions?
> Are we working on moving to 3.x and just haven't gotten fully there yet?
We need to support multiple versions of Python because that's what
users have on their systems. For example, RHEL/CentOS 6 which are
still in wide use ship with Python 2.6.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
