- Keep Calm! Test On!
- Now that you're familiar with the concepts of testing, your goal is to write tests for an API that is already in production. (This happens a lot :))
- Answers to your written questions will be recorded in ANSWERS.md
- This is to be worked on alone, but you can use outside resources. You can reference any old code you may have, and the React Documentation, however, please refrain from copying and pasting any of your answers. Try and understand the question and put your responses in your own words. Be as thorough as possible when explaining something.
- Just a friendly Reminder Don't fret or get anxious about this, this is a no-pressure assessment that is only going to help guide you here in the near future. This is NOT a pass/fail situation.
Questions - Self Study - You can exercise your Google-Fu for this and any other Sprint Challenge in the future.
- In Jest, what are the differences between
beforeAll
,afterAll
,beforeEach
, andafterEach
? When do they run? What are they used for? - What is the point of Test Driven Development? What do you personally think about this approach?
- What is a
mock function
? How do we use it to test acallback
passed to a function? - Mention three types of tests.
- What type of test performs database operations against a real server.
- Fork/Clone this project into a directory on your machine.
cd
into your forked local copy.- notice there is a
package.json
file included. We have included all of the dev-dependencies that you'll need to build your project. - run
yarn
to download and install all the dependencies you need for this project. - run
yarn test
to start your tests. - Keep an active log of your changes by committing with Git and pushing often to GitHub.
- Write all of your tests in the
server.test.js
file.
- You're going to be writing the tests for a CRUD API.
- The API itself is really simple. Your task is to peek at the endpoints found in the
server.js
file and write the tests for them.
- The provided API has already been manually tested.
- Your job is to write
unit and integration tests
to ensure that the endpoints do what they're supposed to do. - Each endpoint should have multiple tests to ensure that different sorts of input are handled correctly/as expected. As a guideline, write at least two tests for each endpoint.
- THERE IS NO NEED TO
YARN START
, BUT YOU'LL WANT TO ENSURE THAT YOU HAVE AMONGO
INSTANCE UP AND RUNNING.
-
The
POST
method should take in an object that looks like this{ title: 'California Games', genre: 'Sports', releaseDate: 'June 1987' }
-
Our get method should return the list of games.
-
REMINDER That this data structure returned from Mongo will be an array, so to test your game with a
beforeEach
hook you'll need to make sure you test against the first item in the arrayexpect(res.data[0].foo).to.equal(bar.foo);
DELETE
can take an ID off of the route parameter and delete the corresponding game if it exists or return a 404 and an object with a message if the game does not exist in the database.
- Just like in class, send up the information you want changed on the server via the
req.body
.