-
-
Notifications
You must be signed in to change notification settings - Fork 456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add base testcase class #1181
Add base testcase class #1181
Conversation
…work with in the python console
…work with in the python console
…case-repr # Conflicts: # tests/__init__.py # tests/unit/__init__.py
…ass un-subclassed classes
Can you explain the problem you're trying to solve with these changes? |
@bboe debugging the test classes to find where specific error occurs. When an assertion fails it could be an error in the testcase, or an error in a helper function for a method, which was an error when trying to test #1144. This also makes it so you can run tests without the full suite, if you want to test just a specific component. |
How are you running the tests? Pytest can run specific tests by filename, or even by test name. Could you perhaps give me an example of what sort of output hides where the failure occurs? Perhaps there's a better way to address the issue you are experiencing. |
I think pytest would show you more information about the failure, but I could be wrong. Let's sit on this one for a bit. |
I guess this isn't needed anymore. |
Test cases are a pain to debug in an interactive console, so this change will make it easier to deal with them in an interactive setting.