Reserve your seat now and mark it on your calendar! Our next webinar will cover how organizations, especially Enterprises, can adopt mobile devops practices and what tools, technologies should be utilized to help the transition to mobile devops. The webinar will include a Q&A session at the end so join us to ask our expert if you are involved in bringing mobile devops to your company.
Thank you all for attending our latest webinar – Hassle-Free Continuous Integration with Real Device Testing. Despite the topic isn’t new to any of us there were plenty of great aspects and insights provided on how to tackle today’s challenges using CI with real device testing.
According to various studies, many of retailers are still prioritizing customer facing programs over strategic infrastructure improvements, and choosing to invest in data capture for marketing purposes and pricing programs over mobile platforms and improved delivery. This is really a surprising finding as mobile-first initiatives are spreading across verticals and domains – and soon a significant majority of consumers use mobile web as their first data point to make their purchasing decisions.
How can brands ensure their quality criteria isn’t compromised and how to build better user experiences for customers?
In the mobile development, Agile and DevOps are widely used terms and majority of mobile teams exercise either one of these ‘practices’. However, there are differences of how organizations have adopted both Agile and DevOps culture in their daily doings. Some may even see agile and devops similar manner.
We’ll take a look at how these two popular and well-adopted methodologies/cultures are different from mobile testing point of view. For starters, I’d recommend to read the definition of mobile devops.
Already for years, our Testdroid Run in Cloud Plugin has been instrumental for many mobile app and game developers to enable test automation with real mobile devices on the cloud. As a Jenkins user, Testdroiders have had a chance to launch their test runs from the the Jenkins jobs and results have been delivered back in minutes. This enablement has been a profound shift for many developers to jump on board with real agile workflow and make continuous integration work for building and automating tests.
A tremendous number of things in mobile app development and testing are metric-driven. And especially when it comes to mobile app testing, metrics are highly valuable indicators of how well does the app perform, what is the general bug rate, and how many things have been exposed from the code so far. Metrics also reveal how well test automation and infrastructure used around it can expose issues in the code and how quickly and easily developers can fix those.
In this blog, I’ll describe one great example, a real-life story, of how one of our customer uses a great number of identical mobile devices, with the very same OS version, with the same OEM customization setup, to hammer their builds of their mobile app hundreds of times per day, and how each build are getting tested on those devices every time.
The increasing competition in mobile app landscape urges a call to action for companies to act rapidly with agile operations, while not to compromise on the quality of the mobile apps, games and webs. Thus, many software companies have established DevOps team, provided with automation toolsets, to accelerate and smooth the entire delivery pipeline. That being said, not every company gets the real essence of DevOps or has it properly aligned with Developers and other IT professionals. We will be hosting a webinar to share with you what you can learn from top companies and what their DevOps do for day-to-day tasks. Save your spot now.
One of the cornerstones in mobile app testing is the efficient use of test automation, with real hardware, making all that to work for you efficiently, and seamlessly integrate with your development and testing process. You know, the whole beef with test automation is that you can simultaneously run tests on different devices, preferably tens or even hundreds of those, to get comprehensive understanding of real behavior of your app on real platform. As discussed, there are myriad of different combinations when you consider OS version, hardware setup with all its diversity, networks, user conditions and many other things. Running something in concurrent – or parallel – mode will get you great details how things actually perform. Let’s take a look at some fundamentals of mobile app testing and how to use parallelism / concurrency to deliver you a significant value.
Like in all software projects, products and companies, the process of writing down documentation about requirements sparks never-ending debate of how it should be done, how much is enough, what and how certain feature requests and requirements should be documented. We are no exception here at Bitbar.
In this blog, I’d like to explain how we have approached this challenge, what have been the pit-falls for us, and how we have overcome of those issues. It’s just not about documenting requirements and specifications, but how to get those in our every-day doing and make these our strength – and build incrementally better product and the requirements documentation.
As we advocate an agile development and practices for any kind of mobile development, we would like to share with you some fundamentals and our thoughts on how we’ve built our products, what kind of processes we use internally to get things done efficiently and what has increased our capability to faster build and deploy new versions of Testdroid. This being a broad topic, let’s start first with a glance on how we changed our internal doing into yet more agile doing – enabling us to do faster releases. The part of that is agile process, agile regression testing and test-driven development approaches. Let’s deep dive into details!