Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to set up the test runner #4

Open
ngm opened this issue Dec 25, 2017 · 2 comments
Open

How to set up the test runner #4

ngm opened this issue Dec 25, 2017 · 2 comments

Comments

@ngm
Copy link
Owner

ngm commented Dec 25, 2017

Currently the test runner is codeception. But this should be changeable (theoretically) from project from project.

It should probably be a config option then. And if we pick a particular option, running 'runtests' should do a basic smoketest to see whether that test framework appears to be in place.

@ngm
Copy link
Owner Author

ngm commented Dec 26, 2017

I've made it come from the config file as to the command to run for the test runner.

(It could probably be improved, e.g. multiple configurations could be available and then you pick one, but good enough for now.)

However, still need a simple way of actually getting the test infrastructure into place. That should probably be the task of the developer, not aplet, but it would be nice to have a shortcut as it's a bit cumbersome to repeat over and over again (at least while I'm testing...)

@ngm
Copy link
Owner Author

ngm commented Dec 26, 2017

Just wrote a basic bash script for now to copy the codeception files from another repo I have, then run composer install. Works for now but need to think if this is something the aplet should do or not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant