Skip to content
This repository has been archived by the owner on Jun 27, 2019. It is now read-only.

Typo in: selenium driver fixture; load firefox from profile #124

Open
wvanmourik opened this issue May 7, 2014 · 5 comments
Open

Typo in: selenium driver fixture; load firefox from profile #124

wvanmourik opened this issue May 7, 2014 · 5 comments

Comments

@wvanmourik
Copy link

At the moment, the code is:
public void loadFirefoxProfileFromDirectory(String directory) {
defaultWebDriverSupplier.setCustomProfilePreferencesFile(new File(directory));
}

It should be:
public void loadFirefoxProfileFromDirectory(String directory) {
defaultWebDriverSupplier.setProfileDirectory(new File(directory));
}

I am guessing this typo is an copy/paste error from function:
public void loadCustomBrowserPreferencesFromFile(String filename) {
defaultWebDriverSupplier.setCustomProfilePreferencesFile(new File(filename));
}

@jguglielmi
Copy link

Similar to #106 ?

@raboof
Copy link
Contributor

raboof commented May 7, 2014

That indeed looks like a clear mistake. Should be fixed, but as I don't use this functionality, could you test whether this indeed now works?

@wvanmourik
Copy link
Author

Hi Jaison,

Almost, but not really. It seems you want a different functionality, while
I just wanted the existing functionality to work.
The issue is basically solved seeing the comment from raboof.

The file not found errors you got before, were because of this bug. I had
those too and that is how I found this typo.
Likely you can use the now fixed code and use multiple Firefox profiles by
passing a directory.

Example:
|load firefox profile from directory|
FitnesseRoot\files\BrowserProfiles\Firefox\myprofilename|

@jguglielmi
Copy link

Gotcha.

@jguglielmi
Copy link

I was just using the setProfileDirectory method directly with the String implementation when I declared my default web driver supplier as a variable. Where as you described it was then passed into the File instance of the method which called setProfileDirectory. Thanks for @mourikwa! This should close #106 as well. I'll go ahead and tidy up...

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants