anchor.diff:  ----
   
   For additional information on using WebDriver, refer to the Selenium
  -https://code.google.com/p/selenium/wiki/GettingStarted[WebDriver documentation].
  +https://github.com/SeleniumHQ/selenium/wiki/Getting-Started[WebDriver documentation].
   
   [[spring-mvc-test-server-htmlunit-webdriver-advanced-builder]]
   ====== Advanced MockMvcHtmlUnitDriverBuilder
  
positive.code: ----
  
  Formerly, this pattern is known as the
  https://code.google.com/p/selenium/wiki/PageObjects[Page Object Pattern]. While we can
  certainly do this with HtmlUnit, WebDriver provides some tools that we will explore in the
  following sections to make this pattern much easier to implement.
  
  
negative.code: 
  <2> The next thing you will notice is that we have a member variable for each of the
  parts of the HTML page that we are interested in. These are of type `WebElement`.
  ``WebDriver``'s https://github.com/SeleniumHQ/selenium/wiki/PageFactory[PageFactory] allows
  us to remove a lot of code from the HtmlUnit version of `CreateMessagePage` by
  automatically resolving each `WebElement`. The
  https://seleniumhq.github.io/selenium/docs/api/java/org/openqa/selenium/support/PageFactory.html#initElements-org.openqa.selenium.WebDriver-java.lang.Class-[PageFactory#initElements(WebDriver,Class<T>)]
  method will automatically resolve each `WebElement` by using the field name and looking it
  up by the `id` or `name` of the element within the HTML page.
  
  <3> We can use the
  https://github.com/SeleniumHQ/selenium/wiki/PageFactory#making-the-example-work-using-annotations[@FindBy annotation]
  to override the default lookup behavior. Our example demonstrates how to use the `@FindBy`
  annotation to look up our submit button using a css selector, *input[type=submit]*.
  
  