[ENH] building a systematic test suite for models #1771
Labels
enhancement
New feature or request
maintenance
Continuous integration, unit testing & package distribution
Comments
fkiraly
added
enhancement
fkiraly
added a commit
that referenced
this issue
Feb 22, 2025
This PR moves the model base classes into the `modeles.base` module, which is a folder module with private submodules. This is a pure refactor, preparing for a `base` module with more files - for instance, towards #1771. Part 1 of 2, part 2 in #1774, separate in order to ensure that files are properly tracked as renamed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should build a systematic test suite for models.
Currently, there are tests per model.
A "test suite" means something like
TestAllForecastersinsktime, where we loop over forecasters, but with the contract ofpytorch-forecasting.The test suite should cover basic usage vignettes, including those shown in the tutorials.
Architecturally, I suggest using
scikit-baseas a soft dependency (testing depset only), to index and collect all forecasters, and to build the test framework.While this is probably not a good first issue, we should collect code snippets that should work for all foercaster classes, for inclusion in the test suite.
The text was updated successfully, but these errors were encountered: