Testing is a big topic with lots of nuances. Testing pure functions is one thing, but testing an application with database interaction, sending network queries, emails, and using timers and asynchrony is another. Even error testing has its own peculiarities.
By organizing these tests properly, maintaining them won't be too difficult, and you'll be able to work much faster. If it's done wrong, however, it's very easy to fall into the trap of seemingly having tests, but they're hard to write, keep breaking, and you have to rewrite them often.
This course is about how to test complex situations with side effects, and asynchronous code, including code bound to timers. Main topics:
- Error Testing. Snapshot tests.
- Fixtures. Organizing test data.
- Isolating side effects. Stubs. Dependency inversion.
- Moki. Black box testing.
- Timers. Time management.
- Testing asynchronous code.
Further reading
Since this is an advanced testing course, it expects a certain amount of knowledge on your part. Below is a list of what you might need in different lessons to fully understand them:
- Modules for working with the file system: fs, path <!---* HTTP--->
Recommended materials
Are there any more questions? Ask them in the Discussion section.
The Hexlet support team or other students will answer you.
For full access to the course you need a professional subscription.
A professional subscription will give you full access to all Hexlet courses, projects and lifetime access to the theory of lessons learned. You can cancel your subscription at any time.
