Parallel testing might be hard for matrix testing. Today, executed serially, if 2 tests rely on table of the same name there is no concern about clash. And even for in-memory dbs, given my understanding of how the parallelization would occur, I do not think there is a concern.

I am not familiar with details of "configuration on demand".

But certainly there are 1.5 features I'd like to use as well. Hence the upgrade and the linked issues.

I was about to ask this

this brings us two major features I'd like to use:

• parallel testing

• configuration on demand