MeeGo Mobile platform Architecture

MeeGo Mobile platform Architecture

MeeGo Architecture

MeeGo Software Architecture Overview

The MeeGo platform has been carefully created to provide the components necessary for the best device user experience. As shown in the MeeGo Reference Architecture Overview diagram below, the MeeGo architecture is divided into three layers:

* The MeeGo OS Base layer contains the Linux kernel and core services along with the Hardware Adaptation Software required to adapt MeeGo to support various hardware architectures.
* The MeeGo OS Middleware layer provides a hardware and usage model independent API for building both native applications and web run time applications.
* The MeeGo User Experience layer provides reference user experiences for multiple platform segments; the initial MeeGo release will contain reference user experiences for handhelds and netbooks and additional platform segments will be supported over time.

MeeGo OS Base
Hardware Adaptation Software

There are multiple software components that a hardware vendor must provide for MeeGo to run successfully on their platform architecture, including platform kernel drivers, core architecture additions, kernel configuration, X software additions and configuration, modem support, and hardware specific media components. You can learn more about the hardware enabling process here. These specific software components are called the hardware adaptation software and are detailed below.
Kernel

The kernel is the heart of Linux, and acts as the bridge between applications and the actual data processing done at the hardware level. There are three general categories of additions that MeeGo requires for each supported hardware platform.

* Kernel Drivers: This is the set of software drivers needed to interact with the hardware device. Some examples are drivers for wireless, camera, USB, 3G, Bluetooth, and touchscreen.
* Core Architecture Additions: These are additional packages added to the Kernel to enable certain architecture features. An example would be firmware.
* Kernel Configuration File: This file determines the options needed to get the hardware device working properly. This configuration file is in addition to the general kernel configuration file that is provided within MeeGo, and is specific to the hardware vendor platform. This file details the specific configurations required for the specific device. Examples include device architecture, processor type, device driver configuration options, network support, and kernel debugging options.

X Window System

The X Window System (also known as X11 or simply X) provides the graphical interface and the basic framework for building this interface. There are two general categories of X additions that MeeGo requires for each supported hardware platform.

* Core Architecture Additions: These are additional packages to be added to X to enable certain architecture features. Examples include the graphics controller, display, and acceleration.
* X Configuration file: This file provides configuration and runtime parameters for initializing the X windows system. If there are hardware-specific configuration options required for the X windows system, these details must be added and supplied to the specific hardware platform X configuration file. Examples include the display output and resolution.

Miscellaneous

* Bootloader: The bootloader program's only job is to perform the necessary initializations to prepare the hardware for the operating system, and it contains board- and/or processor-specific code. The bootloader provides the necessary glue between the firmware and the kernel.
* Image Device Format Tool: This provides the details on how to write an image for a specific device. It is a tool used to create a device executable in the appropriate device format.
* Modem Support: telephony framework plug-ins for specific cellular modems
* Hardware-Specific Media Codecs: Codecs that are hardware specific (such as codecs with hardware assist/offload)

MeeGo Kernel

MeeGo uses a Linux kernel from kernel.org, with architecture specific configuration and patches (as needed). Drivers are provided for each supported platform.

Qt

Qt provides application developers with the functionality to build applications with state-of-the-art graphical user interfaces. Qt is fully object-oriented, easily extensible, and allows true component programming.

Component(s): QtGui, QtCore, QtDBus, QtMultimedia, QtNetwork, QtOpenGL, QtScript, QtSql, QtSvg, QtWebKit, QtXml, Qt3Support, QtDeclarative, QtHelp, QtScriptTools, QtTest, QtXmlPattern

Mobile Testing Interview Questions and Answers

Mobile Testing Interview Questions and Answers
Q. What is the difference between TDMA and FDMA?
TDMA is Time Division Multiple Access. In TDMA technology each user in the channel owns the channel bandwidth for some time in a round robin fashion. All GSM handsets use this technology.
FDMA is Frequency Division Multiple Access. In FDMA many users are allowed to transmit through the same channel at the same time. So each user at any particular time uses part of the bandwidth. CDMA handsets use this technology.
Q. What will be the common test case for SMS and Mp3 player applications?
There are a few common test cases for SMS and MP player:
TC-I:
1. For SMS: For entering text for SMS, you need to open Text editor.
2. For MP3: For entering/editing play list names, text editor should be opened.
TC-II:
1. For SMS: It uses UDP protocol
2. For MP3: Audio streaming also uses UDP protocol
So, the test cases written for text editor can be used for both applications.
Q. How and from where to download JUnit and what is its use?
Generally, there are 3 levels in structure:
Base level - Platform code will be there.
Service level - modules and their engines communication code.
Application level - GUI, user interacting applications.
JUnit will be used for Unit testing to test at service level.
Q. What are value added Services in Mobile Application Testing?
Value added services refer tpo extra services like toll free number, getting messages for new offers in recharging sim card, getting messages for downloading new ringtones, caller tunes etc.
Q. How to test the MMS application?
MMS stands for Multimedia Messaging Services
Pre-requisites before start testing an application MMS.
# ME should have a valid GPRS enabled SIM.
# Profile should be added manually or sometimes operator will send all the settings as message, saving these settings profile will be added. If you are adding profile manually MMS server details of an operator should be provided. These are:
Data(bearer): GPRS
APN:
User:
Password:
Auth:
IP: parameters are is compulsory.
Testing MMS can have several cases, some of them are mentioned below:
Sending, Receiving (text, image, audio, video)
Sending with specific to GPRS classes.
Checking received MMS(Audio,video clarity)
Q. What could be the Possible Test Cases to test the Functionality and Performance of a Mobile Client Application?
There can be a lot of scenarios for mobile client applications. Lets discuss a few of them below
- All mobile features: Incoming call, outgoing call, Incoming SMS, outgoing SMS, phone directory, call history, redial facility, all called numbers, all received numbers, storage capacity of calls, SMSs, audio, video storage, display.
- Multimedia services: Radio, audio, video capabilities, MMS etc.
- Internet: Connectivity, browser display, downloads, uploads etc.
- Utility: Games, reminders, calendars, clock etc.
- Performance: Fill all the hard-disk with say video files. Check how much time it takes to open the files and is there any impact on the way the video is played. Is it slow etc.
These are only few of the many scenarios that can be derived for the mobile client.
Q. How we test battery back up time using load testing especially for mobile testing ?
Below are given a few scenarios to test the mobile battery backup:
1. Charge the mobile up to maximum capacity.
2. Call to a number and continuously use it until the battery fully drained out. Measure the time of life for one full cycle.
3. Charge the battery up to 20% of it's capacity use it until the battery is fully drained out.
4. Charge the battery up to 40% of it's capacity use it until the battery is fully drained out.
5. Similarly check for 60%,80% of battery charge capacities and measure the battery backup time.
6. Verify the battery life by continuously sending SMSs.
7.Verify the (GUI) power indicating lines or levels correctly displaying or not with respect to actually charged battery level.
8.test the phone in non signal coverage area and measure the battery stand by time. (In non signal coverage area cell continuously searches for signals due to this the power continuously dissipated as radio frequency signals and battery drained very soon)
Q. What is the difference between mobile testing, mobile application testing?
Mobile Testing means the complete testing of mobile - system level + Application level
Generally there are 3 catgories:
1. Mobile Protocol stack testing. (using network simulators)
few examples are below:
* Stack supports 4 bands EGSM,PGSM,GSM-850,DCS.Mobile originating and mobile terminating call in all those bands.
*cell selection reselection
*cell bar
*All types of handover
*frequency hopping
*Coding schemes etc
2. Multimedia testing
* Midi polyphonic tones ringer and player
* MP3 as ringer and player &other supported formats
* Camera
* Video Conferencing etc
3. Feature testing
*Phonebook
*SMS
*Supplementary calls
*Security
*Calculator
*Gaming
*Fast dialing etc
Mobile Application testing deals with only the features and multimedia part. But Mobile testing deals with all three categories above.
Q. What is the advantage of symbian OS devices comparing with j2me and Brew OS devices?
- Symbian is the latest OS where as j2me and Brew OSs are old ones.
- Symbian OS has SIS file format where as j2me has JAR file format which means this is a third party software and anybody can develop softwares in this OS.
- Symbian is a fast browsing and a fast operating system. j2me is not as fast.
- Symbian OS provide touchscreen phones such as UIQ phones. No such facility on j2me.
- Symbain OS has superior hardware access to the phone compared to j2me and Brew OS
- Symbian OS offers rich UI.
Q. What are the modes of downloading content on mobile from server?
There are many techniques to download a content e.g. downloading, progressive downloading, streaming etc.
1. Downloading: Normal download and can be saved in the local machine, once saved user can play or do operation whatever he likes.
2. Progressing downloading: Whenever user selects a content it starts buffering and the same will be continued till the file ends playing. The content will be played once the buffer is finished. This could be even a min (e.g. if the buffer is completed for 1 sec the content will be played for one second) 3. Streaming: When user selects a content to download, buffering takes place and once the buffer is over content will be played. Until then player does not get initiated. And user can save, play again or whatever the operation he requires.
Q. What is streaming?
Streaming is the process of downloading a content from the server. There are many techniques to download a content e.g. downloading, progressive downloading, streaming etc.
Downloading: Normal download and can be saved in the local machine, once saved user can play or do operation whatever he likes.
Progressing downloading: Whenever user selects a content it starts buffering and the same will be continued till the file ends playing. The content will be played once the buffer is finished. This could be even a min (e.g. if the buffer is completed for 1 sec the content will be played for one second) Streaming: When user selects a content to download, buffering takes place and once the buffer is over content will be played. Until then player does not get initiated. And user can save, play again or whatever the operation he requires.
Q. How can smoke testing be applied to mobile testing?
Smoke testing can be done on a Mobile once the latest build has been released to the testing team. Smoke test or build verification is nothing but just the basic functionality check for all the applications, test scope parameters that are involved in mobile application testing, testing very basic and important features of the mobile and also testing the showstopper issues at a higher priority level.
Q. Is there any automation tool for mobile application testing ?
TestQuest is one of the best tools to automate mobile applications
Fitnesse tool can also be used to automate mobile applications.