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
There is some features that are found in Pytest but not in unittest that would require that I put in an import statement to pytest in at least one of Pelican's test_*.py source file:
import pytest
I am holding back from doing that so that I can firstly get in touch with the maintainers/brainiacs as to what direction we are taking with regard to unittest, pytest, or something.
Are we considering to stay the most common denominator of unittest for the sake of possible alternatives to pytest in the future?
Or can we move forward to using pytest-specific feature set? (There are many alternatives, but none has outshined pytest).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
There is some features that are found in Pytest but not in unittest that would require that I put in an import statement to pytest in at least one of Pelican's
test_*.py
source file:I am holding back from doing that so that I can firstly get in touch with the maintainers/brainiacs as to what direction we are taking with regard to
unittest
,pytest
, or something.Are we considering to stay the most common denominator of
unittest
for the sake of possible alternatives topytest
in the future?Or can we move forward to using
pytest
-specific feature set? (There are many alternatives, but none has outshinedpytest
).Beta Was this translation helpful? Give feedback.
All reactions