You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Presently the disruptor's e2e tests are implemented in go. These tests rely on a massive library developed in the project for
Maintaining this library in the project creates a considerable overhead. Therefore, it would be convenient to reuse existing tools in the k6 ecosystem:
One task that seems to be outside the scope of these tools is the creation and configuration of the cluster itself, including:
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.
The text was updated successfully, but these errors were encountered: