Top 30 Wireless Testing Interview Questions You Must Prepare 19.Mar.2024

sort out builds on basis of :

  • make (Brand) due to their specific key functionalities.
  • resolutions 128x128, 240x320, 176x220 (208), 320x240 or higher resolution.

The most common and important difficulties that should be overcome by testers is testing on multiple types of handsets and automation testing.

  1. Wired-side AP fingerprinting
  2. Wired side MAC prefix analysis
  3. Wireless-side warwalking
  4. Wireless-side client monitoring
  5. Wireless-side WLAN IDS 

  1. Should know the Functional units for new technology.
  2. Tester should know the latest Mobile technology knowledge.
  3. Should know about the Test Environment.
  4. Should able to configure and troubleshoot the device.
  5. Should able to follow the standards and verify the checklist.
  6. Should be innovative thinking and make Test scenario for the running the application.
  7. Should able to Test the full part of coverage.

There are testlabs to test the voice over wireless testing. Otherwise you can use two of ur test mobiles and can put any operators simcard just like ur own mobile and can test it. Most of the companies provide some operators simcards to test.

  • TLS: Transport Layer Security
  • TTLS: Tunneled Transport Layer Security

Basically Call module should be covered for wireless testing, after that all the applications should be tested how those applications behave when a call is received being in that application.

  • Check that the Wireless Network Adapter is on and verified by LED glow.
  • Check that the Wireless Network Adapter is suited for the different OS.
  • Check the Wireless Network Adapter is able to pass Installation Testing.
  • Check that the Wireless Network Adapter is able to configure.
  • Check the data flows(in/out) functions for the Wireless Network Adapter.
  • Check the flow rate of data and should not breakup.
  • Check the Time delay taken for every process.
  • Data Transmission should not be freeze at any situation.

Best way to test network apps to test connectivity.

  • WEP: Wired Equivalent Privacy
  • TKIP: Temporal Key Integrity Protocol

  • TestQuest and MTS are two mobile automation tools. 
  • TestQuest is used to test wireless handsets.
  • MTS is a scalable automated application testing tool for Windows Mobile 5.@
  • There are also ways to produce automated tests on various mobile browsers with wireless handset simulation tools such as OpenWave.

If application is clent server - you need wifi (if Device support) and GPRS (device should be enbled and GPRS Access Points should be configured according to requirement).

For CDMA there is no need to set access point. And devices should be according to service operators.

There are wireless simulators to which you connect ur mobile and test. Simulator acts like wireless tower in real network

Wireless test executive is an easy-to-use graphic interface for controlling test selection, execution, and runtime options. Tests are displayed in a hierarchical list where each entry represents one test.Test Objects are a key component of the Test Executive Architecture.The Test Objects operate with the Test Executive through a standard interface that is provided by the Test Executive DLL.

Its giving enough load to the process. Suppose a user using the wireles interface for communication, which it is many-many communicator.

  • Check the interface behaves once another communicator is in request(make a call to a interface, which is busy in communcating with another interface).
  • Check the Wireless interface performance on invoking the another application( Reminder, Alaram invoked on call, Message received, low battery ect..)

Mobile Tester Should know about the

  1. Mobile Technology
  2. Development Technology
  3. Mobile Platform(OS)
  4. Knowledge on Device Supporting Tools.
  5. Mobile Protocols

Testers must be able to think lot of scenarios relating to calls, for example when a call comes and at the same time alarm rings how the system behaves or say when the mobile is busy with a call at that time one more call comes, how the system behaves etc. There can be a lot of scenarios like this.

2G and 3 G is a family of standards for mobile telecommunications defined by the International Telecommunication Union,which includes GSM EDGE, UMTS, and CDMA2000 as well as DECT and WiMAX. Services include wide-area wireless voice telephone, video calls, and wireless data, all in a mobile environment.

2G Stands for second generation mobile telephony standards, where 3G defined the third generation mobile telephony standards to facilitate growth, increase bandwidth, and support more diverse applications.For example, GSM (the current most popular cellular phone standard) could deliver not only voice, but also circuit-switched data at download rates up to 14.4 kbps. But to support mobile multimedia applications, 3G had to deliver packet-switched data with better spectral efficiency, at far greater bandwidths.

Actually the same TCP/IP concepts go in mobile apps also, but when it comes down to browsing apps/downloading apps, it is generally done via WAP gateway (Not WAP Server which generally people confuse with). WAP is a standard defined to serve as a common platform as we cannot directly hook on from normal TCP/IP network to a mobile network. But it is definitely possible to call, SMS, sending mail from any browser to a mobile device, and vice versa. 

we must consider the following aspect:

  1. Unauthorised access/Guest access
  2. Firewalls
  3. Concurrent connections

As a tester you need to make yourself more aware of the automation services/tools to run tests on mobiles handsets.

A smart mobile simulation program is hooked on to the actual (physical) handset at 'device anywhere' site. Companies pay per use or a monthly fee. The UI is like that of a mobile simulator, but the tests run on a phone.

The beauty lies in the variety of mobile phones they offer. I'm no way connected to device anywhere company but I'm a customer who is benefiting from their service.

The technology used will determine the type of test environment and tools that we need.

  • WAP.
  • Bluetooth, etc..
  • XML, WML.
  • Security protocols.

Tools: 

  • WAP Simulators by hardware vendor: Nokia, Ericsson, Motorola.
  • Capture/Playback - such as TestPartner by Compuware.
  • Performance Testing - such as QA Load Compuware.

White box testing provides the testers with complete knowledge of the infrastructure to be tested, often including network diagrams, source code, and IP addressing information. 

It can be performed to validate whether code implementation follows intended design, to validate implemented security functionality, and to uncover exploitable vulnerabilities.

Wireless (OTA/WiFi/BT) wired: using Data Cable, PC Suit.

Levels of testing:

  1. Usability Testing
  2. Network Performance Testing
  3. Server-Side Testing
  4. Automating Unit Testing

Wireless testing you can classify into 3 types:

  1. Platform testing: To do this testing, tester should have programming knowledge of cpp, java
  2. Protocol testing: To do this, tester should have a knowledge of Networking concepts like, making lan connections, read protocol logs in wireshark, ethereal (both are protocol logging tools), all protocol definitions TCP/IP, UDP.. etc etc
  3. Application testing: Testing mobile application is almost testing windows applications but bit different. Some basic networking concepts are must. If the application is to be testing in JUnit, then Java knowledge is a must.

RACAL is Base station emulator, using this we can test all mobile use cases in the controlled environment.

procedure of battery testing :

battery backup test for idle mode:

  • fully charge the battery
  • make sure no calls should be made on DuT
  • start timer when fully charget
  • wait until the battery drain out fully 

battery backup test for dedicated mode:

  • again fully charge the battery 
  • make a call to a test phone from DuT
  • start timer when call is connected
  • wait untill the battery is fully drain out 
  • match all the readings from user manual and check the battery leakage

Call modules should be tested for wireless testing, after that all the applications should be tested to check how those applications behave when a call is received in that application.

The quality of a wireless signal is measured with respect to thresholds of:

  • BER (Bit Error Rate) which should be < 10^-6 or BLER (Block Error Rate)
  • RSSI (Received Signal Strength Indicator)
  • SWR (Standing Wave Ratio)
  • SNR (Signal-to-Noise Ratio) which is P/N
  • SINR (Signal to Interferance and Noise Ratio) or P/(N+I)
  • SINADR (Signal-to-Interference plus Noise And Distortion Ratio).. and many more.

These parameters are evaluated based on the technology or standard in use. For example, in WiFI or 802.11, the RSSI is used as the link quality parameter to be used. However, all of the above contribute in one way or the other to the quality of the wireless link as noise, interference, environmental characteristics, power, frequency used... contribute to the loss or gain in the link's quality.