x12saandClaude Opus 5.5
d56a2a6d47
On 2026-10-10 an interlock abort left the Eiger2 Si 500K Dectris server armed (state ready, stream acquire), and every re-init then failed with "Detector busy" until the fibres were re-seated. The cancel path logged nothing on success, so it was not possible to tell what happened. - stop() logs a successful cancel with its reason, then the Dectris status - recover_from_error() adds a hint to the error when Dectris is still armed - on_stop logs that it was called - tests: block cancel to the production JungfrauJoch host from fixtures Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01G1MYT2ByPys8XL6BdfApAF
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.