Software Testing For Wireless Mobile Computing

1

• Software Testing For Wireless Mobile Computing
• __________________________________________________
  _______________________
• By
• Michael Paltayan

2
Introduction

• 4GL wireless networks make it difficult to test
  applications for mobile technology. (PDAs,
  Notebooks, Phones, tablet PCs, etc)
• This article presents new approach, called
  Flying Emulator for testing mobile applications
  in different subnets within a LAN or WAN
• Key idea is to automate testing of applications
  designed for WLAN with subnets or LANs
• Why I chose this Article?

3
The Flying Emulator

• The key idea in this approach is to implement
  emulators as mobile agents that can travel from
  computer to computer under their own control.
• When an agent moves to another location, the
  agent transfers its state, as well as its code,
  to the destination.
• Carried software can continue its processing
  after arriving at the new host in the same way as
  it had been physically moved with target
  terminal.

4
(No Transcript)
5
The Flying Emulator

• This approach consists of three components
• A mobile-agent-based emulator that provides the
  target software with internal execution
  environment, also carries the software to
  specific access point host on remote networks on
  behalf of the terminal.
• Access point hosts (APHs) that are allocated to
  each network and enable the software carried by
  the emulator to connect with various services.
• Remote Control Server (RCS) which enables
  remotely displaying emulators GUI on the screen.

6
Mobile Termianl Emulation

• Each mobile agent based emulator can carry and
  test software designed to run on its target
  terminal.
• The current implementation of the approach is
  built on JAVA and provides mobile-agent-based
  emulators.

7
Emulation

• When emulator migrates between APHs, its target
  software is transformed into a bitstream along
  with states and codes then transformed to
  destination APH.
• The Destination APH retrieves the software and
  emulator from the bitstream.
• Developer can control the movement of the
  emulator interactively through the RCS.

8
(No Transcript)
9
Emulation

• When emulator migrates between APHs, its target
  software is transformed into a bitstream along
  with states and codes then transformed to
  destination APH.
• The Destination APH retrieves the software and
  emulator from the bitstream.
• Developer can control the movement of the
  emulator interactively through the RCS.

10
Software Testing And RCS

• Developers use RCS to manage APHs, monitoring
  their status and controlling execution of the
  code.

11
Conclusion

• This approach enables application-level software
  to be executed and tested through its current
  network as if the software were being moved and
  executed on that target device.
• Approach still has issues and needs further
  testing and implementation.

12
No Questions Right ?