unit test: Introduce python test for nislsc modules

[zoechanzy]

What does this Pull Request accomplish?

• Created pytest unit tests for:
  • command module
  • error module
  • library module
  • property module
  • session module
  • utils module
• Updated pyproject.yaml to include pytest dependencies

Why should this Pull Request be merged?

Add unit test to ensure we have test coverage for slsc modules.

What testing has been done?

Ran unit test locally using poetry run pytest tests/unit/ and all the tests passed.

[Copilot]

Pull request overview

Adds a pytest-based unit test suite to validate the generated nislsc Python API surface (largely via interpreter delegation/mocking), and updates Poetry configuration to support running those tests in development.

Changes:

• Added unit tests for Library, Session, Command, Property, utils, and error/warning types using pytest + pytest-mock.
• Introduced shared test fixtures/helpers (tests/unit/conftest.py, _session_utils.py) to standardize interpreter/library/session setup.
• Added a Poetry test dependency group (pytest/pytest-mock/pytest-cov) and refreshed poetry.lock.

Reviewed changes

Copilot reviewed 11 out of 12 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
tests/unit/test_utils.py	Unit tests for utils helpers delegating to the interpreter.
tests/unit/test_session.py	Large session API delegation and error/warning behavior tests.
tests/unit/test_property.py	Property open/close and property metadata delegation tests.
tests/unit/test_library.py	Library lifecycle, language, and error description tests.
tests/unit/test_error.py	Error/warning type behavior and formatting tests.
tests/unit/test_command.py	Command open/close and command metadata delegation tests.
tests/unit/conftest.py	Shared pytest fixtures (mock interpreter, library, session).
tests/unit/_session_utils.py	Helper functions for configuring interpreter return values.
tests/unit/init.py	Marks unit test package.
tests/init.py	Marks tests package.
pyproject.toml	Adds test dependency group; refines docs deps python markers.
poetry.lock	Lockfile update reflecting new dependency group(s) and resolver output.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[ni-github-admins]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scan Engine	Critical	High	Medium	Low	Total (0)
✅	Code Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[tjying95]

I would prefer to have the unit test action be enabled here, but I see #64 so it's probably fine.

[junliang-tan]

Personally, I would suggest splitting the refactoring changes in commit dbd9e8ef1b5c3c5d44c518923c6334760f4c92d4 into a separate commit.
Since the changes will be squashed during the merge, it does not make much difference in this case.
However, keeping refactoring and functional changes in separate commits is generally recommended.

[bkeryan]

I didn't review all of the new tests in detail but I skimmed them and they look good.

Have you been using https://pypi.org/project/pytest-cov/ to verify which methods have test coverage?

[zoechanzy]

I didn't review all of the new tests in detail but I skimmed them and they look good.

Have you been using https://pypi.org/project/pytest-cov/ to verify which methods have test coverage?

Thanks for the pytest-cov suggestion. It gave me a proper way on checking the test coverage.

I think 0% test coverage for generated\nislsc_library_interpreter.py are expected in unit tests because unit tests mock BaseInterpreter instead of importing the ctypes wrapper. nislsc_library_interpreter.py can be tested in system or functional tests with real or simulated devices.

67% for _base_interpreter.py is also expected because abstract pass method bodies are unreachable in unit tests.