Roughly 55 of the tests are decorated @skip_if_no_connection and need KG_AUTH_TOKEN. They are run manually before pushing, but CI has no token, so they skip there and the passing runs leave no record anyone else can inspect. A reviewer, or a contributor without KG credentials, cannot see that they passed, nor produce such a record themselves.
If suitable credentials were available in CI (e.g., a pre-production service-account), then the full test suite could run against core.kg-ppd.ebrains.eu. Running this particular job as a GitLab CI pipeline on the EBRAINS mirror would keep the secrets on EBRAINS infrastructure.
Roughly 55 of the tests are decorated
@skip_if_no_connectionand needKG_AUTH_TOKEN. They are run manually before pushing, but CI has no token, so they skip there and the passing runs leave no record anyone else can inspect. A reviewer, or a contributor without KG credentials, cannot see that they passed, nor produce such a record themselves.If suitable credentials were available in CI (e.g., a pre-production service-account), then the full test suite could run against core.kg-ppd.ebrains.eu. Running this particular job as a GitLab CI pipeline on the EBRAINS mirror would keep the secrets on EBRAINS infrastructure.