Week 13

Introduction to Testing

Testing React Components with RTL

Software Quality in Practice

Wrapping up

Practice

Assignment

• Teachers

Frontend Track

Step back and look at what you can now do. You can take a pure function and pin its behaviour down with thorough unit tests. You can test a component the way a user experiences it, including the asynchronous parts. You can run an accessibility pass with axe, drive a small feature with TDD, review a teammate's pull request like a professional, and explain where production monitoring fits in. That's the full quality toolkit for a frontend developer.

The mindset underneath all of it: quality is a habit, not a final step. You don't build the app and then "do testing". You build the safety net as you go, so you can move faster with more confidence.

Bringing it back to your portfolio

Your assignment this week is to make your portfolio verifiably good, not just good-looking:

• Add unit tests for at least two utility functions; date formatting, filtering, slugifying, whatever yours has.
• Add component tests for one or two key components; your project card and your contact form are perfect candidates.
• Add at least one accessibility test with axe.
• Open a pull request for your changes and exchange reviews with a classmate, practising the feedback habits from this chapter.

💡 The goal isn't 100% coverage. It's confidence; a portfolio you can refactor without fear, hand to a reviewer with pride, and trust to work for every visitor. That's what these tests buy you.

The HackYourFuture curriculum is licensed under CC BY-NC-SA 4.0 *https://hackyourfuture.net/*

Built with ❤️ by the HackYourFuture community · Thank you, contributors

Found a mistake or have a suggestion? Let us know in the feedback form.