Most of items #1 and #3's scenarios would not be possible using test accounts. As for the RateExceededError, you can refer
here for more information on how these limits are encountered. You can test getting the rateScope = DEVELOPER by hitting the limits associated to a test account level access as stated
here.
As for the rateScope = ACCOUNT, you may try and perform a high number of requests within a short period of time against a single Google Ads (test/production) account.
For partial failures, you may refer to this
documentation instead for the implementation. Please note as well that not all scenarios or errors in the supported services may be tested using test accounts.
Best regards,
 |
| Peter Laurence Napa Oliquino |
| Google Ads API Team |
|
|
| |

ref:_00D1U1174p._5004Q28pJGg:ref