Comments on: Outsourcing and Test Driven Development http://blog.geekmanager.co.uk/2007/10/21/outsourcing-and-test-driven-development/#utm_source=feed&utm_medium=feed&utm_campaign=feed Mon, 05 Jul 2010 20:16:47 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Ajax Application Development Services http://blog.geekmanager.co.uk/2007/10/21/outsourcing-and-test-driven-development/comment-page-1/#comment-64443 Ajax Application Development Services Mon, 25 Jan 2010 08:38:59 +0000 http://blog.geekmanager.co.uk/2007/10/21/outsourcing-and-test-driven-development/#comment-64443 i have read your article Really Nice one.because Now a days not only big companies like Adobe, Microsoft are doing software and product development in India at their development center. But now many other small to medium scale companies have started software and product development and started entering into outsourcing software product development. It is considered that, increase in business will be around 100% in offshore outsourcing product development. i have read your article Really Nice one.because Now a days not only big companies like Adobe, Microsoft are doing software and product development in India at their development center. But now many other small to medium scale companies have started software and product development and started entering into outsourcing software product development. It is considered that, increase in business will be around 100% in offshore outsourcing product development.

]]> By: Meri http://blog.geekmanager.co.uk/2007/10/21/outsourcing-and-test-driven-development/comment-page-1/#comment-9110 Meri Mon, 22 Oct 2007 08:27:40 +0000 http://blog.geekmanager.co.uk/2007/10/21/outsourcing-and-test-driven-development/#comment-9110 Hi Ed. The approach I use tends to be blended -- unit tests written by developers/QA, as you advocate, but with a suite of acceptance tests run regularly by business specialists. Even if they are running the tests manually, the time investment is worth it to get quick feedback on whether the enhancements being built are what is needed. Obviously this approach is more usable when enhancing existing software, but I think functionality demos can be used when initially prototyping software to get the same sort of customer acceptance feedback. Hi Ed. The approach I use tends to be blended — unit tests written by developers/QA, as you advocate, but with a suite of acceptance tests run regularly by business specialists. Even if they are running the tests manually, the time investment is worth it to get quick feedback on whether the enhancements being built are what is needed.

Obviously this approach is more usable when enhancing existing software, but I think functionality demos can be used when initially prototyping software to get the same sort of customer acceptance feedback.

]]> By: Ed Gibbs http://blog.geekmanager.co.uk/2007/10/21/outsourcing-and-test-driven-development/comment-page-1/#comment-9102 Ed Gibbs Mon, 22 Oct 2007 04:01:36 +0000 http://blog.geekmanager.co.uk/2007/10/21/outsourcing-and-test-driven-development/#comment-9102 I think the focus on TDD is great. One note of caution though on talking about the customer creating the test suite. Unit tests are almost always purely a developer level practice, possibly with some enlightened QA staff. Customer level acceptence tests are another matter entirely. Higher level functionality expressed as tests are typically concendered acceptence tests. You can do Acceptence Test Driven Development or Story Driven Development using tools like FIT/Fitnesse, but its really a different animal than tightly focused developer unit tests written as the code is being worked out. Done right TDD is often much more about evolutionary design rather than testing. You might want to look into RSpec or JBehave for aspects of that. I think the focus on TDD is great. One note of caution though on talking about the customer creating the test suite. Unit tests are almost always purely a developer level practice, possibly with some enlightened QA staff. Customer level acceptence tests are another matter entirely.

Higher level functionality expressed as tests are typically concendered acceptence tests. You can do Acceptence Test Driven Development or Story Driven Development using tools like FIT/Fitnesse, but its really a different animal than tightly focused developer unit tests written as the code is being worked out.

Done right TDD is often much more about evolutionary design rather than testing. You might want to look into RSpec or JBehave for aspects of that.

]]>