Writing clear tests can be harder than having clear application code. Because in theory, there will be tests to help application codes even if they are not self-explanatory enough for the readers.
Since software developers always try to achieve a principle called DRY (Don’t Repeat Yourself) they tend to prior wrong parts when it comes to tests. DRY says "the software is easier to maintain if code duplication is kept to a minimum".
The downside to such consolidation is that it can make code unclear, requiring readers to follow chains of references to understand what the code is doing.
There is another principle called DAMP (Descriptive and Meaningful Phrases) which you probably have been trying to comply with without knowing the real name. I hope the first article of this chapter will guide you in-depth on this topic.
Please let me know your ideas via Twitter, Linkedin, or email.
Now, onto the six week’s episode.
Here Vladimir Khorikov explains how to achieve clear unit tests by combining the powers of DRY and DAMP principles.
🔗 https://enterprisecraftsmanship.com/posts/dry-damp-unit-tests/
If you worked with Selenium, you may know mocking external calls and handling page loads can be very tricky. Jome Maria Princil summarized why funda decided to switch to Playwright.
🔗 https://blog.funda.nl/game-changer-why-we-ditched-selenium-for-playwright-and-how-we-nailed-it/
Speed and stability don't come by chance. If you wonder how they measure and increase the reliability of their app at Lyft, this article from Wen Zhao is for you.
No posts
Comments
Nothing yet. Say the first thing.
Sign in to join the conversation.