With Selenium 2, which is based on WebDriver, even running the tests locally (using PropertyWebDriverProvider) results in the creation of a RemoteWebDriver instance (similar to Selenium RC on a local or remote computer), just as with SauceWebDriverProvider and RemoteWebDriverProvider.
So, if you are running locally, no Sauce, using Selenium 2 and PropertyWebDriverProvider, you have no way of passing any desired capabilities to control the logging, as you would in the examples you point out below, which allow you to do so via the constructor, etc. -----Original Message----- From: Mauro Talevi [mailto:[email protected]] Sent: Wednesday, December 14, 2011 5:31 AM To: [email protected] Subject: Re: [jbehave-user] Log Level with PropertyWebDriverProvider() David, SauceWebDriverProvider as well as RemoteWebDriverProvider allow the specification of the DesiredCapabilities, so you can configure to use them as you'd want. Don't understand the issue. Is it that you can't configure the logging via the DC? Have a look at the EtsyDotComStories in the jbehave-tutorial for examples of how to configure custom WebDriverProviders. If you can't do it by current means, we can surely provide a hook. Cheers On 13/12/2011 15:15, Alves, David wrote: > Mauro, > > I understand this. Selenium however does. In particular, RemoteWebDriver. > For whatever reason, in the current version, the log level is set extremely > low and it spews a ton of very useful info if you have a problem, but not > what you want with each run. > > SauceWebDriverProvier, SeleniumWebDriverProvider, and > PropertyWebDriverProvider provider all eventually invoke a RemoteWebDriver. > > The first two allow you to pass DesiredCapabilities as part of the > constructor of the class. PropertyWebDriverProvider however does not provide > any such ability in the constructor, nor can I find any way to get a hold of > the RemoteWebDriver, which has a method setLogLevel that could be used. > > I was just wondering if there was a mechanism in the framework to do so. If > not, does it make sense to add this capability, or expose access to the > RemoteWebDriver? > > There is a workaround, you can simply do the following for those who use > jbehave-web-selenium that may encounter this problem (it took me forever to > find this). > > In my constructor for my embedder, I make the following call: > > import java.util.logging.Level; > import java.util.logging.Logger; > > Logger logger = Logger.getLogger (""); > logger.setLevel (Level.OFF); > > David > -----Original Message----- > From: Mauro Talevi [mailto:[email protected]] > Sent: Monday, December 12, 2011 6:58 PM > To: [email protected] > Subject: Re: [jbehave-user] Log Level with PropertyWebDriverProvider() > > Hi David, > > JBehave does not use logging frameworks, so you cannot configure the > logging via JBehave. > > Cheers > > On Mon Dec 12 21:35:56 2011, Alves, David wrote: >> Could someone save me a lot of time and tell me how to set the Log >> Level (Log4j style level INFO, SEVERE, etc.) when using the >> PropertyWebDriverProvider()? >> >> I upgraded to JBehave-core 3.5.4 and JBehave-Web 3.4.3, and I am now >> getting a slew of Log4j INFO in my Console output. >> >> I can see how to set this using DesiredCapabilities for >> SauceWebDriverProvider and RemoteWebDriverProvider, but not for >> PropertyWebDriverProver. >> >> I've looked everywhere. I'm sure it some property or preference, but >> cannot find it. >> >> Please help. >> >> Thanks. >> >> David >> >> >> >> The information contained in this email message and its attachments is >> intended only for the private and confidential use of the recipient(s) >> named above, unless the sender expressly agrees otherwise. >> Transmission of email over the Internet is not a secure communications >> medium. If you are requesting or have requested the transmittal of >> personal data, as defined in applicable privacy laws by means of email >> or in an attachment to email, you must select a more secure alternate >> means of transmittal that supports your obligations to protect such >> personal data. If the reader of this message is not the intended >> recipient and/or you have received this email in error, you must take >> no action based on the information in this email and you are hereby >> notified that any dissemination, misuse or copying or disclosure of >> this communication is strictly prohibited. If you have received this >> communication in error, please notify us immediately by email and >> delete the original message. > > > --------------------------------------------------------------------- > To unsubscribe from this list, please visit: > > http://xircles.codehaus.org/manage_email > > > > The information contained in this email message and its attachments is > intended only for the private and confidential use of the recipient(s) named > above, unless the sender expressly agrees otherwise. Transmission of email > over the Internet is not a secure communications medium. If you are > requesting or have requested the transmittal of personal data, as defined in > applicable privacy laws by means of email or in an attachment to email, you > must select a more secure alternate means of transmittal that supports your > obligations to protect such personal data. If the reader of this message is > not the intended recipient and/or you have received this email in error, you > must take no action based on the information in this email and you are hereby > notified that any dissemination, misuse or copying or disclosure of this > communication is strictly prohibited. If you have received this communication > in error, please notify us immediately by email and delete the original > message. --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
