It’s obvious that companies nowadays are investing more in automation solutions to streamline the workflow of build, test, deploy and monitor mobile apps. As developing high-quality apps requires lots of intensive testing, companies will most likely highlight Speed as one of the cornerstones when evaluating test automation tools and services.
Transforming a company from Agile Development to Continuous Delivery by deploying a high degree of automation into its delivery pipeline, is called DevOps nowadays. DevOps is short for Development and Operations – the two departments that generally operate with two very different goals. Software Development teams are continuously writing new and better code to achieve fast iteration cycles. They need an environment with improved and instant feedback loops on new innovations. Conversely, Operations teams are all about keeping production software stable and working, no matter what. They need an environment that alerts of any deviations in production. In general, the fewer changes to the environments are introduced, the better.
Have you ever heard term – “Slack is the new email”??
When we talk about DevOps with our customers, terms like “automation”, “speed”, “collaboration” and “tools” always dominate the discussion. Mobile teams want to “move fast and break things.”
It’s become widely accepted fact that every second matters in today’s #ConnectedWorld and business depends on #UX to be competitive. If you depend on your users to alert you to the problem then you’ll definitely notice a drop in revenue and uninstalls. What can we do to identify this problem earlier so that we can avoid losing revenue?
“What devices should we use to test our applications” is a question we get on daily basis from our customers. As we have over 70,000 users from all over the world and from every possible industry sector, there is no simple answer to this question.
The diversity that different application segments require for mobile app testing is enormous and for example game developers tend to use different types of devices for testing when compared to enterprise app developers. The very same applies for users, people who use that app/game on their devices. We’ve included both Android and iOS devices in our data.
The potential and the expectations set in mobile enterprise apps are soaring. The future is clearly a mobile one, but not only for consumers and individuals, but increasingly for enterprises. What are the factors that will be critical for enterprise mobility – and the entire enterprise mobile app development cycle – to be a success in the future? There are few solid foundations we know already that provide significant advantages its users. Let’s drill more in details.
The past weeks have been unparalleled in terms of activity among the mobile developers around mobile device clouds. Personally, I am happy to see Microsoft, Amazon, IBM, and numerous other companies are stepping up in delivering open, standards based tools and services from cloud for mobile devs.
Since you’re someone who cares about mobile app, game or web development and testing, I wanted you to be the first to hear the big news. As we keep working to make things yet more easy and straightforward for our customers and enable them to build world-class apps, games and mobile web content for the hundreds of millions of users, I wanted to share few thoughts with you.
Quality assurance (QA) is a critical part of the process when creating and maintaining successful mobile apps for hundreds of millions of app consumers. One of the metrics in this app creation process is naturally QA’s productivity – the success to efficiently find and filter out the problems in apps before they land on hands of users. This type of productivity of quality assurance can be measured by various metrics, for example:
One of our customers used to do agile development, with typical 2 week sprints, and then combined that with 4 weeks manual testing cycles. So, they ended up doing 2 additional development sprints before developers got feedback from the manual testing on the 1st development sprint! That was huge waste of resources, and ended up in a mess and missed and delayed deadlines. The solution was to go really agile, do continuous integration, continuous testing and automate the testing on real end user devices, all the time during development.