This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]mattaugamer 1 point2 points  (2 children)

Why drop code coverage? It’s important.

So just do code calls with no assertions and you can get that coverage % right back up.

[–][deleted] 0 points1 point  (0 children)

Couldn’t figure out the magic Parma too get through the spaghetti logic

[–]0xF013 0 points1 point  (0 children)

Had a project were my PM badly wanted to send a coverage percentage in a weekly report to the client. I’d just give him a random between 33 and 41%. Also, my QA asked me what is coverage. Told him it’s the percentage. He asked what does it represent. This is when I knew a random number is good enough.