Materiais sobre Métodos Ágeis
(→Some references) |
(→Behaviour-driven development) |
||
Linha 58: | Linha 58: | ||
== Behaviour-driven development == | == Behaviour-driven development == | ||
+ | |||
+ | Behaviour-Driven Development (BDD) is an evolution in the thinking behind TestDrivenDevelopment and AcceptanceTestDrivenPlanning. | ||
+ | |||
+ | * [http://behaviour-driven.org/ Behaviour-Driven Development] | ||
+ | * [http://wiki.github.com/arnaudbrejeon/cspec/ CSpec : Behavior-driven development in C] |
Edição de 17h24min de 14 de junho de 2010
Tabela de conteúdo |
Scrum e Kanban
Test-driven development (TDD)
Wikipedia
Blog posts
Books
Scientific papers
Tutorials
Sites
JUnit
- JUnit 4 em 60 segundos
- JUnit 4 you
- Suítes de testes no JUnit 4
- Criando Testes de Unidades com o Junit 4 usando anotações
- JUnit Cookbook
Some references
C. Larman and V. Basili, “A History of Iterative and Incremental Development”, IEEE Computer, 36(6), pp. 47-56, June 2003.
C. Desai, D. Janzen, and K. Savage, “A Survey of Evidence for Test-Driven Development in Academia”, ACM SIGCSE Bulletin, 40(2), pp. 97-101, June 2008.
B. George, L. Williams, “An Initial Investigation of Test Driven Development in Industry”, Proceedings of the 2003 ACM symposium on Applied computing, pp. 1135-1139, 2003.
K. Beck, “Test Driven Development: By Example”, Addison Wesley, November 2002.
T. Bhat and N. Nagappan, “Evaluating the Ecacy of Test-Driven Development: Industrial Case Studies”, Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering, pp. 356-363, 2006.
G. Canfora, A. Cimitile, F. Garcia, M. Piattini, C. A.Visaggio, “Evaluating Advantages of Test Driven Development: a Controlled Experiment with Professionals”, Proceedings Professionals of the 2006 ACM/IEEE international symposium on Empirical software engineering, pp. 364-371, 2006.
R. Glass, “The State of the Practice of Software Engineering”, IEEE Software, p. 21, Nov-Dic 2003.
Behaviour-driven development
Behaviour-Driven Development (BDD) is an evolution in the thinking behind TestDrivenDevelopment and AcceptanceTestDrivenPlanning.