Update README.md
This commit is contained in:
parent
0747078d97
commit
47ddb0f87d
|
@ -15,7 +15,7 @@ If you have a suggestion to improve an exercise, an idea for a new exercise, or
|
|||
2. Before you start working on any execises, you should first ensure you have the following installed:
|
||||
* **NPM**. You should have installed NPM already in our [Installing Node.js](https://www.theodinproject.com/lessons/foundations-installing-node-js) lesson. Just in case you need to check, type `npm --version` in your terminal. If you get back `Command 'npm' not found, but can be installed with:`, **do not follow the instructions in the terminal** to install with `apt-get` as this causes permission issues. Instead, go back to the installation lesson and install Node with NVM by following the instructions there.
|
||||
* **Jest**. After cloning this repository to your local machine and installing NPM, go into the newly created directory (`cd javascript-exercises`) and run `npm install`. This will install Jest and set up the testing platform based on our preconfigured settings.
|
||||
3. Each exercise includes 3 files: a markdown file with a description of the task, an empty (or mostly empty) JavaScript file, and a set of tests. To complete an exercise, you'll need to go to the exercise directory with `cd exerciseName` in the terminal and run `npm test exerciseName.spec.js`. This should run the test file and show you the output.
|
||||
3. Each exercise includes 3 files: a markdown file with a description of the task, an empty (or mostly empty) JavaScript file, and a set of tests. To complete an exercise, you'll need to go to the exercise directory with `cd exerciseName` in the terminal and run `npm test exerciseName.spec.js`. This should run the test file and show you the output. After installation is complete NPM may warn you of vulnerabilities. To resolve run `npm audit fix`.
|
||||
* When you first run a test, it will fail. This is by design! You must open the exercise file and write the code needed to get the test to pass.
|
||||
4. Some of the exercises have test conditions defined in their spec file as `test.skip` compared to `test`. This is purposeful. After you pass one `test`, you will change the next `test.skip` to `test` and test your code again. You'll do this until all conditions are satisfied. **All tests must pass at the same time**, and you should not have any `test.skip` instances by the time you finish an exercise.
|
||||
5. Once you successfully finish an exercise, check TOP's `solutions` branch to compare it with yours.
|
||||
|
|
Loading…
Reference in New Issue