Subscribe by Email


Showing posts with label Calls. Show all posts
Showing posts with label Calls. Show all posts

Thursday, April 12, 2012

How is testing done on different smart phones?

The word smart phone is all around us these days! Smart phones are on the verge of becoming the devices with the highest demand.

But what it is that makes a smart phone quite different from an ordinary feature both in performance and appearance? What is its smartness quotient?

To put it simple, we can say that:

- A smart phone apart from just making and receiving calls, grants one extravagant usability by means of many other features like listen to songs, send and receive e mails and edit the documents and so on.

- A smart phone has been made by putting together the features of both the mobile phones and PDAs (personal digital assistance).

- Features of cell phones like making calls and sending messages and PDAs features like organizer, calendar, alarm clock, portable media player etc are all incorporated in to a single device now popularly known as the “smart phone”.

- The smart phones can even be synced with one’s computer system.

- Eventually the smart phones achieved the capabilities like greater and better connectivity, web browsing, using third party applications and so on.

- Other advanced features include:
1. Pocket video Camera
2. Portable media players
3. Compact digital cameras
4. GPS navigation units

- The recent smart phones have web browsers pre- installed in them so as to facilitate the web browsing and accessing other web applications.

- The super a moled screens are now used instead of the earlier LCD displays.

- These smart phones very well support the standard web pages in their original form rather than optimizing them to be viewed through a phone like old feature phones.

How is testing on smart phones done?


- Smart phones also undergo rigorous testing to ensure that they are up to the standards and specifications.

- One way is to check the smart phone against a list of key features that must be in a cell phone for it to be a smart phone:

1. The Operating System

- A smart phone is always operated via an operating system rather than a proprietary firm ware as in the case of ordinary feature phones.

- Many of the smart phones make use of the following operating systems like iOS from Apple, Android from Google, Microsoft windows phones, Symbian from nokia, RIMS’s blackberry OS, Embedded Linux like MeeGo and Maemo etc.

- The above mentioned operating systems can be installed on different models.

- One is able to run third party applications on a smart phone only because the operating system of the smart phone is capable of integrating with the hardware of the phone.

- Likewise it also gains a third party support for the better functioning of its features.

2. Applications
- Even the ordinary feature phones include some sort of applications like address book, contact manager etc, but a smart phone serves even more.

- It includes applications for viewing and editing the Microsoft documents, download third party applications that serve other purposes.

3. Web access
- They have the capability of accessing the internet at high speeds via the advanced technologies of 3G and 4G and of course Wi- Fi!

4. Qwerty keypad
- Smart phone does includes qwerty key pad unlike the keypad of ordinary feature phones which have alphabetical order on top of a numeric keypad.

- It can be made available either through hardware or via the touch screens.

- Smart phones come in a whole lot of variety, in this case the performance and features of the models widely differ.

A smart phone is tested by testing its:

1. Usability: It involves the evaluation of the:
a) Menu navigation
b) Durability
c) Ease of use
d) Key pad layout
e) Software design
f) Screen resolution
g) Ergonomics

2. Call Quality: This involves the evaluation of the:
a) Ease of making and receiving calls
b) Managing contacts
c) Sound quality
d) Clarity of the reception
e) Messaging

3. Battery life: This involves the evaluation of the:
a) Talk time
b) Mp3 playback time


Monday, November 29, 2010

Step 4 To test API : Call Sequencing, Step 5 To Test API : Observe the output

Step 4: Call Sequencing
When combinations of possible arguments to each individual call are unmanageable, the number of possible call sequences is infinite. Parameter selection and combination issues further complicate the problem call-sequencing problem. Faults caused by improper call sequences tend to give rise to some of the most dangerous problems in software. Most security vulnerabilities are caused by the execution of some such seemingly improbable sequences.

Step 5: Observe the output
The outcome of an execution of an API depends upon the behavior of that API, the test condition and the environment. The outcome of an API can be at different ways i.e. some could generally return certain data or status but for some of the APIs. It might not return or shall be just waiting for a period of time, triggering another event, modifying certain resource and so on.

The tester should be aware of the output that needs to be expected for the API under test. The outputs returned for various input values like valid/invalid, boundary values etc needs to be observed and analyzed to validate if they are as per the functionality. All the error codes returned and exceptions returned for all the input combinations should be evaluated.


Wednesday, November 24, 2010

How can the testing of API calls be done?

Testing of API calls can be done in isolation or in sequence to vary the order in which the functionality is exercised and to make the API produce some useful results from these tests. Designing tests is essentially designing sequences of API calls that have a potential of satisfying the test objectives.This in turn boils down to designing each call with specific parameters and to building a mechanism for handling and evaluating return values.
Designing of test cases depends on the following criteria:
- What value should a parameter take?
- What values together make sense?
- What combination of parameters will make APIs work in a desired manner?
- What combination will cause a failure, a bad return value, or an anomaly in the operating environment?
- Which sequences are the best candidates for selection?

Some of the interesting problems for testers are:
- Ensuring that the test harness varies parameters of the API calls in ways that verify functionality and expose failures. This includes assigning common parameter values as well as exploring boundary conditions.
- Generating interesting parameter value combinations for calls with two or more parameters.
- Determining the content under which an API call is made. This might include setting external environment conditions like files, peripheral devices and also the internal stored data that affect the API.
- Sequencing API calls to vary the order in which the functionality is exercised and to make the API produce useful results from successive calls.


Facebook activity