-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🧪 ✨ Let's Get Code Coverage to 80% ✨ #367
Comments
Hi, My colleague Ana Rita and I are students at masters in software engineering at FEUP (https://paginas.fe.up.pt/~estudar/mesw/). As part of evaluating one of the curriculum units, we need to choose an open-source project and fix an issue. We would like to know if we could help with this issue? |
Hi @FranciscoBastos. Yes, absolutely! You and Ana can choose a component (or other parts of the codebase) and go from there with your testing! Try to keep your PRs limited to one piece of code or a single component. And have fun! |
Hi, @LowLifeArcade, could you assign me to the issue then? @RitaVeiga and I would like to take this issue! |
You got it @FranciscoBastos! |
Hi @LowLifeArcade me, and @RitaVeiga are getting the following error when running the tests, do you know how can we fix it? |
Hi, @LowLifeArcade @RitaVeiga and I have already been able to run the tests, and we have also written some test scripts. They are selenium test scripts that test the front-end of the application. They consist of E2E integration testing, and I think it was a reasonable effort on a first approach. We will keep updating the test suit so you can reach 80% of coverage! |
What should we change and why?
Thank you @idiglove 🙏 for adding test coverage to the
Card
component. We could use more! If you want to contribute to getting the code base test coverage to 80%, please join in 🦖Check out #354 for an example.
The text was updated successfully, but these errors were encountered: