- shutter.py (OMNYFastShutter): drop the "use dev.fsh if configured, else fall back to a local dummy signal" branching -- always delegate to the 'fsh' device. Removed the now-unused MonitorSignal class and the dummy shutter Cpt along with it. Rewrote test_omny_shutter.py to assert delegation to a mocked 'fsh' device instead of exercising the removed dummy fallback. - omny_sample_transfer_mixin.py: picking a sample up (get_sample, three source kinds: shuttle slot, fixed position, sample stage) only carried the sample name into set_sample_in_gripper(), silently dropping owner (defaulted to "") and measured status/account (reset to "none" by set_sample_in_gripper() itself). Same gap in reverse on put_sample. All six call sites (three pick, three put) now read owner/status/account from the source before clearing it and carry them onto the destination. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_018Mupip8x7Hean6E3FFvpbj
Getting Started with Testing using pytest
BEC is using the pytest framework. It can be installed via
pip install pytest
in your python environment.
We note that pytest is part of the optional-dependencies [dev] of the plugin package.
Introduction
Tests in this package should be stored in the tests directory.
We suggest to sort tests of different submodules, i.e. scans or devices in the respective folder structure, and to folow a naming convention of <test_module_name.py>.
It is mandatory for test files to begin with test_ for pytest to discover them.
To run all tests, navigate to the directory of the plugin from the command line, and run the command
pytest -v --random-order ./tests
Note, the python environment needs to be active.
The additional arg -v allows pytest to run in verbose mode which provides more detailed information about the tests being run.
The argument --random-order instructs pytest to run the tests in random order, which is the default in the CI pipelines.
Test examples
Writing tests can be quite specific for the given function. We recommend writing tests as isolated as possible, i.e. try to test single functions instead of full classes. A very useful class to enable isolated testing is MagicMock. In addition, we also recommend to take a look at the How-to guides from pytest.