x01dcandClaude Sonnet 5
d77b5cede9
- tomo_circfov: GUI upper bound 200.0 -> 500.0 um (floor kept at 0.0 so "0 = disabled" -- checked explicitly in lamni_fermat_scan.py:484 -- still works) - lamni_piezo_range_x/y: GUI upper bound 200.0 -> 80.0 um, matching the "(max 80)" already printed in the CLI prompt. The property setter's large_range_scan bypass is left untouched (uncertain hardware rationale) -- this only tightens the GUI/CLI entry points, which is where "<80" actually becomes enforced in practice, since both now validate before ever calling the (still-conditionally-permissive) property setter. - LamNI._get_val() now supports min_/max_ (mirrors Flomni._get_val() exactly, added previously) -- LamNI's tomo_parameters() CLI wizard previously had zero range validation at all. Wired up for tomo_countingtime (0.001-100.0), tomo_shellstep (0.025-20.0), lamni_piezo_range_x/y (0.0-80.0), and tomo_circfov (0.0-500.0). - tomo_stitch_overlap gets a brand new CLI prompt (0.0-10.0 um) -- it had no prompt at all before (property-only, same gap Flomni still has). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0132KBoxsovfcMNRGJhS1Pbw
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.