braindump of Eric Anderson's open spaces discussion on "Front-End JS Testing: What works?

Eric feels he has two left thumbs in working in JS testing. Kassandra Perch suggests that Mocha is for DOM-free unit testing. Correction, she uses it for DOM-free unit testing. Casper and Phantom are headless browser stuff. Another gentleman: a lot of tools wrap around QUnit and Selenium. 3 areas: determine your framework, mock testings, define how you want to test. FunkUnit (spelling?) is DOM testing of some manner. Test swarm is another tool. Chimera is another tool. Eric mentions that he has seen others get jaded. Kassandra suggests that Angular supports Jasmine and that it is likely good to stick with Jasmine with Angular. Jadedness comes from picking the wrong tools to test with. Cross-browser testing is its own beast. Browserlinq is good for this per Kassandra... you send it a URL (public-facing or on a LAN where you have a staging grounds) and JavaScript testing. Kevin Miller suggests that Microsoft is currently offering 3 months of Browserlinq service for free. Other gentlemen: What about mobile and tablet testing? Emulators such. Person #5: suggests using Yeti. Eric thinks slow servers and respond times leads front end testing to ultimately become unstable. Eric speaks of TestSwarm at Dell. What is Adobe Edge (formerly Adobe Shadow)? Winery is an open source tool that is the free version on the Adobe tool. Weinre is how winery is spelled. You can snapshot the DOM. Phantom allows you to snapshot the DOM per person #6. The 100% coverage rule does not apply to the front end per Kassandra. Don't test the color of a button. She feels this makes it harder to see front-end testing to persons doing back-end unit testing. Kassandra leans more towards testing in a unit testing way, not so much touching the DOM. This makes me think Mocha is very different from Jasmine which is DOM heavy. Sinon is yet another tool. Kevin thinks Mocha is much less clunky than Jasmine. You can also do QUnit style testing in Mocha. Kassandra says you can have it both ways with Mocha both Jasminesque BDD and traditional unit tests. Growl is a notification tool for Grunt to alert you when tests fail. Sublime is another tool. Needle too, a python framework for Selenium that takes screenshots. Ryan something, the first nameless guy here, is bringing up code coverage tools and tools for how long it takes code to load. Kassandra JS said that Phantom has some stuff for these concerns. Another individual mentions Dynatrace AJAX Edition. Timeouts and warnings are available in Mocha per Kassandra. Guy to my right mentions JS TestDriver. Kassandra found it hard to use. Guy at my right mentions there is a code coverage tool in JS TestDriver. Require.js was mentioned by Kevin Miller.

Addendum 11/19/2014: I thought I'd include this Vine which I made the day of this blog posting in the blog posting.