title: How to test in-app-purchases easily, without publishing or signing it first?
body: <h2>Background</h2>
  
  <p>My app has some in-app billing (like <a href="https://developers.google.com/events/io/sessions/324958374" rel="noreferrer"><strong>this one</strong></a>), and I wish to test it out before publishing it.</p>
  
  <p>I've watched some google IO lectures and read some articles, and prepared everything.</p>
  
  <p>According to what i've learnt (talked about <a href="https://www.youtube.com/watch?feature=player_detailpage&amp;v=DgcJPIRpfSk#t=1827" rel="noreferrer"><strong>here</strong></a>), all I need to do is just add my email to the test accounts, and it won't be charged. </p>
  
  <h2>The problem</h2>
  
  <p>It seems that in the developer console, the in app items cannot be activated.</p>
  
  <p>I think it's because the app isn't published yet, but that's the whole point of testing - I want to test the app before publishing it...</p>
  
  <p>As I've also found out, in order to test in-app billing, I have to do a lot of things to take care of for making it work, also having many restrictions and annoyances:</p>
  
  <ol>
  <li><p>sign the app and upload it to the play store . if you don't use a signed app, you get <a href="https://stackoverflow.com/questions/5522323/application-error-this-version-of-the-application-is-not-configured-for-market"><strong>this message</strong></a> ("This version of the application is not configured for Market Billing...") .</p></li>
  <li><p>make credit cards be used to the devices, even if they won't cost anything.</p></li>
  <li><p>let others do the testing instead of myself, as my account cannot be used for that. not only that, but instead of adding exactly which you wish to add, you have to create a google group and there put the people who will be able to use the app, and all will have to have a google+ account... You will also need to wait some time till the testers will be able to use in-app-billing of your app and till then they will get an error "User is not eligible for this purchase" .</p></li>
  <li><p>because of #1, I need to have some kind of mechanism to reset the purchases, within the app itself, but i also shouldn't forget to remove/hide this features for the end users, so that they won't reset it by mistake</p></li>
  <li><p>because of #1, if I wish to be able to debug the app, I need to change it on the manifest, and choose to debug the app within Eclipse, and also remember to uncheck this flag before actually releasing the app.</p></li>
  <li><p>since the app is on the play store, you cannot modify in-app purchases items (their Id for example), as opposed to many thing you can modify before publishing the app. It's no longer a development as flexible as it can be using simple development. It's like your app should be sealed with what you choose even though you haven't published it yet.</p></li>
  </ol>
  
  <h2>The question</h2>
  
  <p>Why is it this way? </p>
  
  <p>How come there isn't a simple way to allow to test the in-app-billing ?</p>
  
  <p>How would you deal with the problems I've written about?</p>
  
  <p>Is it possible to test the in-app purchases before the app is published? </p>
  
  <p>How come I can't use my own google account ?</p>
  
  <p>Also, suppose I do make a (fake) purchase, how do I reset it (all/specific purchases) in order to check it out again? Is it true I can't do it anywhere besides the app itself?</p>
  
  <p>Am I missing anything?</p>