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

Implement e2e tests using k6 #315

Open
pablochacin opened this issue Aug 23, 2023 · 0 comments
Open

Implement e2e tests using k6 #315

pablochacin opened this issue Aug 23, 2023 · 0 comments
Labels
design proposal Requires a design document for discussion internal improvement improves code quality or organization

Comments

@pablochacin
Copy link
Collaborator

pablochacin commented Aug 23, 2023

Presently the disruptor's e2e tests are implemented in go. These tests rely on a massive library developed in the project for

  • Setting up a test cluster (using kind)
  • Configuring the cluster (e.g. installing an ingress controller)
  • Deploying the artifacts required for the test (pods, services, ingresses)
  • Executing some actions and performing some validations

Maintaining this library in the project creates a considerable overhead. Therefore, it would be convenient to reuse existing tools in the k6 ecosystem:

  • xk6-kubernetes for creating the test artifacts
  • k6 for executing the test and performing validations

One task that seems to be outside the scope of these tools is the creation and configuration of the cluster itself, including:

  • Exposing a port to access the kind cluster
  • Install an ingress controller
  • pre-load images needed by the tests (in particular, the disruptor's agent image that is built locally)

This task could be maintained in the project and potentially externalized as a separate tool.

k6-environment seems a promising candidate to help in this task.

@pablochacin pablochacin added enhancement New feature or request design proposal Requires a design document for discussion internal improvement improves code quality or organization and removed enhancement New feature or request labels Aug 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
design proposal Requires a design document for discussion internal improvement improves code quality or organization
Projects
None yet
Development

No branches or pull requests

1 participant