tag:blogger.com,1999:blog-6678855.post111690930740421882..comments2023-10-04T23:45:44.880-07:00Comments on A New Beginning: Joy and Pain with FitnesseShanehttp://www.blogger.com/profile/18237393455554069484noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-6678855.post-19872049542659201602011-12-21T20:18:08.805-08:002011-12-21T20:18:08.805-08:00Great data, I´m starting to implemented, let´s see...Great data, I´m starting to implemented, let´s see <br />ThanksAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-6678855.post-1118011456565452132005-06-05T15:44:00.000-07:002005-06-05T15:44:00.000-07:00shane: great post. good to read about your experi...shane: great post. good to read about your experiences with Fitnesse. while i haven't used Fitnesse, i've used Fit on a couple of projects. as you point out, i think that one of the most overlooked aspects of these tools is the cost of setting up the environment to run the tests and the maintenance overhead for the fixtures. that's not to say i wouldn't use it again -- the alternatives don't come close. also, i hadn't come across the Fixture Tutorials, which are a nice touch.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-6678855.post-1117206120168477622005-05-27T08:02:00.000-07:002005-05-27T08:02:00.000-07:00Great post! Thanks. Selenium looks great for me n...Great post! Thanks. Selenium looks great for me ny the way.Michael Dubakovhttps://www.blogger.com/profile/07679773973314266590noreply@blogger.comtag:blogger.com,1999:blog-6678855.post-1117203242473442772005-05-27T07:14:00.000-07:002005-05-27T07:14:00.000-07:00I have experienced some common feelings about FitN...I have experienced some common feelings about FitNesse - in particular the fact that the "shared web" nature of it leaves me a little cold (I don't really need simultaneously running tests, as the best use of the tests for me is from the continuous integration system). The best aspect, for me, was the visual appearance of the results, which made it easy to "sell" to customers.<BR/><BR/>I helped roll Avignon (www.nolacom.com/avignon), but I will readily admit to its weaknesses (such as how nobody really wants to write the tests in XML). But it (with the BrowserBridge add-on) does do a couple of things well:<BR/>1) Because tests run as JUnit tests, they can easily be folded into an Ant build script. That makes it easy to stop a build/deployment process if tests fail.<BR/>2) The BrowserBridge proved to us to be quite useful at getting around some of the limitations of HTML testing. I have not yet had a chance to use some of the other tools you referred to, but they look promising as well. The biggest negative of the BrowserBridge is XPathAssert which, although powerful, is too complex for a customer to use. But we do have the ability to query a resulting page, as its current state is in Internet Explorer.<BR/><BR/>FIT without FitNesse does one thing really well: you can write your tests in a word processor (like MSWord), save them as HTML, and run them as tests without having to worry about pipets. But it lacks some of the aggregating structures for tests that FitNesse provides.xyzzyhttps://www.blogger.com/profile/13399718288137552129noreply@blogger.com