Re: GWT and automated testing tools

[gong min]

Selenium is suggested in a book "Essential GWT Building for web with Google Web Toolkit 2".

I never touched. Can anyone give some samples if it is a good solution for GWT auto test? Thanks.

2012/8/9 Ocean_Living <winter...@gmail.com>

I'm having some performance issues using Rational Functional Tester as an automated testing tool when testing a web app built on GWT.

Can anyone recommend an automated tool that works and plays well with GWT?

Thanks!

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/g3DtPqxfvJwJ.
To post to this group, send email to google-we...@googlegroups.com.
To unsubscribe from this group, send email to google-web-tool...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

--
Gong Min

gongm...@gmail.com

[Sachin Shekhar R]

We have hundreds of Forms which are tested using internal library based on Selenium Automation. It works really well across browsers and with both GXT and GWT.  The key thing is to avoid using Record feature which generates flaky test and instead rely on ID/Xpath based Java api to wrap test cases.

On Friday, 10 August 2012 06:33:38 UTC+5:30, 退5的工科苹岷 wrote:

Selenium is suggested in a book "Essential GWT Building for web with Google Web Toolkit 2".

I never touched. Can anyone give some samples if it is a good solution for GWT auto test? Thanks.

2012/8/9 Ocean_Living <winter...@gmail.com>

I'm having some performance issues using Rational Functional Tester as an automated testing tool when testing a web app built on GWT.

Can anyone recommend an automated tool that works and plays well with GWT?

Thanks!

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/g3DtPqxfvJwJ.
To post to this group, send email to google-we...@googlegroups.com.

To unsubscribe from this group, send email to google-web-toolkit+unsub...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.

--
Gong Min

gongm...@gmail.com

[Ryan Shillington]

We've been using Selenium for 6 months now, and quite happily.  Occasionally the browser will do something stupid like ask to install an update and ruin the test, but that happens pretty rarely.  It works pretty well across IE, Chrome & Firefox.  

Through the grapevine, I heard that Selenium is used by Google internally, which is why we chose it initially.  They use it to test Gmail, Google.com, Chrome, etc.

Sachin is correct about setting IDs to make tests work better.  If you are not able to modify the code to add IDs, then there's no test strategy that I know of that will work well.

Ryan

[Joseph Lust]

To echo Ryan's point, we have been using Selenium/Cucumber on our 1000+ widget project for a year now to great effect.

Just make sure you add a 'debugId' attribute to elements of interest as we found XPath's or CSS based selectors to be very brittle and often broken by minor UI tweaks. Just place the 'debugId' attribute in the UiBinder element, or set it with element.setAttribute('debugId','CUSTOM_ID');

P.S. JBehave looks very tempting as Cucumber depends heavily on Ruby.

Sincerely,

Joseph