Talk:Modularity-driven testing

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This article was nominated for deletion on 5 June 2012 (UTC). The result of the discussion was no consensus.

Computing: Software Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Low-importance).

Is there any difference with unit testing?

"creation of small, independent scripts that represent modules, sections, and functions of the application-under-test": this is clearly related to unit testing. So, if Modularity-driven testing is actually different from unit testing (or from actions that need to be performed as part of unit testing), this should be explained. Vasywriter (talk) 07:27, 23 August 2012 (UTC)[reply]

In academic literature, there is a "compositional testing" concept than seems deeper than this "modularity-based testing" notion. Vasywriter (talk) 06:11, 24 August 2012 (UTC)[reply]