So if the diff is "only" the build up of the connection ->getConnectionForTable($tableName) and ->getConnectionByName(ConnectionPool::DEFAULT_CONNECTION_NAME) I don't know.
Hope that it somehow makes sense what I'm writting.
I'll be happy to try to help fix and test this.
I have found problem with nimut/testing-framework in combination with PostgreSQL.
MySQL and PostgreSQL differs on how the
auto_increment
is working, but thedoctrine/dbal
handles this for us.If I have a fixture with following content simplified (pages).
When I then have a test, that insert data into this. Let's say we have a function adding pages, but only adding titles as uid is
auto_increment
.$this->addPage('New page title')
will then throw an exception.This will happen the first 3 times I run the tests, the 4th time, it will add it as the
uid
4 isn't set yet.When looking at the PostgreSQL index, after the fixtures is include.
It will return
1
, as no records are inserted yet from PostgreSQL point of view.I don't know how this should be fixed, but if I run the test with the
typo3/testing-framework
instead, it's working.One difference as I see it is that the
typo3/testing-framework
is using thewhereas the
nimut/testing-framework
is usingConstructor of
Database
isSo if the diff is "only" the build up of the connection
->getConnectionForTable($tableName)
and->getConnectionByName(ConnectionPool::DEFAULT_CONNECTION_NAME)
I don't know.Hope that it somehow makes sense what I'm writting. I'll be happy to try to help fix and test this.