When I think about Continuous Integration, one of the first things that comes to my mind is testing. It's amazing how much more confident you can be about changes to your codebase when you have a good suite of tests, and you know they run before every merge.
In this video we'll cover setting up our section custom step in Github Actions, which will simply run Jest. I'll walkthrough setting up a quick test, why I like to use a separate CI specific script for my tests, the --ci flag, and a little bit about multiple jobs and why we aren't using them yet.
~~~~~~
RESOURCES:
Playlist:
• Continuous Integration...
Repository:
github.com/Jimmydalecleveland...
Jest --ci documentation:
jestjs.io/docs/cli#--ci
~~~~~~
00:00 - Introduction
00:26 - Installing Jest and adding a test
06:33 - Github Action
08:09 - Jest --ci flag
08:42 - Standardizing CI commands
09:59 - Pushing up action and checking it
10:59 - Fixing Lint failures
13:11 - Final touches and success
14:56 - To job or not to job
18:18 - Wrap-up
~~~~~~
Follow Jimmy Cleveland's doings:
twitter: / jimmydcleveland
blog: blog.jimmydc.com/
#ci #javascript #testing
Негізгі бет CI #4 - Automating Tests with Jest
Пікірлер: 6