Closed chandrams closed 2 weeks ago
By extending the /listMetricProfiles
API to support name
and verbose
query parameters below are the additional test scenarios to be considered
name
query parameterverbose
query parametername
and verbose
query parametersname
and verbose
Define test scenarios for validating Metric profile API
Create a perf profile with a valid yaml using kubectl, list the perf profile and validate the profile
Create a perf profile with a valid json using kubectl, list the perf profile and validate the profile
Create a perf profile with a valid json using the API, list the perf profile and validate the profile
Create multiple perf profiles using the API and list the perf profiles
Create the perf profile twice, validate for appropriate error message
Create a perf profile with an invalid yaml using kubectl, validate for appropriate error message
Create a perf profile with an invalid json using kubectl, validate for appropriate error message
Create a perf profile with an invalid json using API, validate for appropriate error message
Create a perf profile with a valid yaml using kubectl, use the same perf profile json equivalent and create a perf profile using the API - Will this create a perf profile again?
List perf profiles without creating any profiles
Is list perf profiles taking a profile name as input?
Update perf profile by updating the below in each test scenario, ensure updates to only allowed fields work and appropriate error message is thrown. Validate the updated metric profile using listMetricProfiles and ensure recommendations are generated using the updated queries.
Delete the specified metric profile and validate it using list. Is deleteMetricProfile taking the name as input?
Delete a metric profile that is in use
Delete a non-existing metric profile
Validate the metric profiles are loaded again from the DB on kruize restart