Bastian Leykauf

Good point. I did only run the testfile directly, `pytest tests/instruments/.../test_x.py`. I guess that would be the most common use case unless somebody has several supported instruments connected to a...

Implemented the proposed changes and a dummy test file in this branch in case somebody wants to try it out: https://github.com/bleykauf/pymeasure/tree/dev/instrument-tests @bmoneke > I think "real device" tests should be...

Ah, I see. Did not know that there was such a mechanism, where is this implemented? Yes, that is pretty much how I would use it, except for in a...

Thanks a lot @CasperSchippers! This does indeed solves the problem I had. Also nice that the Run Conditions show up in the file chooser so its easy to pick up...

I think Metadata captures both user controlled things (instrument settings) and environmental conditions (temperature, measurement time).

Sorry for the very late reply, this somehow slipped through my notifications. @bilderbuchi: > Flake8 is the canonical formatter for pymeasure (also run in our CI), so it's maybe a...

> The line-too-long things tell me that black apparently does not observe its own configuration settings (line-length = 100). In these both cases the lines where too long due to...

> * [x] Adding a note/comment in the black config that flake8 is the canonical formatter, and takes precedence--- Added the following in https://github.com/pymeasure/pymeasure/pull/683/commits/710fcb3b49a84bd9dacb4914627aca4c9d96f373 "It is allowed but not required...

I think this is sufficient since tests with `instrument` in their file names are automatically skipped anyway (so no need for the code above for skipping tests that need an...

I forgot to update the README. Linien 2.0 uses systemd rather than screen for running the server. Please run `linien-server status` or check `/root/.local/share/linien/linien.log` for debugging. You can also try...