One of the most common misconceptions I’ve noticed is that application prototypes shouldn’t include automated tests - especially when dealing with frontend side of the application. Wrong.
“Code without tests is broken by design.” - Jacob Kaplan-Moss
Of course it’ll be faster in the short run and it will be “nice” to deliver more features in the short term, but ironically it very quickly changes to the complete opposite. Features take more time to deliver and contain more bugs. It’ll also be incredibly hard to switch from a prototype to production quality application.
I strongly feel that in order to go fast you sometimes need to slow down. Luckily EmberJS provides a fantastic test suite out of the box. Ember’s default testing framework is QUnit. My personal preference is to switch it out with Mocha. Chris Ball has well written guide on how to move your tests to mocha.
Found this article useful? Consider sharing (tweeting) it to your followers.