-
-
Notifications
You must be signed in to change notification settings - Fork 3
Add integration tests #36
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
Conversation
"LibrariesIndex": working_dir_path.joinpath("libraries", "library_index.json").as_posix(), | ||
"GitClonesFolder": working_dir_path.joinpath("gitclones").as_posix(), | ||
# I was unable to get clamdscan working in the GitHub Actions runner, but the tests should pass with this set to | ||
# False when run on a machine with ClamAV installed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As we were discussing in our chats, being this application something that has to run on a well defined environment, could make sense to include in this repo a Dockerfile
with a replica of the destination linux environment, included all the tools that this engine uses (like ClamAV)
if platform.system() == "Windows": | ||
cd_command += " /d" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same consideration as above, with a container that replicates the production environment we could get rid of this "OS dependant" code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The code is very ok, we could merge it and then address my comments about having a test container in a separate PR 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything looks great, just a small comment to edit to reach approval. 👍
This adds end to end testing of the tool to verify that the finished outputs are as expected.
Co-authored-by: Silvano Cerza <3314350+silvanocerza@users.noreply.github.com>
This adds end to end testing of the tool to verify that the finished outputs are as expected.