- Notifications
You must be signed in to change notification settings - Fork208
Test Node.js Backends on TestingJavaScript.com
License
kentcdodds/testing-node-apps
Folders and files
| Name | Name | Last commit message | Last commit date | |
|---|---|---|---|---|
Repository files navigation
👋 hi there! My name isKent C. Dodds! This is aworkshop repo to teach you how to test your Node.js Apps!
- Have fundamental understanding and experience with automated testing andtools. (Additional learning material:But really, what is a JavaScript test?andBut really, what is a JavaScript mock?)
- Have experience with modern JavaScript APIs and features.
All of these must be available in yourPATH. To verify things are set upproperly, you can run this:
git --versionnode --versionyarn --version# or npm --versionIf you have trouble with any of these, learn more about the PATH environmentvariable and how to fix it here forwindows ormac/linux.
If you want to commit and push your work as you go, you'll want toforkfirst and then clone your fork rather than this repo directly.
After you've made sure to have the correct things (and versions) installed, youshould be able to just run a few commands to get set up:
git clone https://github.com/kentcdodds/testing-node-apps.gitcd testing-node-appsnode setupThis may take a few minutes.It will ask you for your email. This isoptional and just automatically adds your email to the links in the project tomake filling out some forms easier.
If you get any errors, please read through them and see if you can find out whatthe problem is. If you can't work it out on your own then pleasefile anissue and provideall the output from the commands you ran (even ifit's a lot).
If you can't get the setup script to work, then just make sure you have theright versions of the requirements listed above, and run the following commands:
npm installnpm run validateIt's recommended you run everything locally in the same environment you work inevery day, but if you're having issues getting things set up, you can also setthis up usingGitHub Codespaces(video demo) orCodesandbox.
This is the backend forBookshelf. I recommend you playaround with it a little bit to get an idea of the kind of data we're dealingwith here.
User
- id: string
- username: string
List Item
- id: string
- bookId: string
- ownerId: string
- rating: number (-1 is no rating, otherwise it's 1-5)
- notes: string
- startDate: number (
Date.now()) - finishDate: number (
Date.now())
For convenience, our we return a
bookobject on each list item which is thebook it's associated to. You're welcome frontend folks!
/me wishes we could use GraphQL
Book
- id: string
- title: string
- author: string
- coverImageUrl: string
- pageCount: number
- publisher: string
- synopsis: string
npmtestThis will startJest in watch mode. Read the output andplay around with it. You'll be working in the.exercise files.
src/**/__tests__/[title].md: Background, Exercise Instructions, Extra Creditsrc/**/__tests__/[title].exercise.js: Exercise with Emoji helperssrc/**/__tests__/[title].final.js: Final versionsrc/**/__tests__/[title].final.extra-#.js: Final version of extra creditsrc/**/[title].js: The source file that you'll be testing
The purpose of the exercise isnot for you to work through all the material.It's intended to get your brain thinking about the right questions to ask me asI walk through the material.
Here's the order of exercises we'll be doing as well as where you can find themarkdown file associated with each.
- 🏋 Testing Pure Functions:
src/utils/__tests__/auth.md - 🏋 Testing Middleware:
src/utils/__tests__/error-middleware.md - 🏋 Testing Controllers:
src/routes/__tests__/list-items-controller.md - 🏋 Testing Authentication API Routes:
src/__tests__/auth.md - 🏋 Testing CRUD API Routes:
src/__tests__/list-items.md
Each exercise has comments in it to help you get through the exercise. These funemoji characters are here to help you.
- Kody the Koala 🐨 will tell you when there's something specific you shoulddo
- Matthew the Muscle 💪 will indicate what you're working with an exercise
- Chuck the Checkered Flag 🏁 will indicate that you're working with a finalversion
- Marty the Money Bag 💰 will give you specific tips (and sometimes code)along the way
- Hannah the Hundred 💯 will give you extra challenges you can do if youfinish the exercises early.
- Olivia the Owl 🦉 will give you useful tidbits/best practice notes and alink for elaboration and feedback.
- Dominic the Document 📜 will give you links to useful documentation
- Berry the Bomb 💣 will be hanging around anywhere you need to blow stuffup (delete code)
- Peter the Product Manager 👨💼 helps us know what our users want
- Alfred the Alert 🚨 will occasionally show up in the test failures withpotential explanations for why the tests are failing.
"node setup" not working
If you're confident that your system meets the system requirements above, thenyou can skip the system validation and manually setup the project:
npm installnpm run validateIf those scripts fail, please try to work out what went wrong by the errormessage you get. If you still can't work it out, feel free toopen anissue withall the output from that script. I will try to help if Ican.
Thanks goes to these wonderful people(emoji key):
Kent C. Dodds 💻📖🚇 | Justin Dorfman 🔍 | Andrew Mason 📖 |
This project follows theall-contributorsspecification. Contributions of any kind welcome!
This material is available for private, non-commercial use under theGPL version 3. If youwould like to use this material to conduct your own workshop, please contact meatme@kentcdodds.com
Each exercise has an Elaboration and Feedback link. Please fill that out afterthe exercise and instruction.
At the end of the workshop, please go to this URL to give overall feedback.Thank you!https://kcd.im/tna-ws-feedback
About
Test Node.js Backends on TestingJavaScript.com
Topics
Resources
License
Code of conduct
Contributing
Uh oh!
There was an error while loading.Please reload this page.
Stars
Watchers
Forks
Uh oh!
There was an error while loading.Please reload this page.
Contributors4
Uh oh!
There was an error while loading.Please reload this page.
