Currently all changes are tested to be made and returned within the same DB transaction which is great to enforce the atk4/ui to made as less server requests possible and always work with fresh data for each Behat scenario, but this imply we cannot test advanced features - like CardDeck or more than one change per test scenario.
Currently all changes are tested to be made and returned within the same DB transaction which is great to enforce the atk4/ui to made as less server requests possible and always work with fresh data for each Behat scenario, but this imply we cannot test advanced features - like CardDeck or more than one change per test scenario.