User Guide

51
CHAPTER 7
Testing Content
Anyone can make mistakes while developing content, and it’s a good idea to test your
Macromedia Flash content frequently as you progress. Consider asking someone who is not
familiar with your application to look at it and provide feedback.
Testing considerations
Test your Macromedia Flash Lite 1.1 SWF content frequently on actual mobile phones. This step
may seem obvious, but it is often overlooked. It is especially important when you develop Flash
Lite 1.1 SWF files for mobile phones. No matter how much phone emulation you do, the final
delivery remains the most important part of the development cycle. Emulation is helpful for
much of the testing, but it is no substitute for testing on actual mobile phones.
You provide the most benefit for users by delivering a well-designed UI. If the application is slow,
difficult to use, or not viewable, your development effort is wasted.
You should use the following methods to test the Flash Lite content you develop for mobile
phones:
• The Flash Player Test Movie command (Control > Test Movie)
• Flash Player on the manufacturer’s phone
The Macromedia Flash MX Professional 2004 Test Movie command recognizes and plays Flash
Lite SWF files. When you select Control > Test Movie or Control > Test Scene, new information,
warnings, and error messages specifically related to Flash Lite applications are displayed in a
separate Output panel.
Whenever an unknown tag is encountered, warning messages are displayed so that you can
modify the content appropriately. Not all invalid Flash content is flagged as an error (for example,
invalid ActionScript and invalid key input).
For a detailed explanation of all messages related to Flash Lite 1.1, see Appendix C, “Warning and
Error Messages” . This appendix lists all of the warning and error messages that you might see
when creating Flash Lite 1.1 SWF files for mobile phones.