webdriver-0.11.0.0: a Haskell client for the Selenium WebDriver protocol
Safe HaskellSafe-Inferred
LanguageHaskell2010

Test.WebDriver.Exceptions.Internal

Synopsis

Documentation

data FailedCommand Source #

This exception encapsulates a broad variety of exceptions that can occur when a command fails.

failedCommand :: (HasCallStack, WDSessionStateIO s) => FailedCommandType -> String -> s a Source #

Convenience function to throw a FailedCommand locally with no server-side info present.

mkFailedCommandInfo :: WDSessionState s => String -> CallStack -> s FailedCommandInfo Source #

Constructs a FailedCommandInfo from only an error message.

data FailedCommandType Source #

The type of failed command exception that occured.

Instances

Instances details
Bounded FailedCommandType Source # 
Instance details

Defined in Test.WebDriver.Exceptions.Internal

Enum FailedCommandType Source # 
Instance details

Defined in Test.WebDriver.Exceptions.Internal

Show FailedCommandType Source # 
Instance details

Defined in Test.WebDriver.Exceptions.Internal

Eq FailedCommandType Source # 
Instance details

Defined in Test.WebDriver.Exceptions.Internal

Ord FailedCommandType Source # 
Instance details

Defined in Test.WebDriver.Exceptions.Internal

data FailedCommandInfo Source #

Detailed information about the failed command provided by the server.

Constructors

FailedCommandInfo 

Fields

Instances

Instances details
FromJSON FailedCommandInfo Source # 
Instance details

Defined in Test.WebDriver.Exceptions.Internal

Show FailedCommandInfo Source #

Provides a readable printout of the error information, useful for logging.

Instance details

Defined in Test.WebDriver.Exceptions.Internal

data StackFrame Source #

An individual stack frame from the stack trace provided by the server during a FailedCommand.

externalCallStack :: HasCallStack => CallStack Source #

Use GHC's CallStack capabilities to return a callstack to help debug a FailedCommand. Drops all stack frames inside Test.WebDriver modules, so the first frame on the stack should be where the user called into Test.WebDriver