Hi, From a software engineering standpoint, we cannot recommend performing QA actions against a production environment. QA is meant to catch bugs or problems before they reach production. The sandbox environment was created specifically for this type of testing. We're not recommending you point your production system at the sandbox, but instead your QA/staging environment.
If a client makes an API call against the sandbox when they intended to go against production, it would likely fail in the sandbox as the credentials and account identifiers would likely not match (nor any other IDs that may have been specified). The call would be failed to be made against production, but it could be remade against production at a later time. Please keep in mind that you can make changes to your production code right now without causing any production issues. The production servers will ignore the developer token until we turn on the switch that requires it. Therefore you can test against the sandbox with the same code you use with production, see it fail, make the change to fix it, test sandbox and deploy to production in advance of the 1/17/2012 change and know your fix will work. The information this change will give us will be extremely helpful in monitoring use of reports and use this feedback when making future changes. - Kevin Winter AdWords API Team On Tuesday, November 15, 2011 8:10:18 PM UTC-5, dkasak wrote: > > Hi Kevin. I will clarify my point further. Regardless of whether we do our > coding and unit testing against the sandbox or not, we do *NOT* do QA or > production verification against the sandbox. This has always been the case, > for all search engines that we support. It would require hacking with ref > data to point our production system to the sandbox, and this is asking for > trouble. For example what happens when a client triggers an API call and it > goes to the sandbox instead of production? > > Seriously, if you're going to do out-of-release changes to your production > environment, then you'll have to give consideration to how we can release > our changes to our production environment ahead of your own production > patch, and verify that it's all working. > -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
