Mobile Zone is brought to you in partnership with:

Jared is a highly regarded public speaker and software architect with more than sixteen years in the industry. Jared is currently employed as a Sr. Mobile Evangelist for Microsoft where he helps companies, individuals and startups build applications for Windows 8 and Windows Phone. In his career he’s developed a wide range of skills across several industries, including IP telephony, ruggedized mobile computing, rich clients and soft skills as an advisor and educator. Jared immensely enjoys helping people do amazing things with cutting-edge technologies. Jared is a DZone MVB and is not an employee of DZone and has posted 11 posts at DZone. You can read more from them at their website. View Full User Profile

How to Test Your Windows 8 App Before Submitting to the Store

10.27.2012
| 1756 views |
  • submit to reddit

It’s always a good idea to test your application before submitting it to the store. The Windows Application Certification Kit (WACK) tool can save you from failing the early automated tests.

The first thing you’ll want to do is uninstall any existing build of your application. This is important because the WACK tool may fail if a previous debug build is still installed on the system. To uninstall your app, find it on the Start experience, right-click and choose ‘Uninstall’.

image

Next, make sure to change the project build to ‘Release’ instead of ‘Debug’. This can be done from the Visual Studio toolbar.

image

Now, under the Debug menu, clean and then rebuild the solution.

image

After the build completes, right-click on the project in the Solution Explorer window and choose Store –> Create app packages…

image

When prompted if you want to build the app for the store, say no.

image

When the app packages are finished building you’ll be presented with the option to run the certification kit.

image

If this option isn’t available, double-check that your project was actually built as ‘Release’ and not ‘Debug’.

Before you launch the App Certification Kit, close down other programs and set aside about 5 minutes for it to run. As the screen reminds you, when you see your app appear on the screen do not interact with it.

When the tests are done, if all is well you’ll see a successful report like the one below.

image

Published at DZone with permission of Jared Bienz, author and DZone MVB. (source)

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)

Comments

Vikas Wing replied on Tue, 2012/10/30 - 4:26am


Hello,

Nice article simple and nicely explained. I will definately share this with my testing team.
Enjoyed a lot while reading this article. Can you please provide more inputs on how to make the apps more cleaner and with efficient code I mean avoid memory leaks and crashing.
Will definately look upto some more artcles written by you.

Once again thanks.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.