Repository files navigation

Like last time, there are two parts to this problem set:

• A written response section
• JavaScript small problems¹

To complete and submit this problem set, you will...

1. Your written response questions live in theshort-response.md file. Record your answers without removing the original questions. Use complete sentences and style appropriately with markdown.
2. Your small problems are in theproblems directory. The directory contains these files:
   • README.md
   • answers.js
   • index.html
   • answers.test.js

The problem prompts are inREADME.md. You are to write your solutions in theanswers.js file.You are to write your code inside the existing function declarations.

Example:

// Question 1functionthisIsAnExample(){returntrue;}

I included theindex.html file for you so that you can run your code in the browser and use Chrome Dev tools.

This is our first problem set withunit tests. Unit Testing is a way to ensure that your code functions as intended by breaking it up into smaller components and testing each part, independently. We will talk more about unit tests in the future. In fact, you will eventually write your own.

For now, just follow these steps to test your code using the tests that I wrote.

1. When you are ready to run your first test, runnpm install in the terminal. Think of this command as "installing" the tests.
2. Now, each time you want to run tests, runnpm test in the terminal. When you run the test suite, you will see some helpful information in the output. It will tell you which tests passed and failed and what the expected results of each of the tests were. Only when you have gottenall tests to pass can you submit this assignment.
3. Commit frequently.
4. When you are finished, push your changes to your remote repo and submit the URL thorugh Canvas.

1: Exercises adapted fromLaunch School small problems andCode Wars katas.