-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
Execute Travis CI for Yii Basic App #1744
Comments
I am not into core, someone from core should solve problems with |
Well, the tests are mainly provided as examples to show how to test your app. not sure whether it makes sense to run them on travis... |
@cebe true, but in this case we will know that something gone bad, but to be true we will know it anyway as someone will report about it. |
I like the idea of executing travis ci for the basic app. It can be considered as part of the functional tests for the core code. |
I'm for it as well. Having tests and not running these doesn't make sense. |
@cebe green badge on travis will make us confident that examples work as expected. |
Ok, so someone from core can start working on it i guess, as it was voted to do so :) |
Working on it. |
Added a travis.yml file for basic app. @qiangxue can you please enable travis on the yii2-app-basic repo? Acceptance tests may not run out of the box. Will fix this when travis support is enabled. |
Added it to travis. |
thanks. here is the link to the builds: https://travis-ci.org/yiisoft/yii2-app-basic/builds |
there is currently an issue with travis: travis-ci/travis-ci#1822 waiting for a solution. |
Basic app has some Codeception tests and I'd really like to say thank you to @Ragazzo for writing them and @qiangxue for making them run with Yii2 connector )
I think we should connect https://github.com/yiisoft/yii2-app-basic repo to Travis so we could watch for any regression in Yii-Codeception tests. As well we need to cover various tricky aspects in tests like forms, redirections (I think they are mostly covered, but you know better of them).
@Ragazzo, maybe you can provide PR with travis.yml config for that?
The text was updated successfully, but these errors were encountered: