There is no overview for the class’s challenges. Review the overviews from previous challenges, if needed.
Watch the video for this class from the demo playlist.
There is no demonstration for the challenges for this class. Review the demos from previous challenges, if needed.
javascript
folder within your data-structures-and-algorithms
repository.chaining
git checkout -b chaining
npm run get-challenge 12
javascript
folder, run npm test 12
to execute the tests in this file for this challenge.
npx jest --version
in your terminal. Filename typos can make things break!challenges-12.test.js
file each of which has an associated test at the bottom of the file.
describe
to xdescribe
on any test will cause the test runner to skip that test. This may help you to keep focused on one test at a time.git add
and a git commit
to mark your work on that challenge.Note, you can also run
npm test
(without a challenge number) to run all of the tests for every code challenge file assignment during the course all at once. This can get “noisy”, but it’s an opportunity to get a view of your overall progress
When you have completed your code challenges (tests are passing) and/or are at the alotted time:
git push
of your code to your repository.git pull
as you merge your code challenges so you stay in sync.You will be able to see a test coverage report in GitHub on the Actions tab of your data-structures-and-algorithms
repository. It should match what you saw on your terminal in the above steps. Your graders will be looking at this as well.