Welcome to part 5 of a series on how to test a Vue component.
Here's the table of contents of the series:
- Starting out with tests
- The first test and snapshot testing
- Creating an instance of a component
- More tests and faking time
- Jest awesomeness and a skeleton to get started (you're here)
Jest watch mode
You know by now that Jest is an amazing testing tools that comes with jsdom and snapshot testing built in. But a thing we haven't touched upon is it's test runner. Typing
jest on the command line will make it run all the tests but it can do much more. It has an awesome interactive mode that you can start by
Jest is in this mode it will run the tests when one of the files in your project changes. You can also press
enter to manually trigger a test run. A very cool feature is that you can put a filter on which tests to run by pressing
Now when a file changes only the tests containing
storage in their name will run. I really wish all test runners (I'm looking at you PHPUnit) had this built in.
Our skeleton repository
Like already mentioned getting started with testing a Vue component was a pain because you need to have a good environment set up. To avoid going to through the same pain again I created a skeleton repo to kickstart Vue component development. Sebastian played a big role is setting all this up just right. This repo is what I'll be using myself when working on the next component.
Here's how you can get started with it:
- Clone the repo `firstname.lastname@example.org:spatie/skeleton-vue.git`
- Run `rm -rf .git` && `git init` to cut loose the connection to our repo on GitHub
- Run `yarn` to pull in the dependencies.
- Replace all occurrences of the string mentioned at the top of the readme.
Congratulations, you've reached the end of this series. I hope you liked learning all this stuff and that reading all of this make you want to start creating and testing a Vue component of your own. Although starting with testing may be daunting, try to persist and eventually you will be rewarded with progress and results. If you feel like you're stuck ask a colleague or a programming friend for some help.