Mirko HollerandClaude Opus 5.5
0dd14f6226
- set_sample_measured(..., account=...) stores the e-account of the status change in <slot>:MEAS_ACCOUNT; OWNER is no longer filled with the account (owner is free text now). Callers in omny.py/flomni.py pass bec.active_account. The account moves with the sample (transfer_sample) and is reset on load/clear. - OMNY: status 'screened' when a sample leaves the sample stage (stage -> gripper) with status 'none', i.e. no tomoscan was started on it (Mirko 2026-10-27). - widget: shows 'screened'; the P-touch label prints MEAS_ACCOUNT (owner as fallback for older records); CLI views show the account. - IOCs: OMNY ioc_omny.py / flOMNI ioc_flomni.py got the MEAS_ACCOUNT field (and 'screened' appended to the OMNY status enum), deployed on mpc3217 / mpc2844. - tests/e2e harness updated (owner_if_empty replaced by account). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01M8zoDvfTY6VYunNtWse9VZ
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.