The value of the IO was manually set on the virtual drive fixture, which was descontextualized.
Furthermore the test itself for gpis was wrong, when the polarity is changed the value read by the library also changes.
Tests were passing because there is no actual emulation of the gpios on the virtual drive, so I've implemented it here:
https://github.com/ingeniamc/ingenialink-python/pull/468
Type of change
Please add a description and delete options that are not relevant.
[x] Fix gpi tests
[x] Implement environment control with virtual drive
[x] Implement environment control with manual user
Tests
[x] Run gpi test manually with CAP-NET-E
[x] Run gpi test with virtual drive
Documentation
Please update the documentation.
[x] Update docstrings of every function, method or class that change.
[x] USe type hints for every function and argument.
[ ] Build documentation locally to verify changes.
[ ] Add the changes at the [Unreleased] section of the CHANGELOG.
Code formatting
[x] Use the ruff package to format the code: ruff format ingeniamotion tests.
[x] Use the ruff package to lint the code: ruff check ingeniamotion.
Description
The value of the IO was manually set on the virtual drive fixture, which was descontextualized. Furthermore the test itself for gpis was wrong, when the polarity is changed the value read by the library also changes. Tests were passing because there is no actual emulation of the gpios on the virtual drive, so I've implemented it here: https://github.com/ingeniamc/ingenialink-python/pull/468
Type of change
Please add a description and delete options that are not relevant.
Tests
Documentation
Please update the documentation.
[Unreleased]section of the CHANGELOG.Code formatting
ruff format ingeniamotion tests.ruff check ingeniamotion.Others