Surely it's time to give away the home-grown versioning. How about a few magic parameters we can set to make .FitNesse use SourceSafe?, CvS?, and/or SubVersion??
Adding a big "yes please" for this. Acceptance tests and documentation (however informal) should be under source control, for a start - so why use two different source control methods? Mike Roberts has a blog entry about a somewhat hacky way of doing this: http://www.mikebroberts.com/blog/archive/Tech/Tools/WikisandSourceControl(withFitnesse,SubversionandCruiseControl.NET).html but a properly integrated version (which allowed showing changes via repository APIs etc) would be much better. I (Jon Skeet, if anyone cares) will take a look at the .FitNesse code to see how feasible it would be to "just do it".
Okay, I've now done that, and got a somewhat hacky version which works. See my blog entry at http://msmvps.com/blogs/jon.skeet/archive/2006/02/14/fitnessesvn.aspx
[.FrontPage] [.RecentChanges]
Adding a big "yes please" for this. Acceptance tests and documentation (however informal) should be under source control, for a start - so why use two different source control methods? Mike Roberts has a blog entry about a somewhat hacky way of doing this: http://www.mikebroberts.com/blog/archive/Tech/Tools/WikisandSourceControl(withFitnesse,SubversionandCruiseControl.NET).html but a properly integrated version (which allowed showing changes via repository APIs etc) would be much better. I (Jon Skeet, if anyone cares) will take a look at the .FitNesse code to see how feasible it would be to "just do it".
Okay, I've now done that, and got a somewhat hacky version which works. See my blog entry at http://msmvps.com/blogs/jon.skeet/archive/2006/02/14/fitnessesvn.aspx
[.FrontPage] [.RecentChanges]