Releases: csf-dev/CSF.Extensions.WebDriver
Release list
v1.0.4
This is (essentially) a single-issue bugfix release. It addresses #38 - which is to test the library with a later version of the Newtonsoft JSON library and - if it proves to be compatible - to relax the compatibility in the NuGet package dependencies.
v1.0.3
This is a single-issue release which undoes the work performed on strong-naming the assembly. It has become apparent, because Selenium WebDriver do not ship signed/strong-named assemblies via NuGet, that I am unable to strong-name this assembly without causing more problems than I solve.
v1.0.2
This is a single-issue release to deal with a failure in strong-naming the assembly. This was caused by mono/mono#8495
v1.0.1
This is a single-issue release to address #33 - strongly-naming the assembly.
v1.0.0
This is the first production release of WebDriverExtras. No changes were made since v0.5.0-beta.
v0.5.0-beta
This beta release fixes an oversight in v0.4.0-beta, whereby provisional versions were not marked as such when ToString was used. It also introduces a non-backwards-compatible change into the way in which scenario outcome is reported.
No formal changelog, because no issues were addressed from the issue list
v0.4.0-beta
This beta version is a single-issue release which adds a considerable extension to the manner in which browser versions are identified. When the factory is used to create a web driver, if the returned web driver instance fails to identify its version (it is null or empty) then the browser version which was originally requested is used to identify the browser instead.
Changelog
- #32 - Add a fall-back to the requested browser version as a "presumed" version
v0.3.3-beta
This beta release includes some bugfixes as well as missing features, which identify browser versions. It also includes a last-minute breaking change; notably the browser identification logic has been moved into a new namespace.
Changelog
v0.3.2-beta
v0.3.1-beta
This beta release contains only one change since the previous. This is a bugfix to Sauce Labs web drivers. The scenario name was not being properly transmitted amongst the capabilities.
In order to prove this was working, a new integration test was created for Sauce Labs/Travis.