Beta testing is a great way to test your application before you finally submit your app for validation. By following a set process for beta testing, you can be sure that the next message you get from the validation team is Congratulations! Your app is published. Below is a checkpoint list that will help beta test your application effectively leaving no stone unturned.
The list has 7 items that you will need to scrub against. You can tick and cross against as you move through each item on this check list. Under each check point there are issues that have been usually encountered and the possible areas that need to be looked at have been mentioned in this guide. Also links to validation guidelines under each checkpoint which should provide more information, the validation codes like SEC, ILU along with this guide should help in identifying where your application was rejected in as well.
| Checkpoint | Pass | Fail | Comments |
| Security Check | |||
| Installation Check | |||
| Launch Check | |||
| App Check | |||
| Authorization check | |||
| Uninstall Check | |||
| Content Check | |||
Security Check
Run a virus scan on the MSI package, make sure that no high severity vulnerabilities are a part of the MSI. SEC01 – Virus and vulnerability scan.
SEC01 – Virus and vulnerability scan
SEC02 – Privacy opt-in or opt-out options
Installation Check
Once you have sent out the beta invite, the invitee will see the application under pending downloads in their AppUp client. Click on the Download button. – The installation must be silent; at no point during installation should the user be prompted for any input. Take a looks at this thread which lists with screenshots how to create a silent installer. http://appdeveloper.intel.com/en-us/node/733
– In some cases an error message is displayed “Oops! Something weird happened…..” during the installation process, this is usually a packaging issue. You can use a tool called ORCA to fix these issues. Below link with screenshots illustrates how you can use the tool. http://appdeveloper.intel.com/en-us/article/troubleshooting-validation-failures
Launch Check
The application should launch without any errors, if there are shortcuts from the desktop or any other location, check if the launches from these shortcuts are effective as well.
ILU03 – Application should launch on Netbook
App Check
App check needs to be run at 3 levels, user interface, content & OS compatibility. The validation guidelines are comprehensive and list out what items need to be checked against at each level.
User Interface
UIX01 – All menus, graphics icons and text must be easily readable by user
UIX02 – User interface consistency must be preserved across the application
Content
INC01 – Unauthorized use of Intel trademark and Brand
INC02 – Objectionable content
INC03 – Advertisements within application
OS Compatibility Please also ensure that the app is tested on all OS environment as indicated during app submission. So if you have indicated app supports Win XP & Win 7. Test on both environments.
Authorization Check
The SDK integration enables an ISV to sell the application per device. If I were to copy files of the app onto another netbook or any other device, the app should not run. You could test this by copying the files of the installed app onto another system and check if the app runs. If it does then there is an issue with the SDK integration.
Uninstall Check
After uninstalling completes, check if all shortcuts and files associated with app have been removed.
ILU02 – Application must uninstall cleanly
Content Check
– Check on your short and long description. Please ensure that there is sufficient content to ensure that consumer on the AppUp store gets a fair idea on the capabilities of the app. – Check on the Rating you are providing for app, if it is in adherence with the validation guidelines -Check for all content within the app as well, there should be no profanity, violation of copyright.
Content
DES01 – Content and description fields are error free and adhere to content submission and validation guidelines
DES02 – E-mail addresses and Support URLs are valid and function as appropriate mechanisms to get in contact with Developers
DES03 – Custom end user terms and conditions are compatible with program models and objectives
Image
IMG01 – Icons are appropriate and adhere to applicable program policies and guidelines
IMG02 – Screenshots are appropriate and adhere to applicable program policies and guidelines
Content Rating
RTG01 – Content rating provided for app matches content rating guidelines
Posted by ieetf2 









