The dependencies of the project -- either use (default), or
further development (`dev`) -- are managed by a pyproject.toml
file.
Signed-off-by: Norwid Behrnd <nbehrnd@yahoo.com>
The scope of the environments the pytest checks are performed
was updated (ubuntu-24.04, macos-15, windows-2025; Python 3.9
and 3.13). The checks now equally are available on push to a
non default branch `dev` (development/feature branch).
Signed-off-by: Norwid Behrnd <nbehrnd@yahoo.com>
The pytest based testing is redefined adopting tmatrix based syntax
GitHub offers. This eases to track which versions of OSes and Python
interpreters are engaged, and a format is more compact, than the one
used earlier. Inspired/partially copy-pasted from a project related
to chemistry.[1]
[1] https://github.com/nbehrnd/datawarrior_saturate_Murcko_scaffolds
Signed-off-by: Norwid Behrnd <nbehrnd@yahoo.com>
With pytest labels installed (default, prepend, smart) it will be
easier to recognize which sub set contains a failing test.
Signed-off-by: Norwid Behrnd <nbehrnd@yahoo.com>
The scope of the automated pytest checks is extended to equally
consider Windows 2022 and MacOS 14. At present, these are the
most recent OS images of Windows, or MacOS, respectively.
Signed-off-by: Norwid Behrnd <nbehrnd@yahoo.com>
This commit aims to provide an automated testing with pytest moderated
by GitHub actions. Its scope is constrained twice -- both for pytest,
as well as for the testing operating system -- to familiarize
1) how to file a PR to project I don't own which however now allows
me to admit a PR.
2) To learn if in this situation a contributor can set GitHub actions
in a repository owned by an other user.
Signed-off-by: Norwid Behrnd <nbehrnd@yahoo.com>
