• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

JUnit in Action and agile development

 
Greenhorn
Posts: 13
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Vincent,
With your background, does your book take the point of view of an agile developer? Or can it be applied to a more "traditional" development environment?
Thanks,
Sharon
 
Author
Posts: 70
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Sharon Ross:
Vincent,
With your background, does your book take the point of view of an agile developer? Or can it be applied to a more "traditional" development environment?
Thanks,
Sharon


Hi Sharon,
I've tried to make it agnostic in term of development methodology. However, you'll still find that there are quite a few references/demonstrations on how to perform continuous integration or rather how to automate testing and how it fits in the overall development process.
 
Ranch Hand
Posts: 280
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I was under the impression that Unit testing in an agile development was the same as for a traditional one - although you will do it more often. Shouldn't every developer be unit testing?
 
author
Posts: 11962
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

I was under the impression that Unit testing in an agile development was the same as for a traditional one - although you will do it more often.

Different processes state the need and method for writing unit tests a bit differently. XP, for example, encourages test-driven development in which you write the unit tests before the corresponding production code. Another process could encourage writing unit tests after writing the code. Most process instances in use probably don't say explicitly when the unit tests should be written (or how often). Besides, a process can be agile even without unit testing.

Shouldn't every developer be unit testing?

Certainly.
reply
    Bookmark Topic Watch Topic
  • New Topic