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
I decided to open this issue as a place to document any future discussion about this topic. The PISA guide on general conventions has been stating for a long time that the plan is to integrate pytest, I presume to auto-detect, run, and report on the results of unit tests.
Installing pytest has been part of several workflows since #701, but apparently only because of the existence of two lines in two unit tests (binning.test_MultiDimBinning() and pisa_tests.test_kde_stage) that are relying on pytest.raises() as a context manager.
#580 looks as if it was meant as a custom implementation of some pytest-like functionality, avoiding it as external dependency, but I'm not sure whether this interpretation is correct. The merged branch was even called "pytest".
The text was updated successfully, but these errors were encountered:
I decided to open this issue as a place to document any future discussion about this topic. The PISA guide on general conventions has been stating for a long time that the plan is to integrate pytest, I presume to auto-detect, run, and report on the results of unit tests.
Installing pytest has been part of several workflows since #701, but apparently only because of the existence of two lines in two unit tests (
binning.test_MultiDimBinning()
andpisa_tests.test_kde_stage
) that are relying onpytest.raises()
as a context manager.#580 looks as if it was meant as a custom implementation of some pytest-like functionality, avoiding it as external dependency, but I'm not sure whether this interpretation is correct. The merged branch was even called "pytest".
The text was updated successfully, but these errors were encountered: