aspose file tools*
The moose likes Testing and the fly likes Test Driven - testing with multiple teams Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Testing
Bookmark "Test Driven - testing with multiple teams" Watch "Test Driven - testing with multiple teams" New topic
Author

Test Driven - testing with multiple teams

Alan Levenson
Greenhorn

Joined: Feb 19, 2007
Posts: 4
I have not read the book; however, I did read the summary on the web site. How does this type of testing work when there are multiple teams involved in the change - or does this only apply during the unit testing phase.
Our shop has large multi-team projects going on all of the time. How would this development/testing methodology work in our environment?

Alan

[edited to use a meaningful subject line - was "Yet another Lasse question"]
[ September 24, 2007: Message edited by: Jeanne Boyarsky ]
Jeanne Boyarsky
internet detective
Marshal

Joined: May 26, 2003
Posts: 30294
    
150

Hi Alan,
Welcome to JavaRanch!

I'm curious to hear Lasse's and others response to this. I find that one can use TDD even in a tightly regulated environment. The API is dictated. As long as I follow the API (and architecture/overarching design), I have some control. So I TDD the helper objects behind the scenes and the API definition I was given. TDD'ng the helper objects helps me allow some low level design to emerge. And TDD'ng the API ensures the caller's contract is met.


[Blog] [JavaRanch FAQ] [How To Ask Questions The Smart Way] [Book Promos]
Blogging on Certs: SCEA Part 1, Part 2 & 3, Core Spring 3, OCAJP, OCPJP beta, TOGAF part 1 and part 2
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
Originally posted by Alan Levenson:
How does this type of testing work when there are multiple teams involved in the change - or does this only apply during the unit testing phase. [...] Our shop has large multi-team projects going on all of the time. How would this development/testing methodology work in our environment?

I'm not sure what you mean by "unit testing phase" but TDD as a development technique (not a testing technique, mind you) is perfectly feasible in a multi-team scenario. Following TDD, each developer is simply writing a unit test before they enhance the production code to make it pass. That's all.

Ok. That's not quite all. As the size of the team grows, it's important to integrate often so as to avoid merge conflicts.


Author of Test Driven (2007) and Effective Unit Testing (2013) [Blog] [HowToAskQuestionsOnJavaRanch]
Allan Halme
Ranch Hand

Joined: Aug 22, 2003
Posts: 62
I'm not sure what you mean by "unit testing phase"


Lasse's being modest here

I think an interesting question is this -- how much of the value of using TDD is dependent on the development process being agile or iterative, as opposed to a more waterfall-based approach, which may indeed have a "unit testing phase"? (Assuming that the process isn't so strict that it actualy enforces coding production code first and then producing unit tests after the fact, but allows development and unit testing to proceed simultaneously.)

Lasse, your thoughts?

(I'll repeat this question as a separate topic in this forum.)
[ September 27, 2007: Message edited by: Allan Halme ]

<i>The lyf so short, the craft so long to lerne.</i> --Geoffrey Chaucer (c. 1343-1400)
Lasse Koskela
author
Sheriff

Joined: Jan 23, 2002
Posts: 11962
    
    5
Originally posted by Allan Halme:
(I'll repeat this question as a separate topic in this forum.)

And I'll answer to this question in that other thread...
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Test Driven - testing with multiple teams