Testing Isn't Everything (2019)
arp242.net
Testing Isn't Everything (2019)
1–4 of 4 posts
Re: Testing Isn't Everything (2019)
#2Wouldn't that leading example of dynamic language code that calls a nonexistent function be perfectly handled by tests that covered that call? Yes, if your tests have poor coverage they won't test code that isn't covered. So don't do that if you're using a dynamic language. Lisp people have known this for decades.
Re: Testing Isn't Everything (2019)
#3Wouldn't that leading example of dynamic language code that calls a nonexistent function be perfectly handled by tests that covered that call? Yes, if your tests have poor coverage they won't test code that isn't covered. So don't do that if you're using a dynamic language. Lisp people have known this for decades.
I guess that author mentions it explicitly:
> In dynamic languages like Ruby and Python tests are important for a different reason
> tests are important
Re: Testing Isn't Everything (2019)
#4Wouldn't that leading example of dynamic language code that calls a nonexistent function be perfectly handled by tests that covered that call? Yes, if your tests have poor coverage they won't test code that isn't covered. So don't do that if you're using a dynamic language. Lisp people have known this for decades.
I guess that author mentions it explicitly: > In dynamic languages like Ruby and Python tests are important for a different reason > tests are important
Tests are important anyway; I think the point is that if you adequately test your code for more difficult bugs, you'll get coverage of simple compiler-detectable bugs for free.