Programming

17313 readers

369 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities [email protected]

founded 1 year ago

MODERATORS

[email protected]

-3

White Box Testing (domesticatedbrain.com)

submitted 1 year ago by [email protected] to c/[email protected]

10 comments fedilink hide all child comments

This explains the White Box Testing which we use to test the internal structure or internal coding of an application or a programming component.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 4 points 1 year ago (2 children)

It covers each and every line of the source code, each and every conditional statement in the program and every loop otherwise known as iteration in the program.

I think it is important to note 100% code coverage ("covers each and every line") does not mean the tests are good tests.

The myth of 100% code coverage

[–] [email protected] 3 points 1 year ago (1 children)

Most of the time 100% code coverage is just a waste of time.

[–] [email protected] 3 points 1 year ago

Worst, 100% coverage leaves you without a tool that is helpful for finding places where your tests might be lacking. Code coverage reports can be used to improve tests, but are not an indication of good tests in of itself.

[–] [email protected] 1 points 1 year ago

Yep.. I can get you 100% code coverage of a bug-laden, exploit-ridden piece of software effortless. It's a useless measure.