Managing and Testing Director Projects
569
Testing often during development
Testing should be an integral part of your Director development process. You should test the
functionality of each small part of your movie as you add it rather than waiting until the movie’s
whole feature set is implemented.
When you build features that are interdependent, you should test each one before adding the
next. If you test this way, you’ll know that the most recently implemented feature is the most
likely source of the problem. If you wait to test one feature until after the next feature is
implemented and one of those features exhibits a problem, you have a more complex set of
possibilities to evaluate.
Save multiple versions of your movie as you progress. When difficulties arise, compare the current
version with the last saved version to help locate the source of the problem.
Testing on all target platforms
When you develop a Director movie, you should spend some time defining its audience. Part of
this process is deciding what the minimum system requirements should be for the computers used
by that audience.
You should determine the slowest processor speed you want your movie to play on and verify that
the performance of your movie is acceptable on a processor of that speed. You should also
determine if there is a range of configurations you have to support (such as Macintosh, Windows
NT, and Windows 2000) and test enough of them to ensure success. Be sure to include
parameters such as browser software, screen resolution, and available memory in your testing.
This approach can help you find problems that are specific to an operating system or
configuration, which are distinct from authoring errors.
Testing strategies
You can use the following strategies to test your movies effectively:
•
Be sure to use the Control > Preview in browser command. Testing in Director is different
from testing a Director movie (DCR) file. The Preview in Browser command demonstrates the
true behavior of the DCR file.
•
If you encounter a problem, try to isolate the problem in a new Director file that incorporates
only the problem feature or item. Make a list of the minimum steps that are required to
reproduce the problem in a new file. This process usually reveals the source of the problem in
your movie. It also reveals whether the problem is limited to one feature or if it is caused by the
interaction of two or more features in your movie.
•
Try to re-create the problem with different media. Sometimes the source of a problem is within
a specific media item used in your movie.
•
Try to re-create the problem on a different computer. This will help isolate problems with
hardware configuration or with the Director installation on a specific computer. If the problem
exists only when the movie is posted to a server, determine whether the problem exists on only
one server or all servers. Occasionally the server’s MIME types might need editing to include
the MIME types for Director. For more information, see Director TechNote 16509,
Configuring your server for Macromedia Shockwave Player, at www.macromedia.com/
support/flash/ts/documents/tn4151.html.
•
When you use Lingo, look for typing errors, missing punctuation, or inconsistent naming.
Содержание DIRECTOR MX-USING DIRECTOR MX
Страница 1: ...Using Director MX Macromedia Director MX...
Страница 12: ...Contents 12...
Страница 156: ...Chapter 4 156...
Страница 202: ...Chapter 6 202...
Страница 244: ...Chapter 7 244...
Страница 292: ...Chapter 10 292...
Страница 330: ...Chapter 12 330...
Страница 356: ...Chapter 13 356...
Страница 372: ...Chapter 14 372...
Страница 442: ...Chapter 16 442...
Страница 472: ...Chapter 18 472...
Страница 520: ...Chapter 19 520...
Страница 536: ...Chapter 20 536...
Страница 562: ...Chapter 23 562...
Страница 566: ...Chapter 24 566...
Страница 602: ...Chapter 27 602...