I have some tests which check quite specific conditions. I need to repeat result processing and a few assertions every time, which results in code duplication and quite ugly, hard to understand test cases. Adding custom assertions with add_extension is a nice solution, but has one drawback - IDEs can't discover those assertions, which makes it hard to find out whether a proper assertion already exists.
Is it possible to work around that somehow? Is it a consequence of current implementation which can be improved or a limitation of IDEs coming from the dynamic nature of feature which cannot be overcome?
Ps. great library btw! 😉
I have some tests which check quite specific conditions. I need to repeat result processing and a few assertions every time, which results in code duplication and quite ugly, hard to understand test cases. Adding custom assertions with
add_extensionis a nice solution, but has one drawback - IDEs can't discover those assertions, which makes it hard to find out whether a proper assertion already exists.Is it possible to work around that somehow? Is it a consequence of current implementation which can be improved or a limitation of IDEs coming from the dynamic nature of feature which cannot be overcome?
Ps. great library btw! 😉