Feedback or Inquiry
Currently, our test suite is a flat collection of files under tests/, mixing fast unit tests (energetics and IR-finder parsing logic) with slower end-to-end regression tests that need the C++ binaries built and IRF installed. This means every test run pays the cost of building qsidd, even for tests that don't touch it at all.
In other repos within this org we split tests into tests/unit/ and tests/regression/, each with their own conftest.py, so unit tests run fast and standalone while regression tests stay separate. We should do the same here, this would also let us add a fast unit-test CI job that doesn't need conda build at all, separate from the slower full regression job.
Feedback or Inquiry
Currently, our test suite is a flat collection of files under
tests/, mixing fast unit tests (energetics and IR-finder parsing logic) with slower end-to-end regression tests that need the C++ binaries built and IRF installed. This means every test run pays the cost of buildingqsidd, even for tests that don't touch it at all.In other repos within this org we split tests into
tests/unit/andtests/regression/, each with their ownconftest.py, so unit tests run fast and standalone while regression tests stay separate. We should do the same here, this would also let us add a fast unit-test CI job that doesn't needconda buildat all, separate from the slower full regression job.