By default, Selenium starts the browser with a fresh profile every time,
which means that it has no plugins installed. On quitting, it deletes that
profile again, to make sure that it won't slowly consume your disk.
When you start the firefox driver instance, you can ask it to load profile
details, including plugins. You can either create a new profile that only
has this plugin added (to keep things simpler and avoid other plugin
issues), or you can actually use your own default profile.
http://steveliles.github.io/testing_gwt_apps_in_dev_mode_with_webdriver.html
documents using your own profile, but this requires already having a
firefox profile set up locally with dev mode, which may not be ideal for
using other test machines to verify your app.
https://groups.google.com/d/topic/webdriver/xPDudSnAxwo/discussion
documents doing this the other way around, using the default of a fresh
profile (no history, no cache, no plugins, etc), and adding the gwt dev
mode plugin.
On Wednesday, November 6, 2013 2:37:17 PM UTC-6, Jeff Levene wrote:
Using GWT 2.4.0, Eclipse Kepler, Firefox 25.0, JDK 1.7.0_40, TestNG 6.8.5
When I run my test suite against the GWT app running on a Tomcat server,
all is well.
When I try to run it against a local copy running in Eclipse, instead of
bringing up my application, Firefox gives me:
Development Mode requires the GWT Developer Plugin
with a badge to click on to download the plugin. It does this no matter
how many times I have downloaded and installed the plugin and re-started
Firefox.
Ideas?
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
