5

To be able test any implementation of Android Market licensing (e.g. LVL, In-app Billing), Google advises to create a Google Checkout test account, since the developer cannot buy from himself using his own Google Checkout account.

Sounds great except that the test account must use a real credit card.

Which begs the question: How is this different from a normal account? What is the advantage of a test account over a normal account?

Community
  • 1
  • 1
Bill The Ape
  • 3,261
  • 25
  • 44

2 Answers2

0

You don't need a separate test account. That's only if you want to include others as testers. Your own publisher account is just fine. If you set the LVL response in your developer account to, say "UNLICENSED" for testing purposes, then only the devices that are set up with that Google account will get this test response.

Wytze
  • 7,844
  • 8
  • 49
  • 62
0

The test account does not have to be associated with the google checkout account. The publisher can have his/her google checkout account set up against the android market account. And as a developer, you can have a test account created. Test account holders can test the application for LVL and in-app purchasing, etc only if the application is uploaded on the developer console. It does not have to published. But it has to uploaded and activated and saved. So, it's not true that the test account holder has to have his/her financial details registered with the Google servers. Only the publisher has to do that. And the publisher can add as many test account holders as he/she desires. The publisher will provide a publishing key and that's all the developers need to implement/test their code.

Look for documentation on Google developer site. It explains well.

HTH.

VJ Vélan Solutions
  • 6,434
  • 5
  • 49
  • 63
  • I wish your answer were correct but based on actual experience with in-app-billing it isn't. Have you actually tried what you said with [In App Billing](http://developer.android.com/guide/market/billing/index.html)? – Bill The Ape Feb 16 '12 at 17:02
  • Yes. What i have written is based on my experience and not just reading the documentation. In my case, the documentation and my experiences match. If that were not the case, i believe, the developer/publisher community would have been up in arms :) – VJ Vélan Solutions Feb 17 '12 at 17:51