FidelityWebDriver is a wrapper around the Selenium WebDriver, used to perform semantic driving of the Fidelity website.

MSBuild: Mono:

The demo app depends on Docker, so be sure you have Docker installed!

The demo app will use the specified credentials to log into the www.Fidelity.com website. Once logged in, it will print to the console some basic account info as well as the most recent transactions.

1. Start a Selenium docker container with the following command: docker run -d -p 4444:4444 selenium/standalone-chrome
2. Complie the solution and run Sonneville.FidelityWebDriver.Demo.exe with any of the below parameters:

  -u, --username=VALUE       the username to use when logging into Fidelity.
  -p, --password=VALUE       the password to use when logging into Fidelity.
  -s, --save                 indicates options should be persisted to demo.ini file.
  -h, --help                 shows this message and exits.

If the --save argument is given, settings are stored to demo.ini allowing future demo executions to omit the -u and -p parameters.

To use FidelityWebDriver, identify the IManager implementation which provides the functionality you'd like to consume. Instantiate the manager and required classes using your choice of IWebDriver implementation. An IOC library like Ninject is recommended. The Demo app module can be used to automatically bind all required classes.

FidelityWebDriver should always be functional if built from the master branch. Logging is achieved via Apache log4net. Log files for the demo app can be retrieved from the following location:

Please create an issue with any bugs!