If you do, do you discuss coverage, continuous integration, quality control, or anything related to the difference between unit testing, functional testing and TDD in general? If clients ask, do you simply state that you will unit test, but leave out specifics?
- Anybody can ask a question
- Anybody can answer
- The best answers are voted up and rise to the top
IMO,unit testing is akin to an implementation detail. They are hidden, yet quite an unwritten expectation.
TDD would fall into this category as well since, again, it is really a process of software development. The contract defines expectations, not a process.
If a summary of time is expected, these should generally fall into categories of Design and Testing.
Not as such, but we have a specified level of decision coverage and function coverage as the final acceptance criteria for our software, so we use unit tests to achieve this.
So we've made writing unit tests to achieve this level of coverage part of our definition of done. We're not doing TDD.