- Add support for python 3.13 (#26)
- Re-enabled support for python 3.8 (#25).
- Added support for viash 0.9.0 (#23).
- run_component now executes viash run with --engine docker (or --platform docker) when the test is executed inline (and not as a result of using 'viash test') instead of the first engine that is defined in the config. Another engine can be specified by using the engine keyword argument (#22).
- run_component now uses cachedbuild setup strategy when tests are executed inline with engine docker. This makes sure that the docker image is update when it already exists on the system (#22).
- Added debugging information about the calls that are made to viash. If you want to enable debugging information, use --log-cli-level=DEBUG from pytest (#22).
- The minimum supported version of pytest is now 6.2 (PR #20).
- Added support for python 3.12 (PR #20).
- (development) Removed the bin/ folder in favour of a viash project config (_viash.yaml) (PR #20).
- Fix run_component setting --memory and --cpu at the incorrect location in the viash run command (PR #20).
- Fix tests for pytest versions older than 7.0 (PR #20).
- Match the logging level to the level in the config from pytest (see pytests' --log-cli-level) (PR #20)
- Fixed an issue with run_component assigning too much memory when using viash test with --memory. Viash rounds the values for the units that are bigger than the unit specified with --memory up to the nearest integer. (i.e. with --memory 500GB, memory_tb becomes 1). Because run_component took the value for the largest unit, memory was being over-provisioned. The breaking change involves run_component using the value from the smallest (instead of largest) unit when the memory resources are specified with multiple units.
- Fix an issue with run_component raising AssertionError when using viash test without --memory.
- run_component now passes the cpus, memory_b, memory_kb, memory_mb memory_gb, memory_tb, memory_pb, memory_tb, memory_pb keys, defined in the meta dictionary of the test module, as memory and cpu contraints to the executed component. The cpus and all memory keys can be set by using viash (ns) test with --cpus or --memory respectively. The memory and cpu fields can also be set to a hardcoded value in the test script. In this case, care should be taken to only specify one of memory_b, memory_kb, memory_mb, memory_gb, memory_tb, memory_pb. If more than one value for memory resources are defined and a conflict exists between the values, the value from the largest unit of measure is used.
- Added memory_bytes and cpus fixtures.
- run_component: fixed adding the captured output to CalledProcessError object when a component execution fails.
- run_component: fix a bug where pytest.fail was used when running a component failed instead of using CalledProcessError.
- run_component: when the component fails, stack traces from helper functions are no longer shown.
- run_component: component output captured from stderr and stdout is added to pytest output.
- run_component now returns captured stdout and stderr from the component run.
- Added the meta, viash_executable, test_module, meta_config_path, meta_config, viash_source_config_path viash_source_config fixtures.
- run_component will now supports to execute viash run with the component config when running tests inline instead of using viash test, removing the need to rebuild components.
- Added utility to extract tar files.
- Dropped support for python3.7 and python3.8
- Drop Windows support as viash uses WSL on Windows.
- The run_component fixture now raises AttributeError instead of RuntimeError when the meta variable is not defined in the test module.
- run_component will now use FileNotFoundError instead of RuntimeError when trying to run an executable and this executable is not a file.
- Initial release