The "Enter authorization code" (x12sa) prompt gating advanced tomo modes (types 2-5) predates the account-based _SUPERUSER_ACCOUNTS gate added earlier this branch, and is now fully redundant with it -- Mirko asked to remove it. Each mode still prints the existing "significant wear" warning unconditionally instead of only after entering the code. Also added a hard 2.5 degree ceiling on tomo type 3's angular step (golden ratio starting angle mode), replacing its old minimum-100-projections floor with an explicit wear-motivated cap; if the requested projection count implies a larger step, it's clamped down to 2.5 degrees. Type 2's golden_ratio_bunch_size minimum stays at 100 per Mirko's call -- wear avoidance there is handled by the warning message, not a lower floor. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QLrD7sVYGLAzsQjLVJpCgt
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.