On Fri, Nov 18, 2016 at 11:16 AM, Niklas Laxström <niklas.laxstrom@gmail.com
wrote:
- Testing framework: We mostly use qUnit, Cucumber, Selenium. Of these
only Cucumber appears in the top 6 and it has very low satisfaction (people who have used do not like it).
Direct link, for context:
http://stateofjs.com/2016/testing/
I would like to clarify. As far as I know, we use qunit for unit testing frontend javascript code. We use cucumber for end-to-end/acceptance tests, but only in combination with ruby, not javascript.
qunit and selenium are testing frameworks (generally speaking, a tool that has setup, teardown, reporting...) and selenium is a browser driver, something completely different. They are testing tools, and generally used together, but not the same thing.
Some good news, we are experimenting with nodejs+mocha+selenium:
https://www.mediawiki.org/wiki/Selenium/Node.js
Watch that page, I am working on it, more good stuff is coming soon.
For me one pain point is automated testing of JavaScript code. It
seems that testing frameworks, development practices and the way code is written could all be improved to make automated testing easier. Would there be interest in sharing comments how you do this and does what you do work well for you?
Are you interested in unit or end-to-end/acceptance testing? Both? Something else?
Željko