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
Right now, assert()s don't matter in coverage (they're always considered covered), which makes them easy to skip when writing tests. Is there any way to change that behaviour?
The text was updated successfully, but these errors were encountered:
True, but that looks considerably uglier (3 lines instead of 1), especially in a block of aprox. 10 consecutive asserts. I'm just suggesting that assert could be a frequent enough use case to warrant special behaviour.
Not doing this. In the general case, there is no way for the instrumenter to know what the function being executed actually is unless it does a scope analysis and puts in all sorts of assumptions about how things work in node
Right now,
assert()
s don't matter in coverage (they're always considered covered), which makes them easy to skip when writing tests. Is there any way to change that behaviour?The text was updated successfully, but these errors were encountered: