User interface and minimal functionality as per requirement.

I think one can give various answers depending on the 
requirement of the testing being done:

Some of the basic mobile testing header level scenarios are:

1) Battery charging scenarios
   a) Fully charging and launching the application
   b) operating mobile with charger on

2) Launch of application: Power on/off and Stand-by modes, 
if any

3) Basic Menu functionality checks:

    EX: a) Messages
              i) Inbox
             ii) Outbox...

        b) Camera
        c) Mail

4) Mobile operation: With and without SIM card

and so on...hope one gets the idea..

Cheers,
sb

Mobile testing for an application has following parameters
to Consider.

 1>Is there any prerequisite for our application to run.

 2>Installing an application on Device or external memory
card makes a difference or not?.The functionality of the
application on the mobile should remain the same.

 3>Have many applications running at the same time and then
check the performance of the application.

 4>Opening the application from a shortcut or from running
programms should open up fine.

 5>Check the application UI w.r.t native phone U.I

 6>The application should not interfere in phones basic
functionality which can disturb the user.

 7>Mobile tetsing is done keeping User's expectations in
mind to make it as user freindly as possible.

 8>The terms and captions used in the Application should be
self explanatory as far as possbile .

 9>There should be a "HELP" file provided to a user along
with the application to use on the mobile.

 10>Use your intelligence and smartness to figure out
different possible scenarios that may Crash the application
running on the mobile phone.

     There can be many such points please add If you have one.

TDMA is nothing but Time division multiple access. In this 
each user in the channel owns the channel bandwidth for 
some time in a round robin fashion.All GSM handsets use 
this technology.
FDMA means Frequency division multiple access. In this many 
users are allowed to transmit thru the same channel at the 
same time. They use part of the Bandwidth. CDMA handsets 
use this technology.

what fields you want?

Assained To:to whom you r reporting the bug.
project id:
project name:
defect id:
defect name:
defect description:
Seviority:
Priority:
Status:
Reproducable or not:
Summary:
Comments:

it depends on the company profile.

bud id,
source
moudle name
tester name
date
time
supported docs
dept
snapshot
proirity
seviority
type
etc.....

There might be many common test cases: Here are 2
I)
1. For SMS: It uses UDP protocol
2. for MP3: Audio streaming also uses UDP protocol

II)
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.
So, the test cases written for text editor can be used for 
both applications.

You can easily search in google and it used for performance 
testing.

Generally, there will be 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.

hello,

Marquis Technologies (navi mumbai) is starting a mobile 
handset testing institute shortly in November.
If intereste plz contact 
Marquis Technologies
Unit # 304, Building #2, Sector 3,MBP, Mahape,Navi Mumbai
Ph: 022 27781406

Regards
Marquis Technologies

testing the software/application repeatedly within a certain
period of time continuously with adding some extra
feature/new functionality  into it and compare it with the
existing one.

increamental testing is a way of integration testing in 
which first you test each module of the software 
indiviually then continue testing by adding another module 
to it then another.
Its proper definition is "A integration testing strategy in 
which you test subsystems in isolation, and then continue 
testing as you integrate more and more subsystems".

Advantages of increamental testing:-
when you find a problem, you can find the defect more 
easily because you have a better idea in which subsystem to 
look

there are two types of increamental testing:-

1.Vertical increamental testing
under this there are two testing strategies

i)Bottom-up testing
In this you start by testing the very lowest levels of the 
software using drivers, and then work upwards, as you 
integrate successive layers

ii)Top-down testing
you start by testing only the user interface, with the 
underlying functionality simulated by stubs, then you work 
downwards, integrating lower and lower layers

funtional testing means testing the funtionality of an 
application.
Gui means look and feel testing of the application.

for more info u can mail me to





ajay.thomala@gamil.com

FUNCTIONAL TESTING
--------------------
Functional testing means testing the application from login
to logout. i.es end to end testing

Functionality tests verify that the Product under test
complies with the working requirements laid down by the
client / customer.

Functionality testing is a 3 stage process that helps in
improving the quality of the product. The 3 stages being the
UNIT, INTEGRATION and the SYSTEM TEST phases

GUI TESTING
------------
In gui testing we can cover
1. look and feel
2. navigation checking
3. spell and grammer checking
4. text boxes, radio buttons, check boxes, drop down list....
5. alignment

hi yuva volume testing is one of the form of performance 
testing.

Performance testing includes 1.Load testing
                             2.Stress testing
                             3.Volume testing 

Volume testing: Testing the application buy putting more 
than the max load to c whether the application bears the 
given load or not i hope it is clear.

Stress Testing:Testing the application buy putting just the 
max load

Load testing:Testing the application buy putting just load 
as requested by the client

Hi friend 
Performance Testing :Here we are testing the performance of
the given software which may includes the size of the
software when installed, the amount of main memory and/ or
secondary storage it requires and the demands made of the
operating system when running within normal limits or the
response time. 

Definition: 
To determine whether the program meets its performance
requirements.
The IEEE standard defines performance testing as testing
concluded to evaluate the compliance of a system or
component with specified performance requirements.
Many programs have specific performance efficiency objectives.
Performance test focuses on performance parameters such as :-
-	Transaction response time.
-	Throughput etc.
e.g.:- in database system the response time relates is the
time to obtain report after checking in a specific button.


The time related features within the performance testing are:
Response time 
Throughput (Slide time delay)

Performances Testing includes 
1.Load testing
2.Stress testing

Load testing:Load testing is performed to test 
How much load a system can withstand?
How system performs as load increases i.e. its response time
throughout system crashes.

Stress Testing :Stress testing is performed to test 
Stress testing is subjecting a system to an unreasonable
load while denying it the resources (e.g. RAM, Disc, CPU,
network, bandwidth, etc) needed to process that load.
The idea is to stress a system to the breaking point in
order to find bugs that will make that break potentially
harmful.
The system is not expected to process the overload without
adequate resource but to behave (e.g. fail) in a decent
manner (e.g. not corrupting or losing data).
Bugs & failures modes discovered under stress testing may or
may not be repaired depending on the application, the
failure mode, consequences, etc. The load (incoming
transaction stream) in stress testing is often deliberately
distorted so as to face the system into resource depletion.

VOLUME TESTING : To determine whether the program can handle
the required volume of data or not.

Build can be Taken in Many ways,
1 way is by using the Ant Script Testers can build the WAR 
File. once build is done war file will be created in the 
Dist Folder...directly by taking the war file Deploy it in 
the Tomcat Server and Run the Application.