Comments on: Fitnesse – Selenium integration struggles http://blog.xebia.com/2009/04/23/fitnesse-selenium-integration-struggles/ Software development done right! Wed, 08 Feb 2012 14:41:38 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Keith Sterling http://blog.xebia.com/2009/04/23/fitnesse-selenium-integration-struggles/#comment-91701 Keith Sterling Sat, 09 May 2009 07:15:03 +0000 http://blog.xebia.com/?p=1441#comment-91701 Guys, I have a full DSL implementation of Selenium in Fitnesse available for all to use at http://www.magneticreason.com/tools/fitnium/fitnium.html Keith Guys,

I have a full DSL implementation of Selenium in Fitnesse available for all to use at http://www.magneticreason.com/tools/fitnium/fitnium.html

Keith

]]> By: Powers Foss http://blog.xebia.com/2009/04/23/fitnesse-selenium-integration-struggles/#comment-91642 Powers Foss Wed, 29 Apr 2009 19:12:38 +0000 http://blog.xebia.com/?p=1441#comment-91642 I have also combined FitNesse with Selenium RC to form the basis of our automated functional test strategy. It works quite well and we have a team of nearly 30 QA testers authoring their tests in FitNesse utilizing Java fixture wrappers around the Selenium calls. We've found that with only a basic knowledge of XPath, the majority of the QA team can be productively automating tests without any programming experience. This keeps the so-called "test automation team" size down to a very small number (3) needed to support the functional tests, any custom fixtures, and execute the load & performance testing. I have also combined FitNesse with Selenium RC to form the basis of our automated functional test strategy. It works quite well and we have a team of nearly 30 QA testers authoring their tests in FitNesse utilizing Java fixture wrappers around the Selenium calls. We’ve found that with only a basic knowledge of XPath, the majority of the QA team can be productively automating tests without any programming experience. This keeps the so-called “test automation team” size down to a very small number (3) needed to support the functional tests, any custom fixtures, and execute the load & performance testing.

]]> By: Cirilo Wortel http://blog.xebia.com/2009/04/23/fitnesse-selenium-integration-struggles/#comment-91617 Cirilo Wortel Mon, 27 Apr 2009 07:11:23 +0000 http://blog.xebia.com/?p=1441#comment-91617 Hi Rob, In this team the developers were just doing unit testing. We have found that adding a functional tester to our teams is a recipe for success and if done correctly makes additional acceptance testing by the customer redundant. Also a tester can focus more on the business while the developers can fully focus on technical issues. This is for us a proven strategy, besides in my opinion testing and developing are just two different specialties. Hi Rob,
In this team the developers were just doing unit testing. We have found that adding a functional tester to our teams is a recipe for success and if done correctly makes additional acceptance testing by the customer redundant. Also a tester can focus more on the business while the developers can fully focus on technical issues. This is for us a proven strategy, besides in my opinion testing and developing are just two different specialties.

]]> By: Derek Neighbors http://blog.xebia.com/2009/04/23/fitnesse-selenium-integration-struggles/#comment-91586 Derek Neighbors Thu, 23 Apr 2009 18:21:42 +0000 http://blog.xebia.com/?p=1441#comment-91586 It is nice to see how other agile teams are approaching functional testing. Please keep sharing. It is nice to see how other agile teams are approaching functional testing. Please keep sharing.

]]> By: Rob Fletcher http://blog.xebia.com/2009/04/23/fitnesse-selenium-integration-struggles/#comment-91585 Rob Fletcher Thu, 23 Apr 2009 16:02:06 +0000 http://blog.xebia.com/?p=1441#comment-91585 What kind of 'agile' team has a separate tester writing functional tests? Why aren't the devs doing it? What kind of ‘agile’ team has a separate tester writing functional tests? Why aren’t the devs doing it?

]]> By: Seu Enium http://blog.xebia.com/2009/04/23/fitnesse-selenium-integration-struggles/#comment-91584 Seu Enium Thu, 23 Apr 2009 14:20:50 +0000 http://blog.xebia.com/?p=1441#comment-91584 You can use *chrome instead of *firefox. It resolves all the problems about changing domains during the navigation. About Fitnesse integration with Selenium, I've used it for a while but I haven't like it. Debugging in Fitnesse is awful and web tests generally crash and you have to debug. You can use *chrome instead of *firefox. It resolves all the problems about changing domains during the navigation.
About Fitnesse integration with Selenium, I’ve used it for a while but I haven’t like it. Debugging in Fitnesse is awful and web tests generally crash and you have to debug.

]]>