Allow using SQLite in test environment #160
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First things first:
.env.test.distenv is being parsed by Behat by default which might be confusing if someone uses.envfor a test environmentdoctrine.yamlconfiguration forces you to use MySQL server only, but it's far better to use SQLite for plugins instead, especially if you're working on many plugins at the same time without Docker or Vagrant.PS. Are you planning to write the test suite for plugin skeleton features? There's always a problem once you publish a new Sylius release 😢 . This kind of test suite could be also used to test Sylius-Standard.