- gui_tools.py: _omnycam_parking()/_omnycam_samplestage() now share one
_omnygui_show_omnycam_pair() helper that creates the two camera Image
docks + console once and re-points them via Image.image(device=...)
on later switches instead of tearing down and rebuilding the whole
GUI every time (bec_widgets' Image.image() already supports being
called again to swap the monitored device). Also stops live mode on
the outgoing camera pair on a switch, and drops the dead
_omnycam_check_device_exists no-op guard in favor of the `in dev`
idiom already used for cam_xeye in this file.
- omny_sample_transfer_mixin.py: the two remaining blocking
input("Ready. Press Enter...") prompts in otransfer_put_sample/
otransfer_get_sample now go through otransfer_confirm_dialog() like
every other transfer confirmation, so they show up in the GUI console
instead of blocking on a terminal keypress; fixed the get_sample
prompt's copy-pasted "mount" wording to "unmount".
- simulated_omny.yaml: otransx sim_velocity 10->100 mm/s; oshield
gained sim_velocity: 10.0 (previously unset, defaulting to the
Smaract sim's 1 mm/s) -- both x10 per request.
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.