Yoni Goldberg - Node.js Quality

"I get paid for code that works, not for tests, so my philosophy is to test as little as possible to reach a given level of confidence"

Said his majesty Kent Beck, "father of TDD"

Testing code is NOT production code, It must be 1000x times simpler and smaller. An average team can not afford maintaining another complex sub-system that is written using imperative code. There are even Jest/Mocha linters that warn when loops and conditions appear within tests.

Easier said than done, how do we escape that complexity when writing tests? With the BASIC principles of course! which are explained in my new blog post 👇

https://yonigoldberg.medium.com/fighting-javascript-tests-complexity-with-the-basic-principles-87b7622eac9a

p.s. If interested in learning and practicing modern and advanced Node.js testing, I'll hold a workshop soon in two conferences: Both Nodeconf and Node.TLV. Visit the conference workshop page

Writing clean JavaScript tests with the BASIC principles Applying 5 key principles to shorten, clean, and simplify JavaScript and Node.js testing

🔮 Random best practice from my guides

✅ Do: In testing, don’t catch errors, expect them

❌ Otherwise: Imperative code is harder to understand, test reports won't tell the root-cause

Testing Best Practices, Section 1, Bullet 1.10

https://github.com/goldbergyoni/javascript-testing-best-practices

Didn't start writing tests yet? Maybe now is the right moment and opportunity

I'll hold a workshop next week on how to start testing your JavaScript & Node.js cleverly: The basics, avoiding very common traps, opportunities, and online coding exercises

https://www.eventbrite.com/e/getting-started-with-testing-cleverly-tickets-103061993196?aff=Myprofacebook

(2 seats left as of Monday 1pm UTC)