Angle files now accept -2 to 362 degrees (the fsamroy rotation stage's physical overtravel range) instead of the nominal 0-360 sweep. This required widening both the parser's bounds (angle_file.py) and _tomo_scan_at_angle()'s own gate (a new _min_scan_angle(), alongside the existing _max_scan_angle()) -- without the latter, an angle just outside [0, 360] would have parsed fine but then been silently skipped during acquisition with no error, which is worse than rejecting it upfront. Also fixes the type-4 GUI section's "Content:" label clipping its second wrapped line: QFormLayout sizes that row from the label's sizeHint() at construction (holding the short "---" placeholder) and doesn't reliably recompute it when setText() later swaps in longer, word-wrapped content. _set_angle_file_summary() now recomputes the label's minimum height from heightForWidth() after every update. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NPZ9gzN2rt3wgiMnTKyrug
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.