With frequent updates and releases, Google Play now requires all new apps to target a recent Android API level - set to API level 26 (Android 8.0 - Oreo) or higher. So how does updates like these impact your test coverage? Are you able to analyze these information and identify the impacted areas and devices that can help you optimize your device and test coverage? Find out the details about this in this blog: https://www.pcloudy.com/how-to-analyze-data-to-predict-your-optimum-device-test-coverage/?utm_source=linkedin&utm_medium=post&utm_content=68614421&utm_campaign=android_ios&gclid=EAIaIQobChMI-eDJ7-Tu3QIVRw4rCh1WyQ3yEAAYASAAEgLyRPD_BwE
For more details visit www.pcloudy.com
AndroidFragmentation.com – an open community project Joachim Ritter
This presentation is about an open community project called AndroidFragmentation.com which aims at becoming a central imformation hub for specific fragmentation related device information.
AndroidFragmentation.com – an open community project Joachim Ritter
This presentation is about an open community project called AndroidFragmentation.com which aims at becoming a central imformation hub for specific fragmentation related device information.
Walmart & IBM Revisit the Linear Road Benchmark- Roger Rea, IBMRedis Labs
The Linear Road benchmark was devised in 2004 to
compare Stream Data Management Systems. Walmart selected Linear Road to compare performance of streaming analytic
offerings. IBM implemented the benchmark application using Redis to maintain state, and IBM Streams to handle the
incoming events and queries. Walmart had to completely revamp the data drivers and test verification to take advantage
of multicore multithreaded servers available today. Tests were run on Microsoft Azure cloud to ensure fair comparison of
vendors. Redis and IBM Streams handled nearly 1 billion events in a 3 hour test on a single 16 core Azure node, and 3.8 billion
when scaled out to 4 nodes. Come learn about the application and near linear scalability of Redis and IBM Streams.
Presentation for technical decisions makers on what is in Windows Phone and what you do to implement. Gives some example code on how to get started with key features in Silverlight and XNA. Good starting point for helping you get started writing for Windows Phone 7.
I used this deck to give an overview on Android development for Android Development professional training in DyCode Edu.
More information on the training, please refer to http://edu.dycode.co.id
Embedded Fest 2019. Іван Пустовіт. From AOSP to Android powered deviceEmbeddedFest
На даний момент Android є найпопулярнішою ОС для мобільних пристроїв. Він працює на різних платформах з різною конфігурацією обладнання. Потрібно багато інженерних зусиль, щоб створити Android BSP, що повністю відповідає потребам кінцевого користувача.
Я розповім, як шматок скла та металу стає пристроєм, що працює на Android.
Я проведу вас основними фазами розробки компонентів Android, поясню різницю між Android та AOSP, і розповім про процес сертифікації Google.
Special thanks to Daniel Egan. This presentation provides an introduction to Windows Phone 7, helps developers decide which user controls (Pivot, Panorama), user interface concerns, and step to get your app in Marketplace.
Building a useful set of devices for testing apps requires significant knowledge of the Android ecosystem. Once assembled, the device matrix provides broad, efficient coverage with minimal investment.
ASE 2016 Taming Android Fragmentation: Characterizing and Detecting Compatibi...Lili Wei
The slides are used in ASE 2016 for presentation of paper Taming Android Fragmentation: Characterizing and Detecting Compatibility Issues for Android Apps
Xamarin Evolve 2014 - Designing Android UIs for the Ever Changing Device Land...mstonis
Android is everywhere. Developers can now build apps that run on phones, tablets, TVs, cars, wearables, and even appliances! While this provides a breadth of opportunity, it creates a big problem when designing apps that can run across all of these different device types. In this session, join Michael Stonis to talk about how to create and manage dynamic UIs for Xamarin Android apps that look and feel great across different screen sizes and form factors.
Presentation Video: http://youtu.be/2k2SMiH37eg
Get an overview of Qualcomm Technologies, Inc.'s power and performance profiling tools, and how these tools can help you create more efficient apps. Covered topics include using profiling tools to determine whether your app exhibits behavior that causes excessive power consumption, how to resolve the top five power-related problems and more.
Watch this presentation on YouTube: https://www.youtube.com/watch?v=9Uc0qpMzfw0
How to Test Computer Vision Apps like Google Lens and Google Photos.pdfpCloudy
Computer vision technology has made significant strides in recent years, powering innovative applications like Google Lens, CamScanner, Google Photos, etc
More Related Content
Similar to Optimizing device and test coverage webinar
Walmart & IBM Revisit the Linear Road Benchmark- Roger Rea, IBMRedis Labs
The Linear Road benchmark was devised in 2004 to
compare Stream Data Management Systems. Walmart selected Linear Road to compare performance of streaming analytic
offerings. IBM implemented the benchmark application using Redis to maintain state, and IBM Streams to handle the
incoming events and queries. Walmart had to completely revamp the data drivers and test verification to take advantage
of multicore multithreaded servers available today. Tests were run on Microsoft Azure cloud to ensure fair comparison of
vendors. Redis and IBM Streams handled nearly 1 billion events in a 3 hour test on a single 16 core Azure node, and 3.8 billion
when scaled out to 4 nodes. Come learn about the application and near linear scalability of Redis and IBM Streams.
Presentation for technical decisions makers on what is in Windows Phone and what you do to implement. Gives some example code on how to get started with key features in Silverlight and XNA. Good starting point for helping you get started writing for Windows Phone 7.
I used this deck to give an overview on Android development for Android Development professional training in DyCode Edu.
More information on the training, please refer to http://edu.dycode.co.id
Embedded Fest 2019. Іван Пустовіт. From AOSP to Android powered deviceEmbeddedFest
На даний момент Android є найпопулярнішою ОС для мобільних пристроїв. Він працює на різних платформах з різною конфігурацією обладнання. Потрібно багато інженерних зусиль, щоб створити Android BSP, що повністю відповідає потребам кінцевого користувача.
Я розповім, як шматок скла та металу стає пристроєм, що працює на Android.
Я проведу вас основними фазами розробки компонентів Android, поясню різницю між Android та AOSP, і розповім про процес сертифікації Google.
Special thanks to Daniel Egan. This presentation provides an introduction to Windows Phone 7, helps developers decide which user controls (Pivot, Panorama), user interface concerns, and step to get your app in Marketplace.
Building a useful set of devices for testing apps requires significant knowledge of the Android ecosystem. Once assembled, the device matrix provides broad, efficient coverage with minimal investment.
ASE 2016 Taming Android Fragmentation: Characterizing and Detecting Compatibi...Lili Wei
The slides are used in ASE 2016 for presentation of paper Taming Android Fragmentation: Characterizing and Detecting Compatibility Issues for Android Apps
Xamarin Evolve 2014 - Designing Android UIs for the Ever Changing Device Land...mstonis
Android is everywhere. Developers can now build apps that run on phones, tablets, TVs, cars, wearables, and even appliances! While this provides a breadth of opportunity, it creates a big problem when designing apps that can run across all of these different device types. In this session, join Michael Stonis to talk about how to create and manage dynamic UIs for Xamarin Android apps that look and feel great across different screen sizes and form factors.
Presentation Video: http://youtu.be/2k2SMiH37eg
Get an overview of Qualcomm Technologies, Inc.'s power and performance profiling tools, and how these tools can help you create more efficient apps. Covered topics include using profiling tools to determine whether your app exhibits behavior that causes excessive power consumption, how to resolve the top five power-related problems and more.
Watch this presentation on YouTube: https://www.youtube.com/watch?v=9Uc0qpMzfw0
How to Test Computer Vision Apps like Google Lens and Google Photos.pdfpCloudy
Computer vision technology has made significant strides in recent years, powering innovative applications like Google Lens, CamScanner, Google Photos, etc
Seamless Integration of Self-Healing Automation into CICD Pipelines.pdfpCloudy
we’ll explore how to integrate self-healing automation into your CI/CD pipelines for mobile app testing, with a specific focus on using pCloudy’s device farm service.
SSTS Inc. Selected For The HPE Digital Catalyst Program.pdfpCloudy
The focus of the program was to partner with startups that are working in the field of Artificial Intelligence (AI), DevSecOps, Cybersecurity, and Intelligent Edge.
Tips To Enhance Your Cross Browser Testing With Minimal Effort.pdfpCloudy
With millions of websites being developed every day, it becomes challenging to test them on different browsers. And more importantly not all of them survive.
4. The ever-growing versions of Android
Oreo moves up to 21.5 percent from 19.2 percent.
This along with a small drop in Marshmallow’s
numbers brings last year’s version of Android to
just 6.7 percent below Nougat.
5. Let’s do some math!
• 16 device display categories
• 20 different common resolutions
• 15 Android versions
• 400 Android device Manufacturers
• 4 Major cellular networks
• 16 x 20 x 15 x 400 x 4 = 768000 permutations
Is it feasible?
6. Devising the
right device
matrix
Based on
Market
Penetration
By using
Purchased
data
By using
Analytics
Based on
Device
Diversity
How do you find your right device coverage?
7. Selecting Devices based on Market
Penetration
Determine the set of devices with your target operating system that will have the highest
occurrence of accessing your application.
For Example-
>
What will you prioritize if you’ve more number of Samsung & Xiomi users than iPhone users?
9. Market Share Approach for Consumer Apps
Pros
You can typically gather
approximate market share
data and utilize it to prioritize
your test device list
You choose devices with the
highest market share and test
on as many as you have time
and resources for.
Cons
You could be missing a whole
class of devices that are less
popular but might hold a
significant portion of the
market.
You could be wasting
resources testing on two
devices that are very similar
Purchased Data
Analytics
Source:
10. Selecting Devices based on Device Diversity
Quad Core or above
CPU
RAM >=3 GB
Display >= 5“
Retina, Full-HD
display
Latest OS Version
Dual Core CPU
RAM <=1 GB
Screen size <= 5“
No Retina or Full HD
Display
OS less than 1 year
Single Core CPU
RAM up to 1GB
Display size <4”
Low screen resolution
Older OS
older browser
High End Devices Medium Range Devices Slow Devices
A B C
11. Group
Google Pixel 3 OnePlus 6 Samsung S9+Vivo 9 Oppo F7
RAM
CPU
Display
OS
4GB
5.7" 5.5"
8GB
5.8"
4GB
6.3"
4GB
6.3"
Android 8
4GB
Octa
core
Octa
core
Quad
core
Octa
core
Quad
core
Android 9 Android 8 Android 8 Android 9
A
12. Group B
Galaxy CoreI8262 Sony Xperia
SL(LT26II)
Micromax
Canvas Superfone
Asus Zenfone4 Oppo Joy
RAM
CPU
Display
OS
1GB
4.3" 4.3"
1GB
5.0"
1GB
4.0"
1GB
4.0"
Android
4.4
1GB
Dual
core
Dual
core
Dual
core
Dual
core
Dual
Core
Android
4.1.2
Android
4.0.4
Android
4.0.4
Android
4.4
13. Group C
Sony Xperia Tipo HTC A310E Explorer LG Optimus Net
Samsung Galaxy Chat
RAM
Processor
Display
OS
512 MB
850
MHz
3.2"
Android
4.0
Android
2.3
Android
4.0
3.0"
512 MB
3.2"
850
MHz
650
MHz
512 MB512 MB
3.2"
800
MHz
Android
2.3
15. Terminologies
Manifest File: Every project in Android includes a manifest file stored in the root directory
of its project hierarchy.
What information do you get here?
•Key information about the app without having to read other files in the package or run
the application.
•Defines which components of the application will be accessible externally to other apps,
and how those components interact with other apps.
•Declares which components and resources (icons, text strings, etc.) to use in which cases,
in particular with relation to other apps.
16. Terminologies
Target API Level: The Target Framework (also known as compileSdkVersion ) is the specific Android
framework version (API level) that your app is compiled for at build time.
• This setting specifies what APIs your app expects to use when it runs.
• It has no effect on which APIs are actually available to your app when it is installed
Android versions - Each release of Android goes by multiple names:
• The Android version, such as Android 9.0
• A code (or dessert) name, such as Pie
• A corresponding API level, such as API level 28
18. Why bugs occur?
Android Apps
Application Framework
Inter-Process Communication Proxies
Android System Services and Mangers
Hardware Abstraction Layer
Linux Kennel (With Hardware Drivers)
]
]
Higher Level
System
Lower Level
System
19. What does our analysis say?
Type Root Cause Percentage of Issues Issue Examples
Device -
Specific
Problematic Driver
Implementation
56%
OS Customization 36%
Peculiar hardware
composition
20%
Non-device
Specific
Android Platform API
evolution
67%
Original Android System
bugs
12%
22. The path ahead!
• The digital age force us to test smarter! Optimizing test & device
coverage is the first step.
• Effective use of Data Analysis to take testing to the next level
• pCloudy is at the forefront of innovation to keep you ahead
Thanks for introduction.
Good morning or good afternoon depending on which part of world you are in. It’s a real pleasure to be part of group of experts and a global audience. Thanks a lot for Joining in.
Let me begin with a brief intro about myself. My name is Avinash. I am a co-founder of pCloudy.com, one the fastest growing Mobile App Testing platforms.
So I hope you are settled and we are ready to roll.
I like solving problems of Testing teams and we created pcloudy.com with a goal to simplify lives or let me be precise “Testing lives of” of App developers and Testers. And we have made some exciting progress.
So, today I am going to focus on three key areas
Digital Transformation and world of Apps
Quality @ speed and what can do it beyond what you would have already seen
Lastly, how pcloudy helps you take it beyond.
Here is a checklist most organizations use to consider themselves agile.
If they have moved some dev project from waterfall to agile or have daily standup meetings, or have got a scrum master or think about CD all the time they think they are agile.
But the real question is Are they really agile? Let’s see further.
For Example-
if you support both Android and iOS, and your application will be used across millions of Google Nexus and Moto G devices but only thousands of iPhones, you prioritize testing on the Google Nexus and Moto G above the iPhone device.
So This test plan will consist of testing on devices which are prioritized by your market analysis.
For Example-
if you support both Android and iOS, and your application will be used across millions of Google Nexus and Moto G devices but only thousands of iPhones, you prioritize testing on the Google Nexus and Moto G above the iPhone device.
So This test plan will consist of testing on devices which are prioritized by your market analysis.
With the help of Market share approach you can typically gather approximate market share data and utilize it to prioritize your test device list.
You choose devices with the highest market share and test on as many as you have time and
resources for.
So if your QA cycle allows for testing across 10 devices, you test on the 10 devices with the
highest market share.
Disadvantage
The Market Share Approach ensures that you test on the most popular devices. However, by focusing
only on market share, you could be missing a whole class of devices that are less popular, but when
combined, still comprise a significant portion of the market. And you could be wasting resources testing
on two devices that are very similar—your application is extremely likely to work on both of these
devices if it works on either one. The next section describes an alternative approach that takes into
account both market share and device characteristics to optimize your test strategy.
With the help of Market share approach you can typically gather approximate market share data and utilize it to prioritize your test device list.
You choose devices with the highest market share and test on as many as you have time and
resources for.
So if your QA cycle allows for testing across 10 devices, you test on the 10 devices with the
highest market share.
Disadvantage
The Market Share Approach ensures that you test on the most popular devices. However, by focusing
only on market share, you could be missing a whole class of devices that are less popular, but when
combined, still comprise a significant portion of the market. And you could be wasting resources testing
on two devices that are very similar—your application is extremely likely to work on both of these
devices if it works on either one. The next section describes an alternative approach that takes into
account both market share and device characteristics to optimize your test strategy.