How to Unit Test Controllers In AngularJS Without Setting Your Hair On Fire | I care, I share, I'm Nathan LeClaire.
Developers almost universally agree that unit tests are a VERY GOOD THING when working on a project. They help you feel like your code is airtight, ensure reliability in production, and let you refactor with confidence when there is a need to do so. AngularJS code touts its high degree of testability, which is a reasonable claim. In much of the documentation end to end tests are provided with the
Try, Catch, Fail: AngularJS - Unit Testing - Controllers
Updated Feb 6, 2014 - I'm changing this around a lot. A lot as changed since I wrote the original article and a lot has stayed the same. Most notably how Angular 1.2 handles promises on the $scope when processing the view, and some changes around testing promises. Since I see this gets some traffic and I hate the idea that I'm showing people the wrong thing, I'm going to try to keep this updated
1
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く
