add fuzz testing to ci-cd #353
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Davidson-Souza
requested changes
Jan 27, 2025
erickcestari
force-pushed
the
add-fuzz-testing-ci-cd
branch
from
82f8ceb to
31ad399
Compare
|
@Davidson-Souza I’ve added caching to the most critical parts. If you need any adjustments or have suggestions, feel free to let me know. Also, it would be great if @brunoerg could review this—he might spot some good areas for improvement. |
|
Concept ACK |
brunoerg
reviewed
Feb 3, 2025
|
You can squash the commits. |
every pr or push to master will trigger all the fuzz testing located on floresta-fuzz change branch main to master add dep caching use actions upload artifact v4 instead of v3 which is deprecated change each target time to 1 minute
erickcestari
force-pushed
the
add-fuzz-testing-ci-cd
branch
from
90ef05f to
35b7729
Compare
|
ACK 35b7729 I ran this on my own fork and it works fine. |
Davidson-Souza
approved these changes
Feb 3, 2025
brunoerg
approved these changes
Feb 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What is this PR for?
This PR introduces automated fuzz testing to the CI/CD pipeline. Every pull request or push to the master branch will trigger all the fuzz tests located in the floresta-fuzz directory.
What is the purpose of this pull request?
Which aspect of floresta its being addresed?
Checklists
just lint;cargo test;Description
This PR addresses the addition of fuzz testing to the CI/CD pipeline, as outlined in issue #350. The goal is to enhance the robustness and reliability of the codebase by automatically running fuzz tests on every PR and push to the master branch.
Notes to the reviewers
Fuzz testing is a powerful technique to uncover edge cases and potential vulnerabilities by providing random, invalid, or unexpected inputs to the system. Integrating it into the CI/CD pipeline ensures that these tests are run consistently, catching issues early in the development process.
The fuzz tests are located in the floresta-fuzz directory. The CI/CD pipeline has been updated to include a step that triggers these tests automatically.
This change should not affect the existing functionality of the codebase but will help in identifying and fixing potential issues before they reach production.