Contribution

Contribution

According to Qovery community plan, you can help the community to get more credits to your account (more info here). On the engine front, we will be happy to have contributions on the following topics:

• Add a test coverage report/manifest: we need to know what is the % of code covered by tests, allowing us to better focus on adding tests on untested code
• Update libs to get security audit checks 100% passed (no warnings nor errors)
• Clippy: in order to have a better code quality, we would like the code to be 100% Clippy compatible and add a check to GitHub action to automatically force that before allowing merge
• Add more tests: the engine requires a lot of functional tests, and end-to-end tests to be validated (because of third parties requirements). In order to speed up tests while having better test coverage, we need to have more unit tests. Unit tests allow test smaller features and are limited to one class and are way quicker to run than functional tests on Qovery side. It will allow running functional tests only if all unit tests are valid allowing then to catch bugs / failing features before functional tests.
• Typos and grammar: some sentences could be better, more understandable in some circumstances, typos exist as well. Anything related to a better understanding of sentences is welcome.