📞📱☎️📡🌐 Cloud Native Telecom Initiative (CNTI) Test Catalog is a tool to check for and provide feedback on the use of K8s + cloud native best practices in networking applications and platforms
Currently, it is possible to run cnf_setup multiple times for multiple CNFs/helm charts. When running tests then, tests are executed on each configured CNFs.
Clarify whether this is a supported feature. Currently, there is no documentation nor tests of this behavior.
If this should be supported behavior, address those aspects:
Add this to documentation
Add spec test(s) to verify expected functionality
Fix behavior of generating result yaml files. Currnently, just one yaml file is being generated; results of particular test are overwritten, and it records result only of the latest CNF. Which if obviously not expected behavior. Right behavior needs to be figured out and implemented.
If this is not supported usage, don't allow to call cnf_setup multiple times.
The value of this feature is very low: The same results can be obtained by calling setup/test/cleanup in series with almost no duration difference.
That feature creates confusions by usage by mistake. Users sometimes call multiple cnf_setup with different CNFs and then they are confused by results.
That feature would require resources for documentation, testing and maintenance. That resources can be used better.
Currently, it is possible to run cnf_setup multiple times for multiple CNFs/helm charts. When running tests then, tests are executed on each configured CNFs. Clarify whether this is a supported feature. Currently, there is no documentation nor tests of this behavior. If this should be supported behavior, address those aspects:
If this is not supported usage, don't allow to call cnf_setup multiple times.