There are multiple testing considerations associated with each aspect of the BYOD implementation, End Point Testing, MDM Solution Testing, or Corporate Solution Testing.
Probably the most obvious strategy area is end point testing. This testing focuses on the mobile device itself and whether or not the device is able to access corporate applications, such as email, contacts, calendar, VPN, and so on, that are part of the corporate BYOD strategy.
The five suggestions that follow address what I consider to be the Top 5 testing considerations for BYOD testing. However, the order and priority of the items should be based on your organization’s particular risk tolerance profile.
- Tests should be developed that ensure that all supported device, OS, carrier combinations function correctly. These tests should verify that the device is able to access the network, install the configurations from the MDM solution and correctly access the authorized corporate applications.
- Tests should be considered that attempt to access the network using unsupported devices and OS versions. This strategy is designed to ensure that the system is proactively handling unsupported devices. A well-defined BYOD implementation will deny unsupported devices at every level of the solution.
- Test the actual solutions that are installed by the MDM solution on the mobile device. When an employee connects to the network for the first time, the MDM solution will install applications, such as virus protection on the employee device. Also remember to test that updates pushed out by the MDM are effectively handled by the device.
- Test to ensure that all Personally Identifying Information (PII) is protected on the device. One of the legal considerations for corporations is access to and the protection of, employee PII. The strategy should include testing to ensure that the company doesn’t have the ability to access the device’s location data, which may violate law in many jurisdictions.
- There is a lot of testing that needs to be considered associated with testing the MDM solution installed on the device. This would include testing that the MDM policy enforcement functions correctly for events such as Jailbreaking or rooting attempts, as well as, the blocking of blacklisted applications.
Did you enjoy this article? Help spread the word by sharing:
Engage in the conversation and leave a comment:
About Brian Copeland (19 articles)
With over 25 years of senior level experience in the software development industry specializing in organizational transformation and development, Brian has been instrumental in the testing of critical business systems, from mission critical applications to commercial software. Mr. Copeland’s career has included 10 years as the Test Operations Manager for the Titan II, 34D, IVA, and IVB programs, managing both flight and ground software-testing facilities for Lockheed Martin. Mr. Copeland also served as the Sr. Manager of Quality Assurance for the shared services of Deloitte & Touché, LLP. His diverse experiences range across the aerospace, medical device, title insurance, legal services software, big four accounting firm, and banking industries. Brian led the global testing organization for The Nielsen Company, overseeing the successful transformation of the testing function made up of over 750 testing associates. Mr. Copeland has been a key-note speaker at the International Business Forum, and has been a featured speaker at HP Software Universe. Brian is a past president of the greater Cincinnati International Institute of Business Analysts (IIBA), and holds an ITIL v3.0 Foundations and RCV certifications.
Categories: Mobile, Performance Testing and Automation, Security
Tags: Android, automated mobile testing, bring your own device, BYOD, DMCA, end point testing, iOS, jailbreaking, mobile devices, mobile testing, performance testing, rooting