x01dcandClaude Sonnet 5
83f9a6bb59
Three follow-ups from real-hardware testing of the smear aid: 1. Switching the "Smear preview channel" toggle off then back on showed the live camera feed, not the previous composite. Root cause: Image.image()'s connect_slot subscription only delivers stream entries published *after* connecting (bec_lib's default register(from_start=False, newest_only=False) bookmarks the then-current last entry and only forwards newer ones) -- so nothing re-renders on reconnect until the next sweep pushes a new frame. Added a permanent, independent subscription (newest_only=True) that keeps the last smear_preview payload cached regardless of which channel is currently displayed; set_live_view_signal() now force- renders that cache via main_image.set_data() when switching back to "smear_preview", instead of waiting for a push that may never come. Naturally "resets" once a new sweep starts pushing fresh composites. 2. The new switch row wasn't column-aligned with the existing shutter/camera-running row (each used an independent QHBoxLayout sized by its own labels' widths). Merged both rows into one QGridLayout with right-aligned label columns, so all four toggles line up regardless of label text length. Shutter now pairs with Smear integrating, Camera running with Smear preview channel. 3. find_rotation_center_smear_experimental() now archives each run to a timestamped HDF5 file (~/data/raw/logs/xrayeye_smear_calibration/), mirroring align()'s existing _save_alignment_data() pattern: the FZP reference, one composite image + one clicked centre per iteration, and the final result -- collecting data towards eventually automating center detection from the composite offline. 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.