Every now and then a new mobile test automation framework emerges, it quickly gains attention from mobile developers. This is happening right now with the Detox framework.
Like any team in the world, in the past years we have experienced multiple major changes in our development processes, product release cycles, team collaborations and overall company culture. The purpose of making changes is to be better, smarter and faster. As a Product Owner who is tightly tied with DevOps teams for planning, iterating and delivering, I’m really glad to speak publicly and start my journey of sharing our adoptions, changes and learnings in mobile DevOps.
First of all, I hope you all had a great summer.
As most of you have already known, we moved to a faster release schedule back in 2016, wherein we have been managing to deliver new features to all of our users on a bi-weekly basis thanks to keeping on agile practices. That being said, you might have noticed that this time the sprint for the new Bitbar Testing update is longer than usual. Why? Because we have exciting news to announce and it will bring great benefits to everyone down the line.
As a heads-up, we’re about to release a new version of Bitbar Public Cloud on the 19th of April around 10 am CET. The new awesome release is a major shift towards faster test execution, smoother and more efficient use of mobile devices from the cloud. The cloud and device capacity will also be significantly larger after this release.
Important! In addition to free device policy change, we’ll provide here some instructions on how to use RiC (Run-in-Cloud) and Java API Client after the release has been published. Keep reading!
For the past few months, we have been working on the new policy of the free plan for Bitbar Public Cloud. Below is the summary regarding the new policy.
N.B. If you are a sub-user of a paying account, this has no impact on your Public Cloud access. This change won’t affect Private Cloud or On-Premise customers on the use of your dedicated environment.
Many developers work on their console view significant portion of the day. Getting something done quickly and efficiently is one of those benefits that working directly from command line provides for our every day lives. Even test automation test scripts can quickly be started from the command line and in this blog we’ll take a look at how to get this done quickly and efficiently just using a bash / command line.
Don’t forget to read it entirely! There is a really nice helper script included in this article that will surely help you with your Appium testing!
We’ve been very working hard to build some new stunning features in Testdroid and I’d like to share few of them with you. Since I started as a Product Owner last fall, I have not posted actively update on our features – and there is a good reason for that. We’ve been focusing building the new great user experiences in our products and that has taken a significant portion of my time. In this blog, I’ll highlight some of the coolest features that we’ve done lately, and I’ll finish off this with few teasers about new features that we are working on.
When it comes to test automation frameworks for mobile development there are bunch of great options for modern app developers out there. Many of these mobile-centric test automation frameworks are actively developed and have an active community around those. We at Bitbar believe in these communities and encourage everyone to contribute and use these great open source frameworks, as testing of your mobile apps, games and web-related stuff is really vital for your success. Naturally, all these frameworks have their own traits, pros and cons, and one of the top feature/benefit you should look from these frameworks is how well it exposes the issues, performance, problems and all that DNA to fix app for perfect user experience.
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!