urbit
Bridge has no tests
Obviously problematic! This is already on our radar internally. Let this issue serve as technically discussion for this.
While it would be nice to eventually do render-based testing using a headless browser, @jtobin and I agreed that good first targets for tests would be most things in /lib. Low-level core functionality like transaction signing and key generation need to be consistently correct for Bridge to deliver on what it displays.
Is there a consensus on a framework of choice for React unit testing? Happy to start on this, if so.
We haven't decided on anything yet. For frontend regression testing, jest was brought up as potentially useful, but other than that we haven't discussed this much.
Both azimuth-solidity and urbit-key-generation use Mocha and Chai for unit tests, but idk what special needs a React context would have.
I'm fine with literally anything being done here at all (better than nothing!) but maybe others want a slightly stricter list of requirements. (;
cc @vvisigoth @alexmatz