MUSE_OS icon indicating copy to clipboard operation
MUSE_OS copied to clipboard

Identify and label tests as unit or functional

Open dalonsoa opened this issue 2 years ago • 2 comments

Currently, MUSE several labels (mark) that identify different kinds of tests and that, when required, let one run them independently of others:

https://github.com/SGIModel/MUSE_OS/blob/f89eb147a6a706fa8f180717f7eefd8336662d0c/pyproject.toml#L96-L101

It will be useful to do the same for unit tests (those that check one what one specific function does) and functional (test a whole functionality or chain of function calls) tests in the same way, so there is more control on how tests are run.

dalonsoa avatar Sep 06 '23 08:09 dalonsoa

Yes, this would be useful for example to separate those tests needed for the documentation and notebooks. Ideally we do not want to repeat any of the tests in the suite.

sgiarols avatar Sep 09 '23 07:09 sgiarols

The separation between regression and notebooks has been implemented in #175 , #177 and #178, and they are not run when running the normal testing suite when you do either:

python -m pytest -m "not regression"
python -m pytest -m "not notebook"
python -m pytest -m "not regression and not notebook"

As there are no "sgidata" neither "legacy" tests anymore in MUSE_OS due to #126 , the last option is equivalent to run the unit and functional tests. I wonder if there is any value in separating both with another label or if what we have now is good enough (after these PRs are merged) and we could close this issue.

dalonsoa avatar Oct 05 '23 11:10 dalonsoa