Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 10 months ago

Responsive React Tip calculator

react, vite, vitest, react-testing-library
Daniil•610
@DaniilGurski
A solution to the Tip calculator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

This was my first project with test writing which was one of the main learnings for me. I learned how to use vitest and testing library a little bit and I think it will be useful in future, more large-scale projects.

What challenges did you encounter, and how did you overcome them?

I found it a bit difficult to find resources and examples in terms of testing, so mostly used AI to answer some not-so-obvious questions.

What specific areas of your project would you like help with?

I'd like to know how I can improve my tests. For this project I wrote one large unit test because it was difficult to figure out how to do it with the context provider involved.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Daniil•610
    @DaniilGurski
    Posted 10 months ago

    Thank you for your feedback! I really thought my app was responsive until you pointed this out. There must be something small that breaks the layout on mobile.

  • SaakarX•320
    @saakarx
    Posted 10 months ago

    Hey Daniil, Congratulations on completing the challenge

    • You should check for invalid inputs for the calculateTip function you have in your utils directory. When I tried to change the input to text and input letters it gave NaN error on the result section. Maybe add validation for the function arguments if they are not valid numbers, it should return 0 for both tip and total per person.

    • Also, on mobile devices the website does not look like the design provided for the challenge.

    Hope this helps, overall your solution looks great ✌️.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
Frontend Mentor logo

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub