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

Proper testing method for new releases #9

Open
TechSupportJosh opened this issue Dec 30, 2020 · 1 comment
Open

Proper testing method for new releases #9

TechSupportJosh opened this issue Dec 30, 2020 · 1 comment
Labels
enhancement New feature or request in progress This issue is currently being worked on.

Comments

@TechSupportJosh
Copy link
Collaborator

Is your feature request related to a problem? Please describe.
Currently, there is no method of testing a new release, short of spinning up a few labs that are lying around and running them.

Describe the solution you'd like
A set of defined labs that can be used to automatically test new releases of Netkit. These labs would include features such as:

  • Simple lab with 3 machines pinging each other
  • Lab that tests Wireguard has been properly built into the kernel (and any another kernel additions)
  • Lab that tests tapout
  • Lab that tests entropy levels

These labs would then have an automated running script that can be used to produce a set of test outputs. This can then be used for CI/CD when implemented.

@TechSupportJosh TechSupportJosh added enhancement New feature or request in progress This issue is currently being worked on. labels Dec 30, 2020
@TechSupportJosh
Copy link
Collaborator Author

#42 introduced the first set of testing labs. We also need a way to test commands such as vdump, vcommand, etc.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request in progress This issue is currently being worked on.
Projects
None yet
Development

No branches or pull requests

1 participant