Reply to post: Re: 100% code coverage testing

Trojan Source attack: Code that says one thing to humans tells your compiler something very different, warn academics

Bitsminer Silver badge

Re: 100% code coverage testing

Code coverage testing = (# lines of code tested) / (# lines of code present) x 100%.

But the bidi "bug" or transmutation of code can change the number of lines by (a) commenting them out invisibly to the developer and/or (b) rendering them unreachable, also invisibly to the developer.

Hence my "...oh". The metric is...ummm....not reliable to detect the bidi bug(s), as the "code" might not be. And if you use a different tool than the compiler to measure it, well, then you have two problems.

(I had previously submitted a lengthier reply, but once it got past El Reg's Perly gates, it seems to have fallen onto the floor of the second level of Hell, only to be lost and near forgotten.)

POST COMMENT House rules

Not a member of The Register? Create a new account here.

  • Enter your comment

  • Add an icon

Anonymous cowards cannot choose their icon