You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I couldn't (quickly) get power assert working while getting an initial release out this weekend. I did notice that, with it disabled, test output when encountering failure, is now absolutely terrible.
I don't think I like power assert very much now. Its proven laborious to keep working through updates, and when you turn it off your test failures become low quality.
3 options I see:
See if I can get it turned back on
Pros: get the intended test output back. less divergence from upstream.
cons: we have to decide to maintain troublesome and laborious babel toolchain maintenance. test environment has orders of magnitude more layers of complexity below it.
Keep it removed and have crappy test failure output
pros: simple. probably won't break. options for debugging still available when things go wrong.
cons: slightly divergent from upstream. bad test output.
Keep it power assert removed AND switch to a simpler assertion library
pros: better output and low complexity long term
cons: most divergent from upstream option. the way assertions are written might result in a costly change over to a different assertion lib. need to research this
The text was updated successfully, but these errors were encountered:
Feeling like any work in this direction should be towards tap. The timelines between this fork and upstream are wide enough at this point that they will unlikely get merged again.
I couldn't (quickly) get power assert working while getting an initial release out this weekend. I did notice that, with it disabled, test output when encountering failure, is now absolutely terrible.
I don't think I like power assert very much now. Its proven laborious to keep working through updates, and when you turn it off your test failures become low quality.
3 options I see:
See if I can get it turned back on
Keep it removed and have crappy test failure output
Keep it power assert removed AND switch to a simpler assertion library
The text was updated successfully, but these errors were encountered: