MACROMEDIA FLEX 2-TESTING FLEX APPLICATIONS WITH MERCURY QUICKTEST PROFESSIONAL Manual de usuario descargar pdf (Pagina 10)

489 CHAPTER 23 Debugging and testing

Using this technique and the Flash log file can get you reasonably far, but to take your

game to a new level, you’ll want more advanced tooling.

23.1.6 FxSpy

FxSpy (a.k.a. Flex Spy) is an open source tool that allows you to inspect your compo-

nents and see what their properties and styles are set to, while allowing you to manip-

ulate many of these items (see figure 23.1).

This tool is particularly handy when you want to tinker with properties that affect the

visual aspects of the application. This can save you time compared to making changes

in the code and having to recompile constantly to test those changes.

You can download this free tool at http://code.google.com/p/fxspy/.

The tools mentioned so far cater to the front end, but monitoring the back end

also becomes vital when you need to know what’s going over the wire.

23.1.7 Monitoring network activity

One of the most challenging things you’ll encounter when developing Flex applica-

tions is trying to figure out why communications with a back-end data service (such as

a web service or remote object) doesn’t seem to be working. Yes, you can specify fault

handlers to handle exceptions, but that may not be enough.

Flex Builder has a built-in ability to monitor network activity. This is facilitated by

adding

<mx:TraceTarget/>

to your application, as shown in listing 23.5.

<?xml version="1.0" encoding="utf-8"?>

<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml">

<mx:TraceTarget/>

. . .

</mx:Application>

Listing 23.5 Using the TraceTarget component to monitor network activity

Figure 23.1 FxSpy allows you to

browse and inspect components and

their properties.

1 2 ... 5 6 7 8 9 10 11 12 13 14 15 ... 26 27

Sin comentarios

MACROMEDIA FLEX 2-TESTING FLEX APPLICATIONS WITH MERCURY QUICKTEST PROFESSIONAL Manual de usuario Pagina 10