You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
dev-master has some key fixes such as fixes to testsessions that never end (constantly creating new temp databases), among others. There's also one other issue I'm just creating a PR for (where the database created by testsession is immediately cleaned up by TempDatabase when the request ends, meaning that it's useless for Behat testing as it stands without configuration changes).
I know there's been some API changes on master which is why it's targeting ^5, but I've done a quick test changing composer to target framework ^4 and master seems to still work just fine, so would it be possible to get a 3.0.0 with the changes currently on master (plus my PR coming in a sec)?
Happy to help set this up if needed, just wanted to get people's thoughts, at the moment we can't install dev-master unless we also upgrade to framework dev-master and so on down the line.
Thanks!
The text was updated successfully, but these errors were encountered:
dev-master
has some key fixes such as fixes to testsessions that never end (constantly creating new temp databases), among others. There's also one other issue I'm just creating a PR for (where the database created by testsession is immediately cleaned up byTempDatabase
when the request ends, meaning that it's useless for Behat testing as it stands without configuration changes).I know there's been some API changes on master which is why it's targeting ^5, but I've done a quick test changing composer to target framework ^4 and
master
seems to still work just fine, so would it be possible to get a 3.0.0 with the changes currently onmaster
(plus my PR coming in a sec)?Happy to help set this up if needed, just wanted to get people's thoughts, at the moment we can't install
dev-master
unless we also upgrade to frameworkdev-master
and so on down the line.Thanks!
The text was updated successfully, but these errors were encountered: