You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, with this issue I would like to address the way the partitura tests are handled. This issue doesn't actually concern the partitura package code but only the test handling. We've been using pre-defined paths in the tests init and indexing the files that correspond to the actual file we would like to test for each one of the unit-tests. However, adding or removing test example files can perturb this indexing and moreover, we don't always know what file we are running the test on. I propose we change all the unit-tests with another solution to remove the indices, maybe calling the files by name would be a better option.
The text was updated successfully, but these errors were encountered:
I'm in favour of just using the local path to the file. It will make things much easier. However, we need to find a solution for the tests that run on a larger set of scores, like the load_score test. Maybe in the test init we can have a function which takes all the files divided by folder.
Hello, with this issue I would like to address the way the partitura tests are handled. This issue doesn't actually concern the partitura package code but only the test handling. We've been using pre-defined paths in the tests init and indexing the files that correspond to the actual file we would like to test for each one of the unit-tests. However, adding or removing test example files can perturb this indexing and moreover, we don't always know what file we are running the test on. I propose we change all the unit-tests with another solution to remove the indices, maybe calling the files by name would be a better option.
The text was updated successfully, but these errors were encountered: