Circle ci: dockerized tests#796
Conversation
fa9badb to
9982378
Compare
9982378 to
6f42a79
Compare
DavertMik
left a comment
There was a problem hiding this comment.
Looks good to me! We can keep Travis CI for fast feedback and use Circle for heavy tests.
And what about Appium? You see the way to make it work in emulator? ;)
|
I will have one more shot at those failing scenarios before merging this week - it's for sure some small mistake ;) Also I cleaned up config, removed my "optimizations" (I way overdid it with circle workflows and custom caching :D) and went down to little bit over 10min build :) As for Appium I haven't look into that yet but for sure will follow one day, I have pretty limited time for codecept unfortunately right now. |
Wow. your limited time looks like greater than mine ) |
ed2fc40 to
60f3b70
Compare
60f3b70 to
b437dbe
Compare
|
@DavertMik looks ready to merge :D I'm not sure why travis build wasn't triggered for this one, it passed for my fork: https://travis-ci.org/jploskonka/CodeceptJS/builds/309036420 Also I had problems with |
Why?
#747 introduced dockerized test environment for easier usage in development. However TravisCI still use non-dockerized way of running it. Also Docker is fun and I really want to have Appium tests working in emulator :D
Differences with TravisCI
TODO
config.yml@DavertMik I have two WebDriverIO exmaples failing on CircleCI unfortunately, I wasn't able to reproduce it locally and it also used to work OK there - I have no idea yet what is going on here :D If you have any suggestion what may be wrong please let me know, maybe you saw something like this before :)