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

Adds the capability to test generated files #66

Closed
szkiba opened this issue Sep 11, 2024 · 0 comments · Fixed by #67
Closed

Adds the capability to test generated files #66

szkiba opened this issue Sep 11, 2024 · 0 comments · Fixed by #67
Assignees

Comments

@szkiba
Copy link
Collaborator

szkiba commented Sep 11, 2024

The generated registry and catalog will play an important role in the k6 binary provisioning subsystem, so it is important that there is no loss of service due to generated files. It is advisable to test the generated files to see if they meet the minimum requirements.

The --test flag should be used to test the registry and catalog files generated by the --api flag. The test is successful if the file is not empty, contains k6 and at least one extension, and if all extensions meet the minimum requirements (e.g. it has versions).


grafana/k6-ext-tooling#34

@szkiba szkiba self-assigned this Sep 11, 2024
@szkiba szkiba linked a pull request Sep 11, 2024 that will close this issue
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 a pull request may close this issue.

1 participant