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.

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

e2e: Added tests for Jsonnet and file rendering. #49

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

bwplotka
Copy link

Trying to revive this project a bit as we depend on it in Observatorium, plus experimenting with potential further use. (:

cc @brancz - let us know if you want our team to maintain this project / fork if we want to continue development - let us know your preference (:

Signed-off-by: Bartlomiej Plotka [email protected]

@brancz
Copy link
Owner

brancz commented Apr 20, 2022

We use this project in production so it's not dead at all, it was just doing exactly what we've needed for the last ~1.5years. But definitely happy to collaborate!

// TestFileExampleRender tests locutus in docker rendering of examples in `/example/files` directory.
// This e2e tests require `make docker` first.
func TestFileExampleRender(t *testing.T) {
e, err := e2e.NewDockerEnvironment("e2e_file")
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does this really need to run in docker?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I get that an e2e test for the kubernetes functionality should run on Kubernetes, but everything else should just be plainly run on the machine, no?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea, well, my arguments were:

  • The direct usage of Locutus is primarily through containers, so we test more by using the docker image directly
  • We have a ready testing framework for docker that is consistently used across all our project
  • Running full Kubernetes just to test Locutus sounds like overkill, plus it's hard to find CI for running Kubernetes for tests purposes (reliable one and ideally free/cheap).

But yea, happy to discuss - you would prefer using os.Exec?

Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah I think I would prefer os.Exec

@bwplotka
Copy link
Author

bwplotka commented Apr 20, 2022

Also see next idea: #50 - to see if we agree on common direction of Locutus - I think there is overlap (:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants