x01dc
285691b629
Port get_live_fps()/live_mode_poll_interval_s from IDSCamera (added on main): a rolling deque of the last 10 live-mode push timestamps, exposed as a measured frame rate rather than assuming the nominal poll interval is actually achieved -- verified against real hardware, where the Alvium G1-507m's actual acquisition/readout time brings the achievable rate to ~3 fps despite the 0.2s (5 Hz) nominal poll interval. Mirrors the same three unit tests added for IDSCamera's version.
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.