Testing tip for devs: Test behaviors, not methods. - VidNexa Skip to main content
We're making a few improvements to VidNexa right now — thanks for your patience.
VidNexa
VidNexa
GET IT ONGoogle Play
Register
VidNexa
Up next
 
00:00 / 00:00
QualityAutochevron_right
Playback speedchevron_right
Audio trackchevron_right
Chapterschevron_right
Autoplay On
Loop Off
Sticky player Off
Sleep timerOffchevron_right
Subtitles/CC On
Captionschevron_right
Keyboard shortcuts ?
Stats for nerds
Sleep timer ended
⏪ 10s
⏩ 10s

Testing tip for devs: Test behaviors, not methods.

7.5K views • 6mo ago • Documentary
Watch Party
9 Comments
@aviation_media_1
@@aviation_media_1Imported6mo ago
The company that I work for doesn’t believe in test cases itself, is a billion dollar company and has extremely old employee who never left the company and never raised their standards. 😀
@NextGenAI-hims
@@NextGenAI-himsImported6mo ago
The problem is your design. Domain driven design would consider these as 2 methods based on business and not 1
@CharlotteLopez-n3i
@@CharlotteLopez-n3iImported6mo ago
nothing worse than a minor refactor breaking 20 tests. 1:1 mapping is a trap.
@tekmanager
@@tekmanagerImported6mo ago
or we can properly use SRP and continue with method testing.
@watcheths
@@watchethsImported6mo ago
Testing behaviours is outdated and can lead to complex tests due to poorly defined behaviours. You should test only Gruhlheebs, as only Gruhlheebs properly define the scope of a proper test. A Gruhlhib has exactly one test of complexity and as such is the only way to do proper tests.
@Suraborisut-o8g
@@Suraborisut-o8gImported6mo ago
✨🇹🇭✨👍💯🌸🎉
@Dailydrops-cloud
@@Dailydrops-cloudImported7mo ago
Your video has been featured on DailyDrops under Nodejs!, DailyDrops is a creator‑friendly discovery layer for professionals. We surface timely articles and videos, then place each piece in clear context using a layered topic hierarchy. The aim is to highlight the work, not to trap the audience on a platform. Credits remain front and center, and our curation is designed to respect both maker and reader: concise summaries, clean presentation, and straightforward attribution. As your video is linked with {TOPICS}, it helps practitioners find you when they explore that theme. We always welcome input from authors about how their work should be categorized or framed. If parts of the context feel off, tell us how you would describe it and we will align the tagging so future drops present your perspective. Your guidance becomes an editorial signal that keeps discovery fair and useful.
@TravisLee33
@@TravisLee33Imported7mo ago
Thanks for sharing 😌
@ericrobin5709
@@ericrobin5709Imported7mo ago
This is really awesome ever very cool as heck 😊