You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- All the files are copied straight into the test folder (under info/tests/{index}/)
- The script is turned into a run_test.sh or run_test.bat file
- The extra requirements are stored as a JSON file called test_time_dependencies.json
For a Python import test:
- A JSON file is created that is called python_test.json and stores the imports to be tested
and whether to execute pip check or not. This file is placed under info/tests/{index}/
I like what it describes, and they can help me build tests with different configurations for the same package file. But when I try to build a package with test section and test file, the package's content does not follow what the documentation describes and the test file is stored in the package content rather than package metadata, leading to extraneous files installed to the environment. Here is an example package on Linux:
Note the test file run.py is under etc tree. The tree command in the test is to confirm that when the package is installed in an environment, the test file in etc/conda/test-files will be installed in the environment, meaning they are the content of the package rather than the metadata, which is undesirable:
In conclusion, none of the points I quoted from the documentation happens in the package, Moreover, there is one file in the test metadata info/tests/tests.yaml, which is not in the documentation. It feels the documented translation is not implemented yet? I like the design in documentation, could we implement that? Thanks.
The text was updated successfully, but these errors were encountered:
I'm reading the documentation of this section: https://rattler.build/latest/testing/#how-tests-are-translated. Specifically, these points:
I like what it describes, and they can help me build tests with different configurations for the same package file. But when I try to build a package with test section and test file, the package's content does not follow what the documentation describes and the test file is stored in the package content rather than package metadata, leading to extraneous files installed to the environment. Here is an example package on Linux:
recipe.yaml
run.py
The command line is something like this:
The build log shows the files that will be in the newly built package:
Note the test file
run.py
is underetc
tree. Thetree
command in the test is to confirm that when the package is installed in an environment, the test file inetc/conda/test-files
will be installed in the environment, meaning they are the content of the package rather than the metadata, which is undesirable:In conclusion, none of the points I quoted from the documentation happens in the package, Moreover, there is one file in the test metadata
info/tests/tests.yaml
, which is not in the documentation. It feels the documented translation is not implemented yet? I like the design in documentation, could we implement that? Thanks.The text was updated successfully, but these errors were encountered: