I need to add tests for create and delete flavors, specifically. This is one use case that I have come across.
* Create and delete flavor api can only be run by a user with an "admin" role. A user with Member role is unauthorized as per policy.json for flavorsmanage.
Currently, the default behavior is to run tests as non-admin users (list flavors, get flavor details etc). which is fine.
* To test create delete, i'd also need to call list. So either I run the whole suite as admin or just the create and delete API as
admin user.
Please suggest.
I do agree with your suggestions to separate the admin tests into another directory.
Hi Jay,
I need to add tests for create and delete flavors, specifically. This is one use case that I have come across.
* Create and delete flavor api can only be run by a user with an "admin" role. A user with Member role is unauthorized as per policy.json for flavorsmanage.
Currently, the default behavior is to run tests as non-admin users (list flavors, get flavor details etc). which is fine.
* To test create delete, i'd also need to call list. So either I run the whole suite as admin or just the create and delete API as
admin user.
Please suggest.
I do agree with your suggestions to separate the admin tests into another directory.