Functional Testing with Zombie.js

The pros and cons of functional testing with Zombie.js

Transcript

1. TESTING WITH ZOMBIE… Han Chang
2. Background Test Framework Browser Emulator / Driver Web Application
3. HtmlUnit htmlunit.sourceforge.net
4. HTMLUnit uses Rhino
5. Rhino is not good at the real world   http://stackoverflow.com/questions/1536896/apache- htmlunit-problem-in-handling-javascript   http://www.coderanch.com/t/95804/Testing/Better- JavaScript-support-than-HtmlUnit   http://stackoverflow.com/questions/2848398/htmlunit- doesnt-load-externally-referenced-javascript   http://stackoverflow.com/questions/2188905/java- htmlunit-crashes-upon-javascript-error   I could go on…
6. But wait – Zombie.js!   https://github.com/assaf/zombie   Full stack   Headless   V8   Node.js
7. This sounds awesome, right?!
8. Nope – can’t handle real life…
9. Why is this happening?   Browser to Javascript engine interaction   Chrome uses the HTML parser within Webkit   Zombie uses JSdom, which does not correctly handle a lot of edge cases; for example, a script containing “&” would be truncated and passed onto Zombie for evaluation as a partial script ending in “&”: https://github.com/assaf/zombie/issues/88   Result: Zombie.js can’t even handle google.com https://github.com/assaf/zombie/issues/121
10. Remedies
11. Make Selenium Run Faster   Run headless via Xvfb   Replace static waits with spin http://saucelabs.com/blog/index.php/2011/04/ how-to-lose-races-and-win-at-selenium/
12. SpinAssertions
13. Make Selenium Run Selectively   Only run Selenium tests for mission critical functions   Use server side functional tests for other features
14. Conclusion Full Stack / Acceptance   Selenium Functional / BDD   Cucumber
15. Bonus: Behat, BDD for PHP