-
Notifications
You must be signed in to change notification settings - Fork 12
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
Create pipeline to lint and test #32
Create pipeline to lint and test #32
Conversation
0f2ca9f
to
a8dfeda
Compare
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 version of the step actions/checkout
needs to be updated to v4 and the tests are currently failing, likely due to the way they are called: shunit2 tests/*
, they should instead be called with ./tests/tests.sh
.
I have left a few other comments, but they are all things that can be done in a different PR, it's just so I don't forget to open issues to track those features.
55e6932
to
0bd93bc
Compare
0bd93bc
to
6ed6f3c
Compare
I've spoke to Arthur and mentioned that the CI in the PR needs to pass before we review it again. |
5c528c9
to
b0de4a0
Compare
b0de4a0
to
2f5dc17
Compare
Closes: curl#29 Signed-off-by: Arthur Diniz <[email protected]>
2f5dc17
to
96505b6
Compare
Signed-off-by: Arthur Diniz <[email protected]>
96505b6
to
a428ccd
Compare
Summary
This pull request introduces a CI pipeline that sets up
automated testing
andshellcheck
for the project.Details:
Created a GitHub Actions workflow to run automated tests and shellcheck on every push and pull request targeting the main branch.
Shellcheck Job:
shellcheck
to lint thewcurl
scripts.shellcheck
on the shell scripts in thetests/
directory to identify potential issues.Test Job:
shunit2
(required for running tests) based on the operating system.shunit2
on thetests/
directory to validate the project functionality.Instructions for Testing:
No manual testing is required as this pipeline is automated. It will be triggered on every push and pull request, ensuring that all scripts are linted and tested for issues.
Dependencies
Before merge this Pull Request we need to make sure the #31 is merged otherwise the
shellcheck
will fail.