Comments on: Is Fitnesse ready for the Enterprise? It’s getting there. http://www.brokenbuild.com/blog/2006/07/24/is-fitnesse-ready-for-the-enterprise-its-getting-there/ Databases, code and all things agile. Thu, 09 Feb 2012 08:52:43 +0000 http://wordpress.org/?v=2.6.3 By: Naresh Jain http://www.brokenbuild.com/blog/2006/07/24/is-fitnesse-ready-for-the-enterprise-its-getting-there/#comment-2987 Naresh Jain Tue, 15 Aug 2006 11:58:23 +0000 http://www.brokenbuild.com/blog/2006/07/24/is-fitnesse-ready-for-the-enterprise-its-getting-there/#comment-2987 <p>Thanks. You seemed to have quite nicely summarized what I wanted to convey.</p> <p>You will soon see most of this part of standard fitnesse.</p> <p>Let me also answer your questions one by one:</p> <ol> <li><p>Do you use source control? We have a solution and this will soon be a part of fitnesse.</p></li> <li><p>Can you make a build in one step? I'm assuming you are talking of having an ant target. Yes I'm working on that and that would be part of fitnesse.</p></li> <li><p>Do you have a bug database? We have just moved fitnesse back to SourceForge and it does have a bug database.</p></li> <li><p>Do programmers have quiet working conditions? If you are testing a J2EE app, you can execute fit tests inside the container and most of the classpath issues will disappear. Have a look at http://sourceforge.net/projects/patang</p></li> </ol> Thanks. You seemed to have quite nicely summarized what I wanted to convey.

You will soon see most of this part of standard fitnesse.

Let me also answer your questions one by one:

  1. Do you use source control? We have a solution and this will soon be a part of fitnesse.

  2. Can you make a build in one step? I’m assuming you are talking of having an ant target. Yes I’m working on that and that would be part of fitnesse.

  3. Do you have a bug database? We have just moved fitnesse back to SourceForge and it does have a bug database.

  4. Do programmers have quiet working conditions? If you are testing a J2EE app, you can execute fit tests inside the container and most of the classpath issues will disappear. Have a look at http://sourceforge.net/projects/patang

]]>