Serverless infrastructure environments are set to become the dominant paradigm for enterprise technology deployments, according to a new report — Why the Fuss About Serverless? — released by Leading Edge Forum ...
3 Key Components of the Mobile App Testing Cycle
September 11, 2013
Start with Eran Kinsbruner's blog: Are Your Mobile Apps Ready for the Real World?
An integrated and iterative mobile application testing cycle should include the following key components:
1. Test Automation
For flow control and repetitive testing, automation allows developers to test a function many times without having to manually test a program. This automatic function can give full reports of each execution with helpful statistics and insights, as well as save time and money on problem reproduction.
In a highly fragmented mobile market, the use of device-agnostic scripting lets you build test cases that can be easily maintained, reused and ported to multiple mobile platforms.
2. Performance Testing
Performance testing in real-world conditions is a prerequisite for ensuring the best possible user experience. Simulating mobile load against specific network conditions, and during specific times of day, is very helpful in predicting performance bottlenecks. Application developers/testers must take into account the fact that the number of users for specific applications at peak hour and seasons can be significantly greater than average use.
Testing for performance against pre-OS versions of Android, iOS, etc. enables the detection of OS-specific network issues on specific devices. In this context, it is important to download available beta releases of iOS and Android and test your app against these versions on leading devices (smartphones and tablets) under different network conditions. This lets you identify and fix potential issues before the general OS version release. A good example of this was the avoidable iOS 6.1 network bug, which resulted in 3G network performance issues on 3G networks for iPhone 4S users.
3. Production Monitoring
To enable achievement of your business goals, the mobile quality lifecycle must also include performance monitoring of applications in production. Enterprises cannot afford to launch an app and wait for a problem to occur. By monitoring the application 24/7 on real devices, your operations team can obtain metrics and detailed reports on application behavior and understand exactly what end users are experiencing. Real-time mobile monitoring allows you to isolate, analyze, classify and reproduce issues for fast resolution.
In a dynamic and unpredictable mobile market, a continuous and iterative testing cycle, comprising automated functional testing, performance testing and production monitoring are crucial for meeting users' expectations and maintaining brand loyalty. Mobile APM solutions that address these needs allow enterprises to benchmark success over time and constantly improve the quality of their applications – to the delight of their end users.
Related Links:
The Latest
November 14, 2018
What to automate? Which parts of the delivery process are good candidates? Which applications will benefit from automation? At first, those sound like silly questions. Automate all your repetitive processes. If you think that you'll do the same thing manually more than once, automate it. Why would you waste your creative potential and knowledge by doing things that are much better done by scripts? Yet, an average company does not adhere to that logic. Why is that? ...
November 13, 2018
I'd love to see more security automation deeply integrated into the development process. Everybody knows since the 1990s that security as an afterthought just doesn't work, yet we keep doing it. The reason, I think, is because it's very hard to automate security ...
November 09, 2018
DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 5, the final installment, covers deployment and production ...
November 08, 2018
DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 4 is all about security ...
November 07, 2018
DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 3 covers the development environment and the infrastructure ...
November 06, 2018
DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 2 covers the coding process ...
November 05, 2018
Everyone talks about automating the software development lifecycle (SDLC) but the first question should be: What should you automate? With this question in mind, DEVOPSdigest asked experts from across the IT industry for their opinions on what steps in the SDLC should be automated. Part 1 starts with by-far the most popular recommendation: Testing ...
October 31, 2018
Halloween is a time for all things spooky, but not when it comes to your mobile app experience. A poor experience can not only scare off your customers but keep them away for good ...
October 30, 2018
As organizations have embraced open source, they have become polyglot — using multiple programming languages and technology stacks to accomplish software and hardware related tasks. Enterprises are caught between the benefits provided by a polyglot environment and the complexities and challenges these environments bring. Ultimately, if the situation remains unchecked, polyglot will kill your enterprise ...
