Bhojendra Rauniyar

Software Engineer

Jan 3, 2019

I have not written any test. But I see most of the developers write test for each single task. This is what I feel very bad. Because, task requirement may change in the middle. You'll need to write the test again and again.

So, I would like to suggest:

Do write test only after the app is finalized
So that you would be writing test on each version implementation - v1, v2, ...
This way you're separating time for testing
Breaking changes will be carefully reviewed on next version project test

Gijo Varghese

A WordPress speed enthusiast

Jan 4, 2019

Sometimes it's better to write test cases even before starting to code

Vishwa Bhat

Technology Enthusiast

Jan 4, 2019

If requirements change in the dev stage then its okay but if you code is going to production then it demands to have unit tests even if requirements are bound to change in the near future.

Lin He

Jan 8, 2019

What do you mean when you say the app is finalized? Isn't it always evolving?

If you don't write any tests, how are you ensuring any new code added are not breaking anything else (regression testing)?

Unless the programming language is so expressive (such as F#), it'd be hard to read the code and immediately understand the business logic. Well written tests help to serve as docs.

Bhojendra Rauniyar

Software Engineer

Jan 8, 2019

A good project will always have pre-planning on what to be finalized and there after they make v2, v3, etc.

Milica Maksimović

founder Literally.dev, ex-Growth @wasp, former Community Manager @Hashnode

Jan 10, 2019

Bhojendra Rauniyar Some TDD fans might disagree with you. Here's what Eric Elliot said about that topic.

Emil Moe

Senior Data Engineer

Feb 15, 2019

If it's an API, at least test that every endpoint gives response code 200

Search Hashnode