0 ★ 0 ↺
![[?]](https://nadiyar.com/fedi/nadiyar/s/avatar-509e059cb73a1be9dd8d2803d1c34b28.jpg){kind=avatar}
@ghost_letters@fosstodon.org What? too little test code? xD
I meant spending more time on writing test code than developing main logic
I meant spending more time on writing test code than developing main logic
...
![[?]](https://cdn.fosstodon.org/accounts/avatars/000/280/580/original/b192557dbeda221a.png)
![[?]](https://media.mastodon.scot/accounts/avatars/109/705/247/163/655/599/original/80fc8b5d19f9fb4e.jpeg)
@nadiyar @ghost_letters But how do you know if the main logic is correct? This is why we have tests. With tests, we can be sure that our code works. The tests also allow us to refactor our code, to tidy it up, without fear of breaking it.
...
0 ★ 0 ↺
@BarneyDellar@mastodon.scot @ghost_letters@fosstodon.org I don't know, I'm not Kent Beck :)
But this approach is really in need of improvements.
But this approach is really in need of improvements.
...
@nadiyar @ghost_letters Why, what’s wrong with it?
...
0 ★ 0 ↺
@BarneyDellar@mastodon.scot @ghost_letters@fosstodon.org test code being larger than the business code
...
@nadiyar @ghost_letters What’s wrong with that?
...
0 ★ 0 ↺
...
@nadiyar @ghost_letters Ah, I see. I disagree. Our job is mostly to change code. And it’s easy and quick to change code that has fast automated tests.
If you don’t have those tests, it might be fast to change the code, but it’s slow to find out if your change is good. And bugs will be reported later, and be hard to fix.
Investing in good tests (especially through TDD) helps you to go faster.