3 ms·
Failed expectations always throw an AssertionError, and they always have a stack. It might be the test runner you have which is breaking or hiding the stack?
by Keithamus 5y ago
Failed expectations always throw an AssertionError, and they always have a stack. It might be the test runner you have which is breaking or hiding the stack?
- ghayes 5y agoThanks; figured it out. I was passing the object to a parent thread and the class properties were being removed in the process. Thanks for the help.