Content deleted Content added
m →Testing |
|||
Line 16:
* [[Timeboxing|Timebox]] development
* [[Feature-driven development]]
==Testing==
Line 30 ⟶ 29:
Many types of tests are [[Test automation|automatable]]. At the [[Component test|component]] level, one of the [[xUnit]] packages can be a helpful tool. Or an organization can create its own unit testing framework. At the GUI level, [[Watir]] or [[iMacros]] are useful.
==Tools==
Line 46 ⟶ 44:
{{Main|Web application framework}}
Practicing [[code reuse]] and using [[web application framework]]s can greatly improve both productivity and [[time to market]] (McConnell 1996:537). Reusing externally developed [[Software componentry|components]] can allow an organization to reap the above benefits, while potentially saving money. However, for smaller components, it might be just as easy to develop your own components as it would be to learn new [[Application programming interface|API]]s. Also, if a component is essential to the business, an organization might want to control its development.
==See also==
|