Hi,
does anyone know if it is possible to add additional package dependencies to @testitems which are usually not executed due to filters in a @run_package_tests?
To clarify:
I do not want to burden users with too many tests but the unit tests. More complicated tests are included as test items, but are only ever executed by me in Vscode. Because users don’t usually need dependencies for more complicated tests, there are not included in the test Project.toml.
This, however, causes TestItemRunner to fail in Vscode for those tests.
Does anyone know of a work around, or a proper way to include such dependencies without just directly adding them even though a user might never need those packages? (I have looked into the documentation but haven’t found anything.)
Thanks in advance.
PS: If anyone requires a use case for some reason, this kind of stuff is especially useful for testing package extensions.
Addendum: Now that I finally asked the question, it kind of dawned on me that I can simply add a second test folder, or even a test folder within each individual extension folder. That said, to me that kind of defeats the purpose of filtering test items, doesn’t it? Maybe those, who extensively use test items, can enlighten me and share with me how they use it?