Open ozten opened 11 years ago
+1!
this might involve either taking the improvements to wd
and offering them upstream, or figuring out a way to share them between projects.
If there are a considerable number of these improvements that are not interesting upstream, we could publish wd-wrapper as an official npm project which depends on wd. have a look at automation-tests/lib/wd-extensions.js
- that thing would be easy to roll into its own lib if needed.
On Oct 11, 2012, at 10:21 AM, Dan Callahan notifications@github.com wrote:
+1!
— Reply to this email directly or view it on GitHub.
Damn it.
The script in this Gist tests the two most common cases: https://gist.github.com/4338268
(Was having issues with the Node.js API; will port to that once necessary)
This is great, which codebase should we put it in? Let's get it out of a gist. Since it's known to fail sometimes, maybe put in ourcodebase and document how to run it during a smoke test?
We should take the kapow branch and write BigTent focused selenium tests.