You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
File services endpoints are individually feature complete, but need thorough testing of endpoints working in conjunction with one another before we start onboarding BoG Project Teams onto File Services.
In this ticket, you will write tests for a variety of different scenarios that will use the file services APIs, including, but not limited to:
Registering a config for a team, registering a provider, creating a bucket, and uploading/downloading a file with the upload/download predesigned URLs
Incorrectly registering one of any combination of the 4 above (the remaining tasks should all not be run or fail)
Testing this behavior for multiple API keys in a project that each have different environments (different, unique configs)
API Keys for the same project but a different environment should not share a file service config (the config is per project per environment)
Testing this behavior for multiple API keys in a project that each share an environment (same config)
API Keys for the same project and the same environment should share a file service config (the config is per project per environment)
The text was updated successfully, but these errors were encountered:
File Services Testing
File services endpoints are individually feature complete, but need thorough testing of endpoints working in conjunction with one another before we start onboarding BoG Project Teams onto File Services.
In this ticket, you will write tests for a variety of different scenarios that will use the file services APIs, including, but not limited to:
The text was updated successfully, but these errors were encountered: