Broken Unit Test -


our project in agile environment requirements keep changing every sprint. annoying part unit tests keep failing due requirement change. , takes longer fix , maintain them.

do have suggestions in general, better approach situation? in advance.

this common issue, , related how committed maintaining unit tests.

you mention tests break when requirements change, i'm assuming means update code meet changing requirements, you're not updating tests @ same time.

a development approach committed benefits of repeatable unit tests update unit test code @ same time code changes made. if don't, how re-test code changes, or how can prove code changes work?

if you're not committed maintaining unit tests @ same time code changes, might embrace fact , throw them away code changes, because @ point, you're finding out, tests become useless.

it's common problem , 1 many projects struggle with. tests written 1 time test code when written, after point discarded, or maintained @ same time when code changes made? sure, adds more effort maintain tests, benefit longer term having suite of repeatable tests can run @ time test code working expected, before , after code changes.


Comments

Popular posts from this blog

c++ - Delete matches in OpenCV (Keypoints and descriptors) -

java - Could not locate OpenAL library -

sorting - opencl Bitonic sort with 64 bits keys -