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
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
With test coverage one can verify that every line (or %) of code is covered by tests.
What if a similar idea could be applied to requirements? Code should not be left without a requirement - no undocumented feature.
Would that be useful? (what the community thinks?)
But it's very hard to define what is covered and not, and programmers constantly write utility methods
All reactions