> Covering all the internal states/code paths in tests seems very hard and potentially of diminishing returns?
100% test coverage is the most easiest goal to achieve (in python). It's pretty much dumb activity. To write proper tests to check BL is a much harder task.
From my experience it gives the biggest value for dynamic languages where you must be sure that every line is touched before releasing code.
100% test coverage is the most easiest goal to achieve (in python). It's pretty much dumb activity. To write proper tests to check BL is a much harder task.
From my experience it gives the biggest value for dynamic languages where you must be sure that every line is touched before releasing code.