Ports flomni's ffzp_info() OSA collision-clearance section (compares live losaz against nominal "in" position and a collision-boundary constant, warns if closer to collision than nominal or reports clearance at IN) -- same formula shape and sign convention as flomni (motion directions confirmed identical between the two setups). lamni's collision-boundary constant has never been measured, so it's read from loptz's device config (userParameter.collision_offset) via a new _get_user_param_optional() helper -- unlike the existing _get_user_param_safe(), it returns None instead of raising when the parameter is undefined (as it currently is for every lamni device config, including the simulated one), since absence here means "not yet commissioned" rather than a config error. lfzp_info() prints a clear warning and skips the numeric estimate entirely until someone adds the real measured value to the config -- deliberately not a CLI-settable/global-var parameter, since this is deployment-level hardware calibration. Item 7 of csaxs_bec/bec_ipython_client/plugins/LamNI/AI_docs/ FLOMNI_LAMNI_FEATURE_GAPS_2026-07.md. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
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.