Here’s the video from last week’s Effective .NET Test Driven Development FitNesse workshop. The workshop focused on introducing agile acceptance testing and working with FitNesse, with best practices and ideas how to use fixtures efficiently. The recording is about two hours long.
See also:
Effective .NET Test Driven Development with FitNesse — Workshop video
– April 2, 2008Posted in: fitnesse, presentations
|
|
Ho Gojko
Let me thank you again for this cool workshop, I have attended it and I really enjoyed it. Trying to move things forward, I got my team onboard and now I am trying to set up the environment. We use TFS. Can you point me in the right direction please? What is the best practice? Set up a fitnesse server ? or set up fitnesse on each developer’s machine? Should the fitnesse checkouts be all exclusive locks? Would you even consider adding fitnesse in the build?
Cheers,
Dan
Hi Dan,
I don’t use TFS myself, so this information might not be 100% complete, but hopefully it will point you into the right direction. I would definitely suggest putting fitnesse (files and tests) into the same version control system where your project files are, to keep them in sync. Each developer should have that checked out and can run fitnesse on a developer machine. This avoids version problems, and allows you to work in parallel.
You will need a central fitnesse server if you want to provide a read-only copy to clients/business analysts/whoever does not have the source code checked out. You will also need it if you want to include fitnesse tests into the continuous build. In that case, I suggest setting FitNesse up as a windows service using srvany and re-starting the service every time new code is checked out. Then you can run the fitnesse tests on the end of your build using TestServer.exe.
The only problem with TFS compared to SVN is that TFS is typically not set up in the edit-and-merge mode. People often use it so that it requires exclusive checkouts, and fitnesse will create and modify files without checking them out. So using FitNesse with TFS requires more discipline than with SVN: you will either have to check-out the relevant folders yourself before FitNesse changes them, or remember to synchronize the fitnesse folders every time after changing the tests. If you run TFS in edit-and-merge mode, this problem might not be relevant for you (again, I’m not using TFS, so I do not know the details).
Thanks Gojko. I’ll try to get it setup in source control for now and I will worry about the read only version for customers later. I will let you know if I find anything interesting. So far, I found this which is pretty cool: http://www.codeplex.com/testingbuildtasks