Difference between revisions of "DPS909 & OSD600 Winter 2017 - Lab 8"
Theodor Dule (talk | contribs) (→Open Source Tooling and Automation Part 2: Unit Testing) |
(→Open Source Tooling and Automation Part 2: Unit Testing) |
||
(22 intermediate revisions by 13 users not shown) | |||
Line 53: | Line 53: | ||
| 7 | | 7 | ||
| Heetai Park | | Heetai Park | ||
− | | https://wordpress.com/ | + | | https://tonypark0403.wordpress.com/2017/03/27/open-source-tooling-and-automation-and-unit-testing/ |
| https://travis-ci.org/tonypark0403/OSD600 | | https://travis-ci.org/tonypark0403/OSD600 | ||
|- | |- | ||
Line 78: | Line 78: | ||
| 12 | | 12 | ||
| Zenan Zha | | Zenan Zha | ||
− | | | + | | http://zhazhazenan.blogspot.com/2017/04/lab-8-unit-test.html |
| https://travis-ci.org/ZenanZha/Learning_Lab | | https://travis-ci.org/ZenanZha/Learning_Lab | ||
|- | |- | ||
| 13 | | 13 | ||
|Tiago Araujo Aguiar | |Tiago Araujo Aguiar | ||
− | | | + | | http://dps909lab5.blogspot.ca/2017/04/open-source-tooling-and-automation-part.html |
− | | | + | | https://travis-ci.org/Taguiar/Seneca2017LearningLab |
|- | |- | ||
| 14 | | 14 | ||
|John James | |John James | ||
− | |https://wordpress.com/ | + | |https://johnjamesa70.wordpress.com/2017/03/29/osd-lab-8-part-2-to-lab-7/ |
|https://travis-ci.org/JohnEJames/OSD600_Lab7 | |https://travis-ci.org/JohnEJames/OSD600_Lab7 | ||
|- | |- | ||
| 15 | | 15 | ||
| Margaryta Chepiga | | Margaryta Chepiga | ||
− | | | + | | https://wordpress.com/post/mchepigablog.wordpress.com/434 |
− | | | + | | https://travis-ci.org/MargarytaChepiga/Seneca2017LearningLab |
|- | |- | ||
| 16 | | 16 | ||
Line 123: | Line 123: | ||
| 21 | | 21 | ||
| Peiying Yang | | Peiying Yang | ||
− | | | + | | https://pyang16.wordpress.com/2017/04/17/unit-testing/ |
− | | | + | | https://travis-ci.org/peiying16/LearningLab |
|- | |- | ||
| 22 | | 22 | ||
Line 137: | Line 137: | ||
|- | |- | ||
| 24 | | 24 | ||
− | | | + | | Maya Filipp |
− | | | + | | https://mordax.github.io/open_source/2017/04/15/open-source-tools-2.html |
− | | | + | | https://travis-ci.org/Mordax/Seneca2017LearningLab |
|- | |- | ||
| 25 | | 25 | ||
− | | | + | | Jerry Goguette |
− | | | + | | https://jgoguette.wordpress.com/2017/04/05/lab-8-automated-unit-testing-dps909/ |
− | | | + | | https://travis-ci.org/twigz20/Seneca2017LearningLab |
|- | |- | ||
| 26 | | 26 | ||
− | | | + | | Xiao Lei Huang |
− | | | + | | https://dps909blog.wordpress.com/ |
− | | | + | |https://travis-ci.org/davidhuang1550/Seneca2017LearningLab |
|- | |- | ||
| 27 | | 27 | ||
− | | | + | | Eugueni Antsyferov |
− | | | + | | https://cartryblog.wordpress.com/2017/04/09/osd600-lab-8/ |
− | | | + | | https://travis-ci.org/evantsyferov/OSD600-JavaScript-learning-lab/jobs/219924306 |
|- | |- | ||
| 28 | | 28 | ||
− | | | + | | Eduardo Sorozabal |
− | | | + | | https://edyedyschool.tumblr.com/post/159739643423/lab-8 |
− | | | + | | https://travis-ci.org/edyedy123/Lab7 |
|- | |- | ||
| 29 | | 29 | ||
− | | | + | | Shivam Gupta |
− | | | + | | https://sgupta44blog.wordpress.com/2017/04/19/lab-8-unit-test/ |
− | | | + | | https://travis-ci.org/sgupta7857/Seneca2017LearningLab |
|- | |- | ||
| 30 | | 30 | ||
− | | | + | | Rahul Gupta |
− | | | + | | https://rahul3guptablog.wordpress.com/2017/04/22/lab-8-unit-testing-2/ |
− | | | + | | https://travis-ci.org/rkgupta21/Seneca2017LearningLab |
|- | |- | ||
| 31 | | 31 |
Latest revision as of 08:45, 22 April 2017
Open Source Tooling and Automation Part 2: Unit Testing
In this lab you will extend your previous lab's tooling to include automated unit tests. Most large software projects include tests, and it's a good idea to know how to create, run, and debug them.
Please following the instructions in the README-part2.md doc at https://github.com/humphd/Seneca2017LearningLab.
When you are done, write a blog post about the experience, including:
- what you did
- what you learned
- things you found interesting or difficult.
- Was unit testing new to you? If so, what did you think? If not, how was it different with Jest/JS?
Make sure you include links to things you discuss in your blog.
After you've written your unit tests and got them passing on Travis, add your name, your blog post, and a link to a passing build on TravisCI running your tests: