A webdriver example.

The webdriver action of type WD () should interact with the webpage using commands from Test.WebDriver.Commands (which is re-exported from this module) and then use the expectations in this module. It is possible to split up the spec of a single page into multiple examples where later examples start with the web browser state from the end of the previous example. This is helpful to keep each individual example small and allows the entire spec to be described at the beginning with pending examples.

The way this works is that you combine examples into a session using session or sessionWith. A webdriver session is then threaded through all examples in a session so that a later example in the session can rely on the webbrowser state as set up by the previous example. The type system enforces that every webdriver example must be located within a call to session or sessionWith. Indeed, a WdExample produces a SpecWith (WdTestSession multi) which can only be converted to Spec using session or sessionWith. The reason for the WdPending constructor is so that a pending example can be specified with type SpecWith (WdTestSession multi) so it can compose with the other webdriver examples.

The type multi is used when testing multiple sessions at once (e.g. to test multiple interacting users), otherwise it is (). Values of this type are used to determine which browser session the example should be executed against. A new session is created every time a new value of type multi is seen. Note that the type system enforces that every example within the session has the same type multi.

Optional options that can be passed to runWDOptions.

A shorthand for constructing a WdExample from a webdriver action when you are only testing a single browser session at once. See the XKCD example at the top of the page.

A version of runWD that accepts some custom options

Create a webdriver example, specifying which of the multiple sessions the example should be executed against. I suggest you create an enumeration for multi, for example:

data TestUser = Gandolf | Bilbo | Legolas
    deriving (Show, Eq, Enum, Bounded)

runUser :: TestUser -> WD () -> WDExample TestUser
runUser = runWDWith

spec :: Spec
spec = session "tests some page" $ using [firefoxCaps] $ do
    it "does something with Gandolf" $ runUser Gandolf $ do
        openPage ...
    it "does something with Bilbo" $ runUser Bilbo $ do
        openPage ...
    it "goes back to the Gandolf session" $ runUser Gandolf $ do
        e <- findElem ....
        ...

In the above code, two sessions are created and the examples will go back and forth between the two sessions. Note that a session for Legolas will only be created the first time he shows up in a call to runUser, which might be never. To share information between the sessions (e.g. some data that Gandolf creates that Bilbo should expect), the best way I have found is to use IORefs created with runIO (wrapped in a utility module).

A version of runWDWith that accepts some custom options

A pending example.

A pending example with a message.

A version of example which lifts an IO () to a webdriver example (so it can be composed with other webdriver examples). In the case of multiple sessions, it doesn't really matter which session the expectation is executed against, so a default value is used. In the case of single sessions, the type is WdExample ().

Combine the examples nested inside this call into a webdriver session or multiple sessions. For each of the capabilities in the list, the examples are executed one at a time in depth-first order and so later examples can rely on the browser state created by earlier examples. These passes through the examples are independent for different capabilities. Note that when using parallel, the examples within a single pass still execute serially. Different passes through the examples will be executed in parallel. The sessions are managed as follows:

• In the simplest case when multi is (), before the first example is executed a new webdriver session with the given capabilities is created. The examples are then executed in depth-first order, and the session is then closed when either an exception occurs or the examples complete. (The session can be left open with inspectSession).
• More generally, as the examples are executed, each time a new value of type multi is seen, a new webdriver session with the capabilities is automatically created. Later examples will continue with the session matching their value of multi.

This function uses the default webdriver host (127.0.0.1), port (4444), and basepath (/wd/hub).

A variation of session which allows you to specify the webdriver configuration. Note that the capabilities in the WDConfig will be ignored, instead the capabilities will come from the list of Capabilities passed to sessionWith.

In addition, each capability is paired with a descriptive string which is passed to hspec to describe the example. By default, session uses the browser name as the description. sessionWith supports a more detailed description so that in the hspec output you can distinguish between capabilities that share the same browser but differ in the details, for example capabilities with and without javascript.

Abort the session without closing the session.

Normally, session will automatically close the session either when the tests complete without error or when any of the tests within the session throws an error. When developing the test suite, this can be annoying since closing the session causes the browser window to close. Therefore, while developing the test suite, you can insert a call to inspectSession. This will immedietly halt the session (all later tests will fail) but will not close the session so that the browser window stays open.

A synonym for constructing pairs that allows the word using to be used with session so that the session description reads like a sentance.

allBrowsers :: [Capabilities]
allBrowsers = [firefoxCaps, chromeCaps, ieCaps]

browsersExceptIE :: [Capabilities]
browsersExceptIE = [firefoxCaps, chromeCaps]

mobileBrowsers :: [Capabilities]
mobileBrowsers = [iphoneCaps, ipadCaps, androidCaps]

myspec :: Spec
myspec = do
  session "for the home page" $ using allBrowsers $ do
    it "loads the page" $ runWD $ do
        ...
    it "scrolls the carosel" $ runWD $ do
        ...
  session "for the users page" $ using browsersExceptIE $ do
    ...

Internal state for webdriver test sessions.

Default capabilities which can be used in the list passed to using. I suggest creating a top-level definition such as allBrowsers and browsersWithoutIE such as in the XKCD example at the top of the page, so that you do not specify the browsers in the individual spec.

Default capabilities which can be used in the list passed to using. I suggest creating a top-level definition such as allBrowsers and browsersWithoutIE such as in the XKCD example at the top of the page, so that you do not specify the browsers in the individual spec.

Default capabilities which can be used in the list passed to using. I suggest creating a top-level definition such as allBrowsers and browsersWithoutIE such as in the XKCD example at the top of the page, so that you do not specify the browsers in the individual spec.

Default capabilities which can be used in the list passed to using. I suggest creating a top-level definition such as allBrowsers and browsersWithoutIE such as in the XKCD example at the top of the page, so that you do not specify the browsers in the individual spec.

Default capabilities which can be used in the list passed to using. I suggest creating a top-level definition such as allBrowsers and browsersWithoutIE such as in the XKCD example at the top of the page, so that you do not specify the browsers in the individual spec.

Default capabilities which can be used in the list passed to using. I suggest creating a top-level definition such as allBrowsers and browsersWithoutIE such as in the XKCD example at the top of the page, so that you do not specify the browsers in the individual spec.

Default capabilities which can be used in the list passed to using. I suggest creating a top-level definition such as allBrowsers and browsersWithoutIE such as in the XKCD example at the top of the page, so that you do not specify the browsers in the individual spec.

shouldBe lifted into the WD monad.

Asserts that the given element matches the given tag.

Asserts that the given element has the given text.

Asserts that the given elemnt has the attribute given by (attr name, value).

Asserts that the action returns the expected result.

Asserts that the action throws an exception.

Run given spec and write a report to stdout. Exit with exitFailure if at least one spec item fails.

The describe function combines a list of specs into a larger spec.

context is an alias for describe.

The it function creates a spec item.

A spec item consists of:

• a textual description of a desired behavior
• an example for that behavior

describe "absolute" $ do
  it "returns a positive number when given a negative number" $
    absolute (-1) == 1

specify is an alias for it.

parallel marks all spec items of the given spec to be safe for parallel evaluation.

Run an IO action while constructing the spec tree.

SpecM is a monad to construct a spec tree, without executing any spec items. runIO allows you to run IO actions during this construction phase. The IO action is always run when the spec tree is constructed (e.g. even when --dry-run is specified). If you do not need the result of the IO action to construct the spec tree, beforeAll may be more suitable for your use case.

A state monad for WebDriver commands.

A structure describing the capabilities of a session. This record serves dual roles.

• It's used to specify the desired capabilities for a session before it's created. In this usage, fields that are set to Nothing indicate that we have no preference for that capability.
• When received from the server , it's used to describe the actual capabilities given to us by the WebDriver server. Here a value of Nothing indicates that the server doesn't support the capability. Thus, for Maybe Bool fields, both Nothing and Just False indicate a lack of support for the desired capability.