test-acceptance-api and test-acceptance-webui makefile targets #129
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.
We are working towards having proper Makefile build targets for each of the parts of testing -
make test-php-style
make test-php-style-fix
etc.Acceptance tests currently come in 2 different flavors. API tests only need a server running somewhere and some client utility code (Guzzle, curl...) on the test script side. webUI tests also need a browser environment and whatever middleware to talk to the browser (e.g. Mink to selenium). We currently do not mix running API and webUI acceptance tests in a single run.
So I am proposing that we have 2 build targets:
For discussion, please comment. e.g.