Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Feature: e2e GitHub action testing #1218

Closed
laurentsimon opened this issue Nov 4, 2021 · 3 comments
Closed

Feature: e2e GitHub action testing #1218

laurentsimon opened this issue Nov 4, 2021 · 3 comments
Labels
kind/enhancement New feature or request
Projects
Scorecard

Comments

@laurentsimon
Copy link
Contributor

laurentsimon commented Nov 4, 2021 •
edited

We need a way to validate that our GH action works as expected in the GitHub scanning dashboard.
Ideally, we want tests that automatically run the action a pre-defined test repos, then use the GitHub APIs to collect the scanning results. This will give us high assurance that changes we make (SARIF, checks) do not break the GH action in any way.

A first step before e2e testing of the action is to have tests for the container image.
@laurentsimon laurentsimon added the kind/enhancement New feature or request label Nov 4, 2021
@github-actions
Copy link

github-actions bot commented Jan 5, 2022

Stale issue message

@laurentsimon laurentsimon reopened this Jan 13, 2022
@justaugustus justaugustus added this to Backlog in Scorecard via automation Feb 23, 2022
@naveensrinivasan
Copy link
Member

naveensrinivasan commented Mar 16, 2022 •
edited

ossf/scorecard-action#142 - We have initial e2e tests running on a cron every day.

@naveensrinivasan
Copy link
Member

With this ossf/scorecard-action#142 e2e are implemented.

Scorecard automation moved this from Backlog to Done Mar 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/enhancement New feature or request
Projects
Scorecard
Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@naveensrinivasan @laurentsimon