Add library policies to e2e about gatekeeper-library HOT 6 CLOSED

Could anyone explain current expected dev flow? I can create src.rego and src_test.rego and run opa test src.rego src_test.rego to test it. But how can i test constraint template?

from gatekeeper-library.

That's a good question and one we've started working on answering!

The draft design for building a constraint template build/test workflow is here:

https://docs.google.com/document/d/1uQlkIBQcgNNyth8o9ufYaVSfUq_JLJGy9fcuW3VB7vU/edit

Definitely interested in feedback and help implementing :)

from gatekeeper-library.

This may be complicated by us not knowing where the library will actually live in the long term. Moving them out of this Repo would be harder if we rely on them for e2e tests.

from gatekeeper-library.

While they're here though it would be good to have confidence that they all work as expected. And presumably the tests could move with the library when it finds its new home, with a bit of refactoring.

from gatekeeper-library.

My concern is flakiness. Currently we are running into timeouts b/c presumably the VM Travis CI provides has low enough resources that it takes a while for initialization to happen. Higher #s of flaky tests => lower probability of a good run even with valid code.

I'd like to keep the e2e tests in the GK project focused on whether GK itself works. Unit tests should be sufficient for the library. Plus they'd have zero flakiness as they wouldn't rely on a live service.

In order to have unit tests, however, we need a unit test framework, which implies that the library repo has been implemented.

from gatekeeper-library.

This issue/PR has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. Thank you for your contributions.

from gatekeeper-library.