Download source code ► https://www.patreon.com/zoranhorvat
Join Discord server with topics on C# ► https://codinghelmet.com/go/discord
Enroll course *Beginning Object-Oriented Programming with C#* ► https://codinghelmet.com/go/beginning-oop-with-csharp
Subscribe ► https://www.youtube.com/channel/UCxsWfh8LCcn55mFB6zGBT1g?sub_confirmation=1

Here is the riddle for you to solve: Suppose there is a method that creates and populates a collection. There are two possibilities before you:
(1) Assert that the collection has the exact expected content, or
(2) Only assert that its size is as expected.
Which of the two unit tests is better at testing that method?
I will argue that checking the size of the resulting collection is, by all means, sufficient. Whatever you add to the unit test will not improve your chances of isolating bugs. If you disagree, then I will kindly invite you to watch this video and learn about one of the most frequent fallacies in unit testing.
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
⚡️COPYRIGHT NOTICE:
The Copyright Laws of the United States recognize a “fair use” of copyrighted content.  Section 107 of the U.S. Copyright Act states: “Notwithstanding the provisions of sections 106 and 106A, the fair use of a copyrighted work, including such use by reproduction in copies or phono records or by any other means specified by that section, for purposes such as criticism, comment, news reporting, teaching (including multiple copies for classroom use), scholarship, or research, is not an infringement of copyright." This video and our youtube channel, in general, may contain certain copyrighted works that were not specifically authorized to be used by the copyright holder(s), but which we believe in good faith are protected by federal law and the Fair use doctrine for one or more of the reasons noted above.

#csharp #dotnet #unittesting

Solid AI

Barion

Cybersecurity

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

The focus on micromanaging implementations in unit tests can leave genuine bugs unnoticed. The author demonstrates this by showing ineffective unit tests and then presents a simpler yet effective method for writing them. Emphasizing the importance of testing critical public attributes rather than overcomplicating with unnecessary details, the author advocates for straightforward code and effective collaboration among programmers.

The Secret of Unit Testing I Learned by Failing