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
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: