diff --git a/CHANGELOG.md b/CHANGELOG.md index 3e18efa..8b9432e 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -5,10 +5,16 @@ - do we need SeleneDriver anymore? (if we go the direction of SeleneBrowser) -## 1.0.0-alpha08 (to be released on 2021.05.??) +## 1.0.0-alpha09 (to be released on 2021.05.??) - deprecate the majority of Selene.* (except S, SS) when providing alternative API via Browser.* -## 1.0.0-alpha07 (to be released on 2021.05.13) +## 1.0.0-alpha08 (to be released on 2021.05.18) +- added waiting to SeleneElementJsExtensions: + - JsClick + - JsType + - JsSetValue + +## 1.0.0-alpha07 (released on 2021.05.13) - improved error messsages - now condition in Should method will be rendered like: `... .Should(Be.Visible)` over just `... .Visible` diff --git a/NSelene/NSelene.csproj b/NSelene/NSelene.csproj index 2c72080..741e123 100644 --- a/NSelene/NSelene.csproj +++ b/NSelene/NSelene.csproj @@ -3,7 +3,7 @@ netstandard2.0 NSelene - 1.0.0-alpha07 + 1.0.0-alpha08 yashaka MIT Copyright (c) 2015-2021 Iakiv Kramarenko @@ -23,33 +23,10 @@ -- improved error messsages - - now condition in Should method will be rendered like: - `... .Should(Be.Visible)` over just `... .Visible` -- deprecated SeleneElement#config, use SeleneElement#Config instead - - yet be attentive... the fate of keeping SeleneElement#Config as public is also vague... -- added experimental feature: Configuration._HookWaitAction - - prefixed with underscore implies that this feature is kind of "publically available private property that might be changed/renamed/removed/etc in future;)", so use it on your own risk!!! - - by default equals to null, making internally call waiting algorithm for actions as it is, without additional customization - - specified to something like: - ``` - Configuration._HookWaitAction = (entityObject, describeComputation, wait) => { - Console.WriteLine($"STARTED WAITING FOR: {entityObject}.{describeComputation()}"); - try - { - wait(); - Console.WriteLine($"FINISHED WAITING FOR: {entityObject}.{describeComputation()}"); - } - catch (Exception error) - { - Console.WriteLine($"FAILED WAITING FOR: {entityObject}.{describeComputation()}"); - throw error; - } - }; - ``` - - should provide some additinal logging for all Selene actions, called on entities (like SeleneElement, SeleneCollection) - - under actions we mean "void commands" not "queries returning result". - - void command like element.Should(condition) will return the element itself instead of void ;) +- added waiting to SeleneElementJsExtensions: + - JsClick + - JsType + - JsSetValue true diff --git a/README.md b/README.md index adaa828..2fee8c3 100644 --- a/README.md +++ b/README.md @@ -34,7 +34,7 @@ For docs see tests in the [NSeleneTests](https://github.com/yashaka/NSelene/blob ## Versions -* Upcomig version to use is just released [1.0.0-alpha07](https://www.nuget.org/packages/NSelene/1.0.0-alpha07) +* Upcomig version to use is just released [1.0.0-alpha08](https://www.nuget.org/packages/NSelene/1.0.0-alpha08) * targets netstandard2.0 * net45 support may be added later * it differs from [0.0.0.7](https://www.nuget.org/packages/NSelene/0.0.0.7) in the following: