- all callbacks use result object
- custom commands, page object/section commands have same behavior/interface
- client/api property consistency
- better separation of user-defined apis and internal properties (page objects etc)
- page/section objects have full api surface
- Page objects, commands classes, having proper instanceof-checkable instances (no weird F() constructor)
- Support command overrides rather than throwing an error
- no legacy stuff
- afterEach hook can receive the browser object only in its async form
- async behavior consistency/clarity
- shouldn't need to emit 'complete' in next tick
- command behavior with completion (what do I mean here?)
- --tag cli arg to support comma-separated list format
- Custom commands don't need to call a command to complete
- Global inconsistencies in parallel test execution
- setValue should clear then sends text
- browser.element(using, selector) vs. browser.expect.element(selector, using) (reversed params)
Last active
August 31, 2017 08:36
-
-
Save senocular/bec75198d3792b9c328116fad736f5e8 to your computer and use it in GitHub Desktop.
Nightwatch API Wishlist
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment