
- Overview
- Transcript
7.1 Conclusion
This video suggests numerous projects you can undertake to further your understanding of Angular test-driven development using the app you have built. If you want to practice some of the ideas that you learned in this course, try completing the Open Assignment!
From everyone here at Tuts+, I want to congratulate you on completing this course.
Keep on coding!
Related Links
1.Introduction3 lessons, 07:24
Free Lesson 1.1Introduction01:12
Free Lesson 1.2Test-Driven Development in Angular04:14
1.3Before You Start01:58
2.Scaffolding a Testable Angular App5 lessons, 46:23
2.1Introducing the Ironclad Address Book04:57
2.2App Setup11:37
2.3Serving Mocha Tests10:32
2.4Running Karma Tests11:33
2.5Implementing a Simple Back End With Express07:44
3.Testing Angular Applications5 lessons, 51:44
3.1Testing Services With Inject and Module12:45
3.2Verifying GET and POST Functionality With $httpBackend05:43
3.3Testing Angular Controllers12:27
3.4Testing Angular Filters10:19
3.5Testing Angular Directives10:30
4.Code Coverage With Istanbul3 lessons, 18:01
4.1What Is Istanbul?01:14
4.2Adding Istanbul to our Application09:40
4.3Generating and Serving a Code Coverage Report07:07
5.End-to-End Testing With Protractor4 lessons, 23:27
5.1Installing Protractor Dependencies03:55
5.2Configuring Selenium08:30
5.3Testing With Protractor05:06
5.4Automating Protractor05:56
6.Adding Finishing Touches4 lessons, 23:06
6.1Reviewing our App03:56
6.2Adding Contacts07:27
6.3Updating the Contact Display04:47
6.4Adding Styles06:56
7.Conclusion1 lesson, 04:05
7.1Conclusion04:05
7.1 Conclusion
Hi. I am Daniel for Touchplus. In this video we're going to review what we've learned and also discuss the open assignment that accompanies this course. So, what have we learned? Well, hopefully we've learned that tests are powerful. They leverage the processing power of computers so that we can test thousands of things every minute. This is what makes tests very cool. We learned all about the technologies Karma, Protractor, and Mocha and we combined those using gulps to make a variety of different angular tests. Finally, we've learned about the measurement of code coverage and we implemented Istanbul to test that. Now, you'll notice that, while the finished app was fully functional and fully styled, we did not write all the tests. In the original development of this app, I spent many, many hours devising all the possible tests to make it very strong. So naturally, I couldn't go over every single one, in this short core series. So for the open assignment, I challenge you to add validation to your app. You'll notice that we could add any contact whatsoever to the list. If the contact was already on the list, no problem. The contact would be duplicated. So what you need to do, is make sure that only valid contacts get added to the list. And, then to make sure that your validation works, you must write tests for your validation. On the branch master, this has already been completed. But I encourage you to give it your best shot before looking for any clues or hints from the master branch. Another very interesting but complex field, which we could not cover in this video, is testing our Node Express server backend. We wrote a very simple backend and we wrote no tests for it, but for a more complicated backend tests are absolutely key. There are more sophisticated tools you can use for back end testing, such as SuperTest, but the Mocha tool we already used would work fine. Therefore, it's your challenge to add tests from Mocha in Express. Keep in mind this isn't Angular TDD it's more like Mocha Express TDD so you're not strictly required to do this to fully understand this course. However I encourage you to do so because it's a very useful skill. Next, I encourage you to augment your Protractor functionality. Right now we're only testing in Chrome, but we could test at least in Chrome, Safari and PhantomJS. So augment your Protractor to test additional browsers, at least Safari. [SOUND] Finally be sure to visit Github and follow Angular and karma. And yes, here I am on Github on the Karma page on github.com/karma-runner/karma and I'm just going to go ahead and star this repository. I'm also going to watch it. I recommend that you star the repository, but careful about watching it because you're going to receive a ton of e-mails for such an active repo. You'll be informed of every possible change. However, starring it is harmless and lets the developers know you support and are interested in their application. Well it has been an absolutely outstanding course. We've learned so much and I would like to personally congratulate you for sticking with it and following the course to the very end. I'm Daniel Stern. Have a super day.