Docker for tests

[machour]

I'd like to discuss the possibility of adding Docker setups in each repositories to help developers running tests.

This wouldn't be a requirement to run tests, and it won't be involved during the Travis builds.

It would allow us to run docker-compose up in the tests directory and immediately having a working environment to fiddle with the extension.

[samdark]

I'm not using Docker much for Yii development but if it helps I'm not against it. @schmunk42 what do you think?

[schmunk42]

I support the idea 100% \o/

@machour: just @ me at will or reach out on Slack or via E-mail.
With which repo do you wanna start?

[kids-return]

I support, first build a basic image, and then define it separately according to different extensions.
But I think this can be done later, it is most important to make the whole framework work properly, so that you can find out where the framework needs to be adjusted and fixed earlier.

[schmunk42]

We have that already ;) https://github.com/yiisoft/yii-docker

Including tests with phpunit tests/framework/ --exclude db
https://travis-ci.com/yiisoft/yii-docker

[samdark]

It isn't about travis. It's about running stuff locally.

[schmunk42]

I support, first build a basic image, and then define it separately according to different extensions.

I actually referred to this, what I wanted to say is: There are Docker images for Yii 3.x

[machour]

@kids-return This is for fixing tests. I was about to install sphinx and elasticsearch on my laptop to try and fix tests when I thought of this.

[samdark]

Experienced all kinds of breakage with travis recently so now I'm all for it :)

[schmunk42]

So, there are 7.4 images now. But which tests can/should be run since there's no more yii-core?

[samdark]

Tests for each individual package: https://www.yiiframework.com/status/3.0. But that's not a priority for now. Travis is OK except it being a bit slow. We're considering GitHub actions though.

[schmunk42]

What takes a lot of time (and space) is a composer install (with dev-packages) for each package, but I think it is the cleanest way to do it.

I'd recommend to run tests which do not need external services such as DBs or caches, since we already have found issues with PHP versions or operating systems.

We can start with a smaller set and/or use branches or triggers to run more if required.

[samdark]

I think it's better to focus on something else... Travis currently isn't problematic.