“测试帐户”如何使用？与“普通帐户”有何不同？
为了能够测试 Android Market 许可的任何实施（例如 LVL、应用内结算），Google 建议创建一个 Google Checkout 测试帐户，因为开发者无法使用自己的 Google Checkout 帐户向自己购买。
听起来不错除了测试帐户必须使用真实信用卡。
这就引出了一个问题：这与普通帐户有何不同？测试账户与普通账户相比有什么优势？
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?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
测试帐户不必与 google checkout 帐户关联。发布者可以根据 Android Market 帐户设置他/她的 Google Checkout 帐户。作为开发人员，您可以创建一个测试帐户。
仅当应用程序上传到开发者控制台时，测试帐户持有者才能测试应用程序的 LVL 和应用内购买等。它不必发布。但它必须上传并激活并保存。
因此，测试帐户持有者必须在 Google 服务器上注册其财务详细信息是不正确的。只有出版商必须这样做。发布者可以根据需要添加任意数量的测试帐户持有者。发布者将提供发布密钥，这就是开发人员实现/测试其代码所需的全部内容。
在 Google 开发者网站上查找文档。它解释得很好。
HTH。
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.
您不需要单独的测试帐户。仅当您想将其他人纳入测试人员时才这样做。您自己的发布商帐户就可以了。如果您在开发者帐户中将 LVL 响应设置为“未许可”以进行测试，则只有使用该 Google 帐户设置的设备才会获得此测试响应。
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.