{"id":1123,"date":"2023-06-29T05:00:00","date_gmt":"2023-06-29T12:00:00","guid":{"rendered":"https:\/\/www.angulartraining.com\/daily-newsletter\/?p=1123"},"modified":"2023-06-27T11:44:30","modified_gmt":"2023-06-27T18:44:30","slug":"running-unit-tests-on-continuous-integration-servers","status":"publish","type":"post","link":"https:\/\/www.angulartraining.com\/daily-newsletter\/running-unit-tests-on-continuous-integration-servers\/","title":{"rendered":"Running unit tests on continuous integration servers"},"content":{"rendered":"\n

We talked about unit testing<\/a> a couple of times last week. One of the main benefits of unit tests is that they run quickly and provide immediate feedback. As a result, we get the best return on investment when running those unit tests on a continuous integration (CI) server after each commit.<\/p>\n\n\n\n

Two challenges come with running unit tests on a CI server:<\/p>\n\n\n\n

    \n
  1. The default test runner for Angular projects (Karma) opens a Chrome browser to run the tests, which is challenging on most CI servers (typically Unix based with no UI support).<\/li>\n\n\n\n
  2. The ng test<\/code> command doesn’t stop on its own. It keeps watching the source code for updates and then reruns the tests.<\/li>\n<\/ol>\n\n\n\n

    Fortunately for us, there is a single command that addresses both problems:<\/p>\n\n\n

    \n
    \"\"<\/figure>\n<\/div>\n\n\n

    <\/p>\n\n\n\n

    Running the command will result in a single test run (thanks to --watch false<\/code>) and will run in a UI-less way (thanks to --browsers ChromeHeadless<\/code>). That’s all your CI server needs to do.<\/p>\n\n\n\n

    If you’re using an older version of Angular, this old tutorial of mine<\/a> might help you configure Karma accordingly.<\/p>\n","protected":false},"excerpt":{"rendered":"

    We talked about unit testing a couple of times last week. One of the main benefits of unit tests is that they run quickly and provide immediate feedback. As a result, we get the best return on investment when running those unit tests on a continuous integration (CI) server after each commit. Two challenges come […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[19,17],"tags":[],"class_list":["post-1123","post","type-post","status-publish","format-standard","hentry","category-testing","category-tools"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t