The areaDetector file plugin refuses to be staged until one NDArray has passed through it, so every restart of the SITORO IOC leaves the Falcon raising ophyd's UnprimedPlugin at the start of a scan. The generic HDF5Plugin.warmup() cannot be used, as it drives parent.cam, which the Falcon does not have. prime() pushes a single spectrum through the plugin using user-advanced pixels, so no external gate signal is required and a disconnected trigger cable cannot mask the priming. No file is written. The trigger configuration is captured beforehand and restored in a finally block. on_stage never resets pixel_advance_mode, ignore_gate or pixels_per_buffer -- only on_connected does -- so a prime that bailed out halfway would otherwise leave the detector deaf to the gate and silently starve every subsequent scan. prime() and is_primed() are exposed via USER_ACCESS, so they are callable from the BEC client as dev.falcon.prime(). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01KLnmUurqcNd1FiDY5M2uZr
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.