reAJAX - FBK | SE - Fondazione Bruno Kessler

Step 3 Application execution tracing by starting and stopping the reAJAX tracer;
When inspector and mutator elements are selected, the next step consists in activating the
application execution instrumentation (it is highlighted by a reAJAX popup). Therefore, the next
application execution will be traced and during this execution the state of the application will be
recorded in a log file. To trace more executions into different log files it is sufficient to start and
stop the reAJAX tracing (respectively) before and after each application execution. Figure 3 shows
the activation of the reAJAX tracer for the Cart application.
Figure 4: Cart execution tracing
The execution tracing starts when the reAJAX tracer is activated and it stops when the same is
deactivated (by means of the reAJAX menu). Each execution trace is stored in a log file such as the
following (it is one execution of the Cart application):
ONLOAD:__:HTTP://LOCALHOST:8080/CART/:__:[
/HTML/BODY/DIV/DIV/UL[@ID='CONTENTS']=0 ;__;
/HTML/BODY/DIV/DIV/SPAN[@ID='TOTAL']=NOTEMPTYMATCH
]
CLICK:__:CHA001_REM:__:[
/HTML/BODY/DIV/DIV/UL[@ID='CONTENTS']=0 ;__;
/HTML/BODY/DIV/DIV/SPAN[@ID='TOTAL']=NOTEMPTYMATCH
]
ONUNLOAD:__:HTTP://LOCALHOST:8080/CART/:__:[
/HTML/BODY/DIV/DIV/UL[@ID='CONTENTS']=0 ;__;
/HTML/BODY/DIV/DIV/SPAN[@ID='TOTAL']=NOTEMPTYMATCH
]
Each row of the log file contains three types of information (separated from special characters
“:__:“ according to the following pattern:
- executed event (e.g., click of the rem button);
- id/name of the event or its Xpath address in the page (e.g., id of the activated button);
- state of the page according to the selected GUI inspectors (e.g., the list of items in the cart).