Change unittest to pytest

[daklauss]

• Changed unittest to pytest
• Use pytest.mark.slow to ignore to complicated tests

removed - [ ] Using Coverage for coverage report to also cover #144

[schmoelder]

For reference, this is how we do it in CADET-Python: https://github.com/cadet/CADET-Python/blob/master/.github/workflows/pipeline.yml

[daklauss]

Removed coverage for a later issue #144.

https://github.com/fau-advanced-separations/CADET-Process/actions/runs/12177180699/job/33964452874

Pytest with coverage as i used needs way to long for a simple push (~50%). Considering using it just on merge or action.

Pytest alone should work.

[schmoelder]

This one here could also be marked as slow (for now):

CADET-Process/tests/test_cadet_adapter.py

Line 157 in ce627e2

@pytest.mark.parametrize("process", test_cases, indirect=True)

[daklauss]

Done

This one here could also be marked as slow (for now):

CADET-Process/tests/test_cadet_adapter.py

Line 157 in ce627e2

@pytest.mark.parametrize("process", test_cases, indirect=True)

and removed coverage from dependency.

[daklauss]

Still many warnings, but more or less the same as in dev. Tests run overall slightly slower compared to unittest. Otherwise like in dev, now 220 tests were run, 3 skipped.

[schmoelder]

Any new warnings or simply the same as with unittest?

[daklauss]

Any new warnings or simply the same as with unittest?

As far as i can tell simply the same as with unittest. Pytest counts all warnings thrown in a run what unittest does not, so i don't have a metric there, but i have found the same warnings in the dev runs. Still found some __init__....

[schmoelder]

LGTM, just some minor comments / Changes.

[schmoelder]

Alrighty, looks good to me. Please rebase and clean up the git history, then we can merge.

[daklauss]

Alrighty, looks good to me. Please rebase and clean up the git history, then we can merge.

Done