-
Notifications
You must be signed in to change notification settings - Fork 168
Inherit Makefile Integration Tests command for hooks #1028
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
Signed-off-by: Rami Souai <rami.souai@iteratec.com>
Signed-off-by: Rami Souai <rami.souai@iteratec.com>
Signed-off-by: Simon Hülkenberg <simon.huelkenberg@iteratec.com>
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.
LGTM. Only .PHONY tags we should add to at least all touched Makefiles.
As requested in the review Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
This is done to include the semgrep integration test fix
…ook folder This is done so these tests would run when "make integration tests" is called in the cascading-scan hook folder This goes hand in hand with issue #890 Signed-off-by: Ilyes Ben Dlala <ilyes.bendlala@iteratec.com>
include ../../hooks.mk | ||
|
||
.PHONY: test-2 | ||
test-2: | clean-integration-tests unit-tests docker-build docker-export kind-import deploy deploy-test-deps-2 integration-tests-2 |
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.
What does the |
here? Never seen this before and I'm too stupid to google it...
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.
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.
Second question: What does the 2 mean in the target name? We should avoid magic numbers in names.
Description
The integration-test command for hooks is now the same for all hooks, and uses npm run tests (With the exception of Persistance-DefectDojo which is in Java).
Now each hook can decide for itself what the
npm run test
command does in it's package.json file. For example, notification and cascading-scans hooks, which are in Typescript, add an extra build step.Checklist
npm test
runs for the whole project.