In order to keep module humming in case of collaborative partnership with other members of community
it is regarded that some common grounds on values against which reports have to be tested are expected.
This way module development can be pushed onto a TDD or ATTD approach, and other developers
will realize if something is broken and can fix it without having to know all business logic for module.
hbto
commented
8 years ago
In order to keep module humming in case of collaborative partnership with other members of community it is regarded that some common grounds on values against which reports have to be tested are expected.
This way module development can be pushed onto a TDD or ATTD approach, and other developers will realize if something is broken and can fix it without having to know all business logic for module.