To provide additional practice writing JavaScript functions to solve a specific task, you will be required to complete one code challenge per day during weeks: 2, 4, 5, 7, 8, and 10. Totaling 30 challenges.
These code challenges are considered deliverables, and thus 80% of them must be completed in combination with other deliverable homework/assignments in order to receive a Certificate of Completion.
You may choose to do more than one per day, or none at all - just don't fall too far behind!
Fork
andClone
this repositorynpm install
(You only need to run this once)- Each day, open the repo in VS Code and work in the
challenges.js
file
-
All challenges have one or more tests that run when the command
npm run test
is excuted from your terminal in this directory. You can use ctrl+c or q from within the terminal window to exit the test suite. -
By default, Jest (the testing framework) will run all of the tests in order. To only run one of the files, start the testing suite with
npm run test
and press p to bring up the filtering option. Here you can type in which test file to run, ie:basic
,intermediate
,hard
and hit enter or return. -
As you solve your challenges and save your files, the testing suite will re-run the tests for you.
-
Solve the challenges by completing the functions in the
challenges.js
file only. DO NOT MODIFY ANY OTHER FILE. -
Each code challenge requires writing a single function to solve.
-
Be sure to name the function exactly as specified by the challenge.
-
The default display shows only the challenges that are failing. You'll see a green indicator at the bottom telling you how many have passed.
-
After solving a challenge, be sure to check the solution(s) contained in
solutions.js
. If multiple solutions are provided, they are typically shown in increasing order of "elegance".
- Your instructors will be checking your progress from time-to-time. As you solve the challenges, add and commit your work, and
git push origin main
. This pushes the updates to your fork. - At the end of Week 11, we will have you make one pull request on the main repo in the org using the PR Guidelines.