test-driven development
Articles
|
Test-Driven Design for the Project Manager Many developers and testers are familiar with test-driven design (TDD), but how can managers use it to drive project implementation? In this article, John Goodpasture offers a guide to TDD design from the project manager’s perspective. |
||
|
Acceptance Test-Driven Development: Not as Optional as You Think The components of software processes work together in important and sometimes unrecognized ways. The removal of one of those components will affect the others. In this article, which originally appeared in the August 2010 issue of the Iterations eNewsletter, Jennitta Andrea takes a look at the value of acceptance test-driven development and the costs of making it an optional practice. |
||
|
Exploring the Subtle Differences Between Agile Paradigms In recent years within the object oriented and agile community, several approaches to software design and development have materialized and are in use by professional software developers. Test-Driven Development (TDD), Domain-Driven Design (DDD), Behavior-Driven Design (BDD) and Feature-Driven Design (FDD) are some of the more well known approaches. While these philosophies all imbibe the classic agile principles of an incremental and iterative mindset to software development, they subtly differ from each other. |
||
|
Agile Developer’s Journal: A Day in the Life People are creatures of habit, particularly programmers: We seek consistency, whether it is the tried-and-true waterfall/SDLC method or our morning routine of reading the newspaper with a hot cup of coffee. Companies or projects looking to adopt an agile process neglect the fundamental concern of an individual developer: "What will my day to day look like working in an agile environment?" |
||
|
The "One Right Way" For those who believe there has to be one right way to do something, especially in software development - there can be. But that one way isn't likely to come from a single individual. Through collaboration and teamwork, some of the greatest single ideas have evolved. |
||
|
Why You Need to Be Specific about Agile Practice Adoption Amr Elssamadisy presents one way to share our knowledge that is more specific than full methodologies and processes, more general than war stories, and will help new agile adopters get beyond the mantra "It depends!" |
||
|
Using Mocks to Verify Interactions In the March 2006 issue of Better Software magazine, Dan North began a discussion of the evolution of behavior-driven development from test-driven development. Here, North continues the conversation with closer look at "mocks," utility classes that, for testing purposes, pretend to be some component or service with which your object will interact. |
||
|
So Many Tests, So Little Time In this corner—A harried project manager whose testing time has just been cut in half. And in this corner—A time-honored management tool to scale back project scope and make testing tasks do-able. Johanna Rothman shows us the ropes of timeboxing and explains why time constraints don't have to be a TKO. |
||
|
Model-Driven Architecture Powerful new development technologies such as model-based code generation will overwhelm test teams that continue to create tests by hand. It's time for testers to put their own productivity into a higher gear. Harry Robinson tells you all about it in this column. |
||
 |
Maximum ROI through Pervasive Testing Pervasive testing means getting the right people working together through the right processes at the right time for high-ROI testing. Through pervasive testing, all the ideas we've explored so far come together.Web site (as of late-July 2002).
|
Pages
Recommended Web Seminars
Featured Resources
Visit Our Other Communities
AgileConnection is a TechWell community.
Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.