This is a project using React with Redux, React-testing-library, and Cypress to test the app. To take data about products, I used this nice project: http://fakestoreapi.com/ (thanks a lot to @keikaavousi for this awesome work, it is so helpful).
Just for fun and to investigate with React, Redux, React testing library, and GithubActions. It's an ugly design, I know it 😅, but if you want to give some feedback about, and help me to do it better I'm glad to ear suggestions.
This project was bootstrapped with Create React App.
In the project directory, you can run:
Just run the following command to run the app in a docker container. With this way you don't need to install node or anything else into your computer, you only need to have docker installed:
Runs the app in the development mode. Open http://localhost:3000 to view it in the browser.
The page will reload if you make edits. You will also see any lint errors in the console.
Launches the test runner in the interactive watch mode.
Launches the test runner just one time.
Follow this steps:
Run yarn startto run the server.
Run yarn cypressto run cypress enviroment and see the e2e test in a navigator.
Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.
The build is minified and the filenames include the hashes. Your app is ready to be deployed!
See the section about deployment for more information.
Note: this is a one-way operation. Once you eject, you can’t go back! 💥
If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.
Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.
You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.