GPT 2.0.0: Group, Projects and User test changes
For 2.0.0 and the switch to opinionated data there's a few follow up tasks for the Groups and Projects tests to make them consistent and useful:
-
Add in a normal api_v4_groups
test but ensure it's using theowned
flag to lock it down to the specific user and test data for GPT. -
Merge the api_v4_project_
tests into a batch test calledapi_v4_projects
as this has been shown to be confusing to users. This should use our new batch approach for testing the same API endpoint with different flags. Also use theowned
flag. -
With 2.0.0
we're going to be recommending that a new user is created for the test data generation and testing. This allows for more consistent testing against the data via filters when required as well as easier cleanup for the users after testing. This change though has one small knock on effect with theweb_user
test. This test needs a username to view it's page. Best solution I can think of for this is for the config to be changed to have the username added to the main environment config beside URL and outside of the large project config.
Edited by Nailia Iskhakova