SE401:Group32:May 20

May 20

◄ Main Page

HUI Analyzer built using .NET

Recording Actions

• For each GUI component on the screen of the mobile device, listeners are added for specific events.
• Once the events are fired an appropriate XML script line is generated.
• This is done first by the developer simulating actions which generates the Expected Test Sequences
• Then the user is asked to try the same task, which generates the the Actual Test Sequence.
• A comparison is made between these to evaluate the usability of the application.

HUI Analyzer Vs Hermes

• HUI Analyzer compares Expected Sequence XML against the Actual sequence XML as opposed to simulating the actions again. With Hermes we want to be able to simulate script actions rather than checking differences between XML schema's.
• HUI Analyzer was tested on an application that was made by the developers. Hermes needs to be generic to any application developed. This avoids the accusation of HARD-CODING the testing.

Advantages

• Structure of the XML is very concise due to the accurate mapping of actions from the components
• Actions are added in an efficient way. The top level form is retrieved first then an iteration through each of the components is done to add the action listeners for specific events.

Disadvantages

• Can only be developed for .NET applications running the Windows OS. While Java applications are far more popular and compatible on most mobile devices.
• Familiarity with the .NET platform is not as high as that with Java.

◄ Main Page