Releases: tanoconsulting/euts
0.11.0
-
improved: default database versions have been bumped to 5.7 for mysql, 11 for postgresql, as previous default versions
are now End Of Life -
fix: make it possible again to use mysql 5.6 as database
-
fix: make it possible again to use debian stretch as base image and have its packages system work, courtesy of Freexian repos
0.10.0
-
new: support environment variables
COMPOSER_IGNORE_PLATFORM_REQS
,COMPOSER_MAX_PARALLEL_HTTP
,COMPOSER_PREFER_LOWEST
,COMPOSER_PROCESS_TIMEOUT
-
improved: when creating the mysql db, set max concurrent connections to 256
-
fix: make it possible again to use debian jessie as base image and have its packages system work, courtesy of Freexian repos
0.9
-
new: support installation of Ibexa 4
-
new: allow specifying a custom version of NodeJS to install, via env var TESTSTACK_NODE_VERSION
-
improved: telling doctrine the correct version of mysql available, for ezplatform 3
0.8.0
-
new: simplified using the test stack on GitHub Actions by making it available as a custom action. This usage is documented via the example GHA workflow
-
fix: determining TESTSTACK_APP_DIR when the config file is given using a relative path
-
fix: avoid a problem with some liip imagine-bundle versions and eZP CP
0.7.0
-
fix: allow setting up the Legacy Bridge along with eZPlatform version 1 - it would work only with eZPlatform 2 beforehand
-
fix: when the teststack is used to test a pure legacy extension (ie. not one within a bundle), it would hang at the phase of generating legacy autoloads. We now prevent it from scanning the vendors folder
-
improved: when TESTSTACK_APP_DIR is not defined in the config file, the
teststack
command now tries to find the directory where the application (eZ bundle or legacy extension) is located by looking for a composer.json file first in the parent directory of the test stack itself (for BC), then in the directory of the config file and going up in all its parents, until one is found. The directory being used can be printed out by using the-v
cli option -
changed: in the test container, the dir where the project is installed is now
/home/test/workspace
- it was previously/home/test/bundle
-
new: command
teststack start
learned option-f
, which was already supported byteststack build
0.6.1
0.6.0
-
improved support for testing projects depending on eZPlatform 3.1, 3.2 and 3.3 (the latter is considered experimental)
-
use a per-project directory to store the db data, easing execution of tests running on different db versions from a single dir
-
install nodejs and npm by default in the test container (not supported yet for debian jessie and stretch containers)
-
the
teststack
command learned actioncleanup containers
;cleanup docker-images
was renamed tocleanup dead-images
-
fix: do not try to install php from a custom repository when the desired version is available in the apt repos already set up in the operating system
0.5.2
0.5.1
-
fixed creating the test database user account so that it can be accessed from all php versions when using MySQL 8.0 (useful for GitHub Actions workers as Ubuntu 18 is deprecated now, and Ubuntu 20 defaults to MySQL 8.0.30)
-
fixed building the MySQL container for recent versions of MySQL 5.7/8.0 (DockerHub now uses Oracle base images)
-
added a configuration example for running tests using GitHub Actions
-
BC break: when using EZ_COMPOSER_LOCK to specify the set of packages to install, it is now mandatory to specify as well the eZP package in use as value for the EZ_PACKAGES env var. This requirement might be relaxed in future releases