Mobile DevOps has very different expectations, criteria and requirements when it comes to successful performance monitoring and general health-level of mobile apps, websites and APIs. The industry has somewhat neglected the fact that monitoring should happen on real locations over REAL networks with real infrastructure. The methods and tools build around mobile monitoring have been focusing too much on Real-User Monitoring (RUM) and unfortunately, this approach provides less useful and unreliable data about the actual performance – and the user experience. In this blog, we’ll take a look at the benefits and the real value of synthetic mobile monitoring, and how it can provide reliable and useful data about the performance, health-level and eventually, the user experience.
Building something that doesn’t meet the expectations right away can be a bad thing. However, sometimes with some types of apps, games and mobile websites, it takes the time to grow big and popular and eventually ends up being true hit products for its creator – and users as well. User Experience (UX), among many other important form factors for successful apps, is no doubt one of the most important driver for success.
In this blog, we’ll take a look at what are the costs related to user experience and especially when that great UX is not delivered with an app, game or mobile website. And these ‘costs’ are not all tangible and necessarily measurable due to unknowns. Let’s take a look!
Container technology and products aren’t new anyhow in mobile development today. The LXCs – Linux containers – which combine certain important kernel components to isolate resources have been around for a decade or so. But to get container technology for everyone the use of popular containerization products such as Docker have helped many of mobile developers to build clean and separated environments where things just work like “on my machine”.
In this blog, we’ll take a look at some technical aspects of containers and how to use those as part of your mobile app testing process.
Container technology has been enabling companies to pack various software components into a single physical package that can be used for various purposes. In mobile app testing, containers are extremely useful and can easily enable clean, secure and scalable test automation with the right set of tools, programming languages, frameworks and literally any software components that test scripts, automation components or application need for a test execution.
Last week we discussed about the benefits of containers for mobile app testing. In this blog we’ll take a look at quite typical ingredients for iOS containers and how to use those for iOS test automation.
The operating system and its version has a crucial role for all development going on Android and iOS. The applications – whether considered as more traditional applications, gaming apps, hybrid or web apps – are the beef for end-users to get everything out of their devices. All those mobile apps play an essential role determining if devices, OEMs, platform itself and the whole ecosystem can flourish.
In this blog, we’ll take a look at Bitbar’s data and analyze it a bit to understand why operating system versions are extremely important factor for app developers, and why appdevs should take every update seriously. Harshly, you know, the OS update can make or break the revenue generation from your app.
We’ve talked about this quite many times here at Bitbar Blog, but Appium has been one of the most solid open source test automation frameworks during the few past years. And despite of significant changes in Appium iOS, it seems that this framework is going (again) full steam ahead.
The latest addition is the Appium Desktop tool that enables users to work with Appium on their desktops and use Inspector for yet better analysis of their app. Let’s take a look at how to get Appium Desktop installed and how to work with it.
Every mobile app developer should consider how end-users of their app experience their app or service. For this purpose, Bitbar has developed its user experience monitoring that allows app developer organization to monitor, inspect and get instantly alarmed if something happens with the user experience flow from end-user’s point of view. To get the best possible tools and method available for developers, we’ve launched a localized monitoring service that uses real Android and iOS devices, with real networks and variety of different geographical locations.
This blog provides all steps you need to do in order to get started with synthetic mobile monitoring at any location around the world.
Real User Monitoring (RUM) has been discussed in great details and what it can provide for companies with mobile app, game or website. It’s has been also stated that Real User Monitoring will be a standard approach for many companies to get how their product does in the wild. However, in many cases, the RUM approach is not possible during the development and not even after release.
In this article, we’ll take a look of few important mobile monitoring user groups that should not rely on real user monitoring and why this is the case for these user segments. Furthermore, this article provides some reason why these app development ‘verticals’ get much better value out from synthetic mobile monitoring.
The Apple’s XCUITest has quickly become very popular among the iOS app developers, and testers as well. We’re extremely excited about this framework as it has enabled many of our users to adopt a new framework since UI Automation was deprecated. The XCUITest framework is not really new, but its foundation XCTest has been as part of the Xcode for some years already.
Let’s take a look at XCUITest and how to get started with it and run your tests on remote real devices on a cloud service.
Our CEO Marko Kaasila got interviewed by Netscout for his insights and deep knowledge of mobile testing industry. Read more to see what Marko things of today’s trends in mobile app testing and the best practices how mobile app developers, testers and organizations of different sizes can overcome problems, improve their app quality and gain better understanding of how users use their apps.
Read the Original Article Here.