Due to the goal of this library that mirrors Protractor which in turn justifiable claims that "[y]ou no longer need to add waits and sleeps to your test" and "you don’t have to worry about waiting for your test and webpage to sync." everything it accomplishes in this regard feels like MAGIC. This complicates the situation when things don't go as expected. It also downplays the importance of the end users understanding what is going on, what this library can and cannot accomplish.
This ticket lists some of the items I want to change to help remove the magic.
- If the library has to poll (more than once, twice, N times) than an info log statement is recorded.
- If the library timeouts log that piece of information at info level.
- [.. something else that I really can't remember at this time ..]
Due to the goal of this library that mirrors Protractor which in turn justifiable claims that "[y]ou no longer need to add waits and sleeps to your test" and "you don’t have to worry about waiting for your test and webpage to sync." everything it accomplishes in this regard feels like MAGIC. This complicates the situation when things don't go as expected. It also downplays the importance of the end users understanding what is going on, what this library can and cannot accomplish.
This ticket lists some of the items I want to change to help remove the magic.