Aerie-CLI integration tests exercise commands against an actual instance of Aerie.
These tests will delete and modify data permanently. Expect the localhost instance of Aerie to be modified heavily. These test will delete all models.
To set up a local test environment, use the test environment and docker-compose files in the root of the repo:
docker compose -f docker-compose-test.yml up
Invoke the tests using pytest
from the tests/integration_tests
directory:
python3 -m pytest .
Integration tests are automatically run by CI against all supported Aerie versions. Update as follows with the supported set of Aerie versions:
tests/integration_tests/files/models
, named as banananation-X.X.X.jar
(substituting the correct version number). Remove outdated JAR files.COMPATIBLE_AERIE_VERSIONS
array in aerie_host.py
..env
file DOCKER_TAG
value to the latest compatible version. This sets the default value for a local Aerie deployment.docker-compose-test.yml
as necessary to match the supported Aerie versions. The aerie-ui compose file can be a helpful reference to identify changes.aerie-version
list in the CI configuration to include the new version.To verify changes:
configurations
commandsmodels
commandsplans
commandsplans download...
commands as wellscheduling
commandsexpansion
commandsmetadata
commandsconstraints
commands