1 / 5

Addressing Device-Specific Failures in Mobile Software Applications

Device-specific failures pose significant challenges for mobile software applications, often causing them to work reliably on some devices but fail on others. Common issues include compatibility with different operating systems and display resolutions. With over 11,000 distinct devices downloaded, proper testing is critical but often expensive and time-consuming. This seminar explores practical testing strategies and the optimal selection of mobile devices to ensure applications perform correctly across the spectrum of devices. Insights will be drawn from recent research to inform effective testing methodologies.

torgny
Télécharger la présentation

Addressing Device-Specific Failures in Mobile Software Applications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Research seminarIntroduction Sergiy Vilkomir April 16, 2014 http://core.ecu.edu/STRG/

  2. Device-specific failures • Device-specific failures are very common for mobile software applications • An application works reliably on many smartphones and tablets, but does not work properly (i.e., fails) on some specific devices • Examples: • App normally works under some specific operating system but fails under the latest or older OS • Graphics created for high-resolution screens are not shown properly on the mobile devices with extra-high or low screen resolutions • Factors: OS, screen resolution, screen size, device type (smartphone or tablet), handset manufacturer, RAM, etc. April16, 2014

  3. Device-specific failures How many? There are many different mobile devices Sufficient testing is required on different mobile devices Such testing is expensive and time-consuming April16, 2014

  4. Android Fragmentation Visualized (July 2013) From OpenSignal, http://opensignal.com/reports/fragmentation-2013/ From OpenSignal: We have seen 11,868 distinct devices download our app in the past few months. In our report last year we saw 3,997 April16, 2014

  5. Research task Practical task • How to test? Where to take mobile devices for testing? Optimal selection of mobile devices for testing S. Vilkomir and B. Amstutz, "Using Combinatorial Approaches for Testing Mobile Applications", Proceedings of the IEEE Seventh International Conference on Software Testing, Verification and Validation Workshops (ICSTW 2014), March 31 - April 4, 2014, Cleveland, Ohio, USA, pp. 78-83. http://core.ecu.edu/STRG/publications/Vilkomir-IWCT-2014-Proceedings.pdf April16, 2014

More Related