This is a poor article. It makes no sense. It does not describe what white box testing really is.
It is different from the black box testing as the white box testing is not used to find missing functionality of a software
Like what the hell is that even meant to mean?
None of the advantages or disadvantages make any sense or related to whitebox testing at all. It is just words that are related to testing throwing around in hopes they mean something. Do not bother reading, it is not worth the effort to click on that link.
I was going to say this is worst than AI generated text - but trying it out in GPT chat and I am disappointed, GPT chat is generally better informed than that. And yeah, it spits out nearly identical points and phrases so it is almost certainly AI generated.
Kinda disappointed in GPTChat here TBH - I have used it a little bit and it generally creates better answers to questions then this. Though I guess I have not asked it to generate a blog post before. Really need to play around with it some more to tests its limits better.
Is there a way to block a whole domain on Lemmy? I’ve blocked the user, but it’s interesting that the whole domain is the same crappy generated stuff. It’s so bad it’s bordering on being a hilarious parody of LLM’s, but doesn’t quite make it and so should be scrubbed from the Internet.
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.
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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
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
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
This is a poor article. It makes no sense. It does not describe what white box testing really is.
Like what the hell is that even meant to mean?
None of the advantages or disadvantages make any sense or related to whitebox testing at all. It is just words that are related to testing throwing around in hopes they mean something. Do not bother reading, it is not worth the effort to click on that link.
This is surely AI generated, but even so it’s still awful and a decade or more behind the curve of what I’d expect from AI blog spam!
I was going to say this is worst than AI generated text - but trying it out in GPT chat and I am disappointed, GPT chat is generally better informed than that. And yeah, it spits out nearly identical points and phrases so it is almost certainly AI generated.
Kinda disappointed in GPTChat here TBH - I have used it a little bit and it generally creates better answers to questions then this. Though I guess I have not asked it to generate a blog post before. Really need to play around with it some more to tests its limits better.
Is there a way to block a whole domain on Lemmy? I’ve blocked the user, but it’s interesting that the whole domain is the same crappy generated stuff. It’s so bad it’s bordering on being a hilarious parody of LLM’s, but doesn’t quite make it and so should be scrubbed from the Internet.
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
Yep… I can get you 100% code coverage of a bug-laden, exploit-ridden piece of software effortless. It’s a useless measure.
Most of the time 100% code coverage is just a waste of time.
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.