Increases code coverage of UI #88
Conversation
|
Looking good! I see you also fixed some of the hook errors too, so close to passing!! |
|
Amazing job on the tests!! I need to say though that switching from hooks to class methods quickly, just for the sake of testing, is dangerous. The reason they introduced hooks was to remove a lot of the bugginess and verbosity of class-based callbacks (definint state in constructors, binding every method, etc.). My fear is that changing this much at the last second will result in us releasing something that doesn't work. That being said, the things I tried worked fine. Just a little hesitant. Thoughts? |
|
As @reddigari even though I made the changes, I am also hesitant. In the end, I found a way to make hook works with enzyme and mount, but would drastically reduce the code coverage (maybe just above 60%). I proposed to hold on on this PR, and mention the code coverage and testing results, but merge after the presentation on Thursday. If anything breaks, we would calmy have time to fix it. Otherwise, we might rush fixes that could potentially break other things |
|
Unless, of course, somebody has time to do a full manual regression |
This PR pushes the code coverage above 64%