Posts

Bandwidth Throttle : a new way to simulate various network speed for Client-Server apps

Image
Bandwidth throttling  is the intentional slowing of Internet service by an Internet service provider. It is a reactive measure employed in communication networks in an apparent attempt to regulate network traffic and minimize  bandwidth  congestion. Now a days releasing the client-server application to the market without testing it in all  possible network speeds such as Edge/2G/3G/4G/LTE various Wi-fi speeds, tethering etc is very dangerous. This is highly risk prone areas for the client-server apps. Normally the companies would be having high speed internet/4G  connections and the QA Team forgets about the normal end user cases such as  network  disturbances, low bandwidth, repeated disconnection etc... Then what would be the solution for this? How the QA should identify this in early stage? The solution found by moderntester is Bandwidth  throttling  using proxy tools! Charles can be used to adjust the bandwidth...

NETWORK CONDITIONS AN IMPORTANT AREA TO TEST : MOBILE APPs

Imagine if your bank’s website were to display the following disclaimer on its homepage: “We do not guarantee the security of your personal data or your account information while transacting on our net-banking portal”. Will you still use it? Almost certainly not! There are four things to consider in this area: Support for different network channels:  Mobile devices can communicate with the network on one or more channels such as SMS, USSD, WiFi, GPRS (2G/3G/4G), WAP, etc. Certain functions in your application may not perform well (or at all) on certain channels and protocols. If you wish to support only the high capacity channels such as WiFi, or 3G/4G/LTE, you will risk shutting out the vast majority of low-end devices which may not support these radios. On the other hand if you do not specify which are the required (or recommended) channels for your application, it may result in the users inadvertently trying your application’s high-bandwidth features on a low-bandwid...

Testing CPU and Memory usage of Mobile Apps

  When an application is developed to run on a particular software platform such as J2ME, Android etc. it can in theory be installed and run on any device that supports that platform. However for any given platform, the supported devices could have a very wide range of capabilities in terms of CPU speed and available memory. For example a J2ME application can be theoretically run on a low end feature phone such as the Nokia 112 with a sub 250 MHz CPU and 16 MB of internal RAM as well as a higher end Nokia ASHA 300 series phone with 1 GHZ+ CPU and 128 MB internal RAM. However if the app has been designed to require a certain minimum CPU power and memory, it will in practice, fail on the Nokia 112 phone. If your application makes extensive use of arithmetic and logic operations such as those involved in streaming and decompression of audio and video and in rich animations, or it lets the user view and manipulate large sets of information or images, you should specify minimum CPU an...

Software Product

Image
Normally, we are getting an answer saying that the Software Product is nothing but a computer program that runs in a platform and executes the intended function. But as per moderntesters, software product is not only an app/software program but it is a set of Software Program, data associated with it, documentation and procedures. These altogether forms a Software Product. What is Software Program? It is nothing but the actual code with which the functionality is implemented and compiled for the specific platforms. E.g, Apps for iOS, Android, windows etc… The Data in the software product is nothing but the piece of data provided with software in-order to operate it. E.g, the licence keys provided with software. Now, documentation is the help/guide that demonstrates about the usage of the software/licence stuffs etc. Procedure clearly explains the set of actions/steps that should be followed to work properly with the targeted software.