Closed ehmatthes closed 1 month ago
__init__.py
utils/it_helper_functions.py
Coupled through path to reference files.utils/manage_sample_projects.py
. Coupled through files_dirs_to_remove
.$ pytest simple_deploy/management/commands/fly_io/tests/integration_tests -x
...
import integration_tests.utils.it_helper_functions as hf
E ModuleNotFoundError: No module named 'integration_tests'
pytest tests/integration_tests
; they should pass, because only platform-agnostic tests are left.test_plugins.py
file, which specifies which plugins to run integration tests for.sys.path
, but maybe a better way?check_reference_file()
makes assumption that reference file is in host repo.
check_reference_file_direct()
for now.simple_deploy
during integration test for plugin.test_default_plugins.py
should read pyproject.toml
to see which plugins are included by default.uv pip
and uv venv
.Just find the simplest way to make integration tests work again, with all tests in the plugin dirs, but assume they're in the same repo.
run_simple_deploy(autouse="module")
is not running for the plugin's integration tests.
integration_tests/conftest.py
. It needs to be placed in a directory that's in the plugin's path as well.Just make them work from within the management/commands/fly_io/
dir.
check_valid_call()
from /tests/e2e_tests/conftest.py
work?
-s
is allowed when it should be caught.$ pytest tests/e2e_tests --platform fly_io -s
Closed by #332.
Right now, integration and e2e tests are tightly coupled with django-simple-deploy core. Uncouple these tests, so all platform-specific integration and e2e tests are within the plugin directories.
build_dev_env.py
into developer_resources. Consider developer_tools, distinct from "resources".