Welcome!

Mobile IoT Authors: Zakia Bouachraoui, Yeshim Deniz, Pat Romanski, Elizabeth White, Dana Gardner

Related Topics: Mobile IoT

Mobile IoT: Article

Testing Wireless Systems

Leveraging automated testing tools

Wireless devices provide users with freedom, convenience, and flexibility. But as their dependency on wireless devices grows, users are becoming increasingly concerned about the quality and performance of wireless networks.

Today's service providers are aware of these concerns and are making big changes to ensure their wireless networks live up to customer expectations. This includes changing their approach to quality assurance (QA) testing. Service providers now recognize that they must test both the device and the network to maximize performance and interoperability. Service providers also have realized something else: How they approach wireless system testing can profoundly impact the quality of their wireless solutions.

Wireless Means Greater Complexity
Wireless devices and the networks in which they coexist are exceedingly complex. Service providers must keep pace with innovation and the demands of the marketplace by constantly building new features and options into their network services. Many service providers also have global clients, which can require managing large-scale, campus-wide deployments with hundreds of access points, intricate physical layouts, and even more intricate security protocols. Such systems must be sufficiently robust to guard against packet loss, plus they must be able to meet stringent interoperability requirements, as they often incorporate devices from many vendors.

Amid short product cycles, surging complexity, and steadfast competition, the list of items to test grows. Yet service providers seldom have enough time to test everything on this list - such as all the combinations of encryption on their larger deployments. Without 100 percent test coverage, however, they risk missing something critical in the testing process. Whether that is a device feature or a compatibility issue, customers will have a problem that needs to be fixed - and making a repair in the field will cost them time and resources.

Steps to More Efficient and Effective Wireless System Testing
Most organizations need to change their view of system testing before they can successfully move forward with wireless system testing and make it part of their standard testing protocol. First, they can no longer view system testing as simply packet routing. The operation of the network, configuration, speed, and packet quality can all dramatically affect the applications that run on them. Second, these systems/integrated solutions do not use the network simply as a delivery mechanism, but rather as part of the application. Changing this mindset is the first step to more efficient and effective wireless system testing, and more important, better quality solutions.

The following tips can further help service providers approach wireless system testing in a more strategic manner. The goal being to ensure that devices not only work as designed, but also work as part of a larger system, a completely integrated solution.

Conduct System Testing in Parallel with Feature Testing
Within the product cycle, organizations typically start with feature and logic testing, and then progress to system and scenario testing. By testing in a linear fashion, however, organizations risk running out of time and skipping aspects of the system testing that can have a dramatic impact on customers. After all, if a customer's device does not interoperate with another vendor's device, then a system issue is just as problematic as a feature bug.

One recommendation is to start system testing much earlier, in parallel with device and feature testing. System testing reveals different issues than feature testing, and no matter how new a product is, organizations need to test it and test for both aspects. By testing as much as possible from both perspectives, organizations will be able to more quickly identify and resolve defects. The benefits are not only greater efficiency and coverage, but a better quality product produced in less time.

Determine Which Tests Are/Should Be Manual
To get the greatest return on automation, organizations need to intelligently evaluate tests to determine which ones are best suited for automation. They can start by understanding why a test is done manually in the first place. Are testers performing it manually because they have no other option? Or, do they believe that the tester is adding value? Typically, the answer is none of the above. Most people simply do not believe that they have the time or permission to change.

The first tests to evaluate for automation are those that are menial and repetitive, and performed for every build. The second set of tests or processes to consider are those involving large numbers of devices that must be set up, and in which testing consists of orchestrating numerous commands in a specific order or simultaneously. By having a tool that can rapidly and reliably execute these tasks time and again, organizations can save large amounts of time. In addition, such targeted automation can provide organizations with significant productivity and coverage gains, resulting in better quality.

Identify Which Tests Need to Be Repeated with Every Release
Once organizations can identify the tests that must be run for each engineering build, they should target those for automation. Automation is an equal opportunity tool and can be leveraged for the most rank and file tests, not only for regression testing.

Organizations should focus on automating the tests that they execute numerous times over the release cycle. These might be menial, repetitive tests, but organizations increase their risk of error by performing them manually. After automating these tests, organizations can set their sights on automating the more complex test cases.

Design for Testability
Organizations can make dramatic strides in testing efficiency - and thus quality - by having developers design for testability. This requires getting development groups involved in testing or at least making them aware that their decisions - such as changing the name of a programming object - ultimately impact testing. When software is designed in a way that makes testing easier, developers and testers can truly work as one team, dedicated to producing a quality product.

Make Quality the Goal, Not Automation
When organizations don't experience productivity gains from automation tools, often it's because they are focused on the wrong result. Organizations typically create automation initiatives with automation as the goal, when quality really should be the goal and measure of success. After all, the fact that an organization has automated 1 million test cases is meaningless if customers are complaining about quality issues.

Organizations therefore need a quality metric that's tied to a business value, such as customer satisfaction, and not simply a number denoting how many test cases they automated. With this data, they can pinpoint where (in the cycle) automation delivers the greatest return, both to the business and to customers. They can then make better, more strategic decisions about implementing automated testing tools - and automate the right things.

Automated Testing Tools for Wireless System Testing: Measuring Results in Quality
Wireless systems are typically plagued by more manual testing and lower coverage than traditional wired systems. Service providers and other organizations can leverage automated testing tools to tackle these issues and produce higher quality products in less time and with fewer resources.

More Stories By Chris Bowlds

Chris Bowlds is a solution architect at Fanfare Software. Chris has nearly 12 years of high-tech industry experience, having worked in tech support, QA, development, professional services, training, and sales.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


IoT & Smart Cities Stories
The deluge of IoT sensor data collected from connected devices and the powerful AI required to make that data actionable are giving rise to a hybrid ecosystem in which cloud, on-prem and edge processes become interweaved. Attendees will learn how emerging composable infrastructure solutions deliver the adaptive architecture needed to manage this new data reality. Machine learning algorithms can better anticipate data storms and automate resources to support surges, including fully scalable GPU-c...
Machine learning has taken residence at our cities' cores and now we can finally have "smart cities." Cities are a collection of buildings made to provide the structure and safety necessary for people to function, create and survive. Buildings are a pool of ever-changing performance data from large automated systems such as heating and cooling to the people that live and work within them. Through machine learning, buildings can optimize performance, reduce costs, and improve occupant comfort by ...
The explosion of new web/cloud/IoT-based applications and the data they generate are transforming our world right before our eyes. In this rush to adopt these new technologies, organizations are often ignoring fundamental questions concerning who owns the data and failing to ask for permission to conduct invasive surveillance of their customers. Organizations that are not transparent about how their systems gather data telemetry without offering shared data ownership risk product rejection, regu...
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
Poor data quality and analytics drive down business value. In fact, Gartner estimated that the average financial impact of poor data quality on organizations is $9.7 million per year. But bad data is much more than a cost center. By eroding trust in information, analytics and the business decisions based on these, it is a serious impediment to digital transformation.
Digital Transformation: Preparing Cloud & IoT Security for the Age of Artificial Intelligence. As automation and artificial intelligence (AI) power solution development and delivery, many businesses need to build backend cloud capabilities. Well-poised organizations, marketing smart devices with AI and BlockChain capabilities prepare to refine compliance and regulatory capabilities in 2018. Volumes of health, financial, technical and privacy data, along with tightening compliance requirements by...
Predicting the future has never been more challenging - not because of the lack of data but because of the flood of ungoverned and risk laden information. Microsoft states that 2.5 exabytes of data are created every day. Expectations and reliance on data are being pushed to the limits, as demands around hybrid options continue to grow.
Digital Transformation and Disruption, Amazon Style - What You Can Learn. Chris Kocher is a co-founder of Grey Heron, a management and strategic marketing consulting firm. He has 25+ years in both strategic and hands-on operating experience helping executives and investors build revenues and shareholder value. He has consulted with over 130 companies on innovating with new business models, product strategies and monetization. Chris has held management positions at HP and Symantec in addition to ...
Enterprises have taken advantage of IoT to achieve important revenue and cost advantages. What is less apparent is how incumbent enterprises operating at scale have, following success with IoT, built analytic, operations management and software development capabilities - ranging from autonomous vehicles to manageable robotics installations. They have embraced these capabilities as if they were Silicon Valley startups.
As IoT continues to increase momentum, so does the associated risk. Secure Device Lifecycle Management (DLM) is ranked as one of the most important technology areas of IoT. Driving this trend is the realization that secure support for IoT devices provides companies the ability to deliver high-quality, reliable, secure offerings faster, create new revenue streams, and reduce support costs, all while building a competitive advantage in their markets. In this session, we will use customer use cases...