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

[Feature] Cloud Native Tagging #849

Open
wvwatson opened this issue Jul 12, 2021 · 1 comment
Open

[Feature] Cloud Native Tagging #849

wvwatson opened this issue Jul 12, 2021 · 1 comment
Labels
enhancement New feature or request

Comments

@wvwatson
Copy link
Collaborator

wvwatson commented Jul 12, 2021

Is your feature request related to a problem? Please describe.
Different user profiles (Network equipment/software manufacturer, Telco Service Provider, CNF Developer, Cloud Native Community) have different non-functional requirements that they desire. The current system does not support a way to easily run the system with these concerns in mind.

Describe the solution you'd like
The system should have different tags for the user profiles e.g. NEM, SP, or CN like so:
cnf-testsuite nem
cnf-testsuite sp
cnf-testsuite cn

The documentation would have all tests that are not cloud native tests to have their own category under profile specific tests. This would allow the different user categories to contribute their own weighting.

Describe alternatives you've considered
One alternative is to offer a la cart testing, which is to allow the user to list each test or category of tests specifically.
Another alternative is to focus on having tests that measure cloud native non-functional requirements exclusively, allowing any networking concerns that fail 'cloud-nativeness' to fail outright.

@wvwatson wvwatson added enhancement New feature or request 3 pts labels Jul 12, 2021
@lixuna lixuna removed the 3 pts label Feb 28, 2024
@lixuna lixuna moved this to Todo in CNTI Test Catalog Mar 18, 2024
@kosstennbl
Copy link
Collaborator

Don't see this as a big priority, but some additional test grouping can be implemented by creating separate SAM tasks, that would be running needed tests or whole test categories.
To me - should be done if some request comes from different community (e.g. Silva), if they would benefit from something like this and wouldn't be able to easily implement this on their side. Doing this as precaution doesn't make much sense to me, we just don't know which tests would be useful for what users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: To do
Status: Todo
Development

No branches or pull requests

3 participants