In this workshop, we'll focus on important skills and techniques for testing web applications of all kinds so you can avoid shipping bugs to your users.
All of these must be available in your PATH
. To verify things are set up
properly, you can run this:
git --version
node --version
npm --version
If you have trouble with any of these, learn more about the PATH environment variable and how to fix it here for windows or mac/linux.
This is a pretty large project (it's actually many apps in one) so it can take several minutes to get everything set up the first time. Please have a strong network connection before running the setup and grab a snack.
Follow these steps to get this set up:
git clone https://github.com/epicweb-dev/testing-web-apps.git
cd testing-web-apps
npm run setup
If you experience errors here, please open an issue with as many details as you can offer.
You'll find all the exercises in the exercises
directory. The structure of the
workshop apps is described below, but most of the time you should be able to
simply run the app and navigate around the different exercises using the
application (there are even buttons to open the right exercise file right in
your editor).
The purpose of the exercise is not for you to work through all the material. It's intended to get your brain thinking about the right questions to ask me as I walk through the material.
To get the app up and running (and really see if it worked), run:
npm start
Now open your browser to the address that's logged out for you and you're good to get started!
The test script in the package.json
runs the tests on the solutions (these
should all pass). To run the tests against your own work, you simply open the
problem page and click the "Test" tab.
The application has several buttons which will launch your editor to the right file. There are a lot of files in this workshop so you'll be using this feature a lot to get to the right place at the right time.
This should just workβ’οΈ, but if it doesn't it could be that our editor guessing
isn't working for you. If that's the case, create a .env
file in the root of
this project and add an environment variable called KCDSHOP_EDITOR
with the
value being set to the path to your editor's executable. For example, if you're
using VS Code on Windows, you'd add this to your .env
file:
KCDSHOP_EDITOR="C:\Program Files\Microsoft VS Code\bin\code.cmd"
Make certain that if the path includes spaces that you wrap the path in quotes as above.
playground
: This directory will be created when you start the workshop and it's where you'll spend the bulk of your time.exercises/*.*/README.md
: Exercise background informationexercises/*.*/*.problem.*/README.*.md
: Problem Instructionsexercises/*.*/*.problem.*/*.tsx
: Exercise with Emoji helpers (this is where the playground code comes from)exercises/*.*/*.solution.*/*.tsx
: Solved version
The purpose of the exercise is not for you to work through all the material. It's intended to get your brain thinking about the right questions to ask me as I walk through the material.
Each exercise has comments in it to help you get through the exercise. These fun emoji characters are here to help you.
- Kody the Koala π¨ will tell you when there's something specific you should do
- Lily the Life Jacket π¦Ί will help you with any TypeScript-specific parts of the exercises
- Marty the Money Bag π° will give you specific tips (and sometimes code) along the way
- Nancy the Notepad π will encourage you to take notes on what you're learning
- Olivia the Owl π¦ will give you useful tidbits/best practice notes
- Dominic the Document π will give you links to useful documentation
- Barry the Bomb π£ will be hanging around anywhere you need to blow stuff up (delete code)
- Matthew the Muscle πͺ will indicate that you're working with an exercise
- Chuck the Checkered Flag π will indicate that you're working with a final
- Peter the Product Manager π¨βπΌ helps us know what our users want
- Alfred the Alert π¨ will occasionally show up in the test failures with potential explanations for why the tests are failing
Each exercise has an Elaboration and Feedback form. Please fill that out after the exercise and instruction.
At the end of the workshop, there will be another form where you can leave overall feedback. I would greatly appreciate it if you do!