If your company desire to become mobile-friendly (or even go mobile-first), being able to test mobile covering effectively is critical. If you can ’ t do proper mobile testing, the rest of your nomadic package evolution and deployment will fall short.

However, prove effectively for peregrine applications is sometimes easier said than make. This clause identifies the challenge that arrangement ordinarily encounter when working to add mobile testing to their delivery chain, along with tips for addressing the challenges.

Deciding Which Mobile Testing Framework (s) to Use

One big vault that hangs up many teams is cull the right test automation framework. There are a plethora of option on the market, and there is no one pick that will address all of your motive. Commonly use frameworks includeAppium, Robotium, and Espresso.

Things to consider when you are selecting a fabric are whether you want it to be cross-platform, or to address only one type of platform (e.g., iOS or Android). Do you want to do UI testing or just component testing? Do you need data-level testing? Do you desire to be able to virtualize services? Do you desire to be able to simulate network latency and packets drop?

Perhaps the greatest challenge in this category is the cross-platform vs. application-specific question. The advantage to using a cross-platform solution is that you can potentially recycle all your exam cases more or less unchanged. On the other hand, a cross-platform testing answer create it more hard to perform platform-specific examination. It can also provide a mistaken sentience of protection by leading your technologist to overlook critical tryout for a specific program or environment.

Remember, however, that perfection is the enemy of progress. There is no such thing as the perfect testing framework. Pick the best fit for you, even if it is a combination of two or three framework, and start edifice tests.

Staying Agile with Mobile Testing

Under the Agile development mantra, there can be the perception that functionality comes before everything else. While working in smaller increments definitely allow for delivering work functionality on a much shorter timeframe, Agile does not mean that structure isn ’ t ask to control an application can be maintained and improved over clip.

For autonomous testing across multiple user personas, check out SUSATest — it explores your app like 10 different real users.

Putting the unveiling of a examination framework in the 1st sprint or two allows for faster rhythm times afterwards on as testing for previous sprints will be automatise, and manual validation can be limited to current alteration. Skipping the comprehension of a trial framework at the inception of a nomadic application may present the first working component a few day faster, but as the technical debt builds and the number of manual tests increases throughout the sprints going forward, the clip benefit up front will be quickly lost.

Integrating Mobile Testing with DevOps (CI/CD) Tools

In more established companies, one of the biggest hurdles will be working with any be concentrate team which currently deal DevOps or similar build and deployment pipelines. Unless a pipeline already supports building mobile apps, especially iOS ones, it will take some time to get everything desegregate and the wrick worked out to make builds and deploys seamless. Ideally your team would get an exclusion or be let to build a net new grapevine using Continuous Delivery principle to support roving app physique and deploys.

Regardless of whether you are a small or large shop, having builds and tests escape on a centralized service will ensure that multiple developers can all work on the app together and that the build is repeatable if something be ever to happen to a developer ’ s laptop or workstation. This could be as simple as having a dedicated Mac Mini go Jenkins that deal builds based on a WebHook from GitHub.

Integrating with ITIL Processes

ITILis not something the average inauguration will hold to deal with, as it is a framework use by larger administration to create sure their operation teams are postdate a standard set of better practices. In a typical go-ahead scope, once a mobile application will need to hire any component of the support organization, it will be asked to follow the same framework for tracking and scrutinize purposes.

The better part about this hurdle, while it may look daunting, is that ITIL Change and Release Management is all about consistency and reproducibility, which are what a proper uninterrupted delivery grapevine furnish. It is even possible (depending on the ITSM toolset involved) to automatically make all needed documents and requests inside the ITIL framework as component of each build, including the release line and tryout result.

You can go the placard child for how easily changes can course through the scheme, which helps everyone.

Conclusion

As shown, none of the hurdles listed in this article are insuperable. They just occupy some dedicated cycle to address, and once the hurdles are cleared, your mobile development life cycle will be world-class.

Vince Power is a Solution Architect who has a focus on cloud adoption and engineering implementations using open source-based technologies. He has extensive experience with nucleus computing and networking (IaaS), identity and admittance management (IAM), application platforms (PaaS), and continuous delivery.