This option offers another way to limit distribution of an app to only a certain group of testers, while preventing anyone else from discovering your app in the Store (or acquiring it without a promotional code). Hiding the app in the Store and using promotional codes Package flights can be used with apps targeting any OS version, but your testers can only get the app if they are running Windows.Desktop build 10586 or later Windows.Mobile build 10586.63 or later or Xbox One.įor more info, see Package flights. This is a great way to try out different packages simultaneously, and you can pull packages from a flight into your non-flighted submission if you decide the packages are ready to distribute to everyone. You can even create multiple package flights for the same app to use with different groups of people. If you have published your app already, you can create package flights to distribute a different set of packages to the people that you specify.
#Starmancer beta testing windows#
You can use this option with apps targeting any OS version, but your testers must be running Windows 10, version 1607 or higher (including Xbox One), and must be signed in with the Microsoft account associated with the email address that you provide.įor more info, see Private audience. The Private audience option can only be used when you have not already published your app to a public audience. This is the only method that lets you distribute your app to testers while completely preventing anyone else from seeing the app’s Store listing, even if they were able to type in its direct link. If you want to let testers use your app before it’s available to others, and make sure that no one else can see its listing, use the Private audience option under Visibility (on the Pricing and availability page of your submission).
#Starmancer beta testing update#
Your testers will get the update after it goes through the certification process, just like they got the original package, but no one else will be able to get it (unless you make additional changes, such as moving an app from Private audience to Public audience or changing the membership of groups who can get it).
You can give your testers an updated version of your app at any time by creating a new submission with new packages.Note that each add-on can only be purchased once per Microsoft account, so the same tester won't be able to test the add-on acquisition process more than one time.
#Starmancer beta testing free#
Since you probably don’t want to charge them money for an add-on, you can generate promotional codes and distribute them to your testers to let them get the add-on for free, or you can set the price for the add-on to Free during testing (then before you make the app available to other customers, create a new submission for the add-on to change its price). You can include add-ons when you distribute your app to testers.You can review analytic reports for your app, including usage and health reports and any ratings or reviews left by your testers.Consider providing a link that lets your testers easily give feedback via email (or via Feedback Hub, if confidentiality is not a concern). You will need to determine how you’d like to collect feedback from your testers.Once they have downloaded the app, they can continue to use it, and they’ll get any updates that you subsequently publish. You can’t revoke access to the app after a tester has downloaded it.Whichever method you choose, here are some things to keep in mind as you beta test your app. Partner Center gives you several options to let testers try out your app before you offer it to the public.
You’ll then have a chance to fix those problems before you release the submission to the public, resulting in a more polished final product. Your testers may discover issues that you’ve overlooked, such as misspellings, confusing app flow, or errors that could cause the app to crash. No matter how carefully you test your app, there’s nothing like the real-world test of having other people use it.