Be brief and specific

Yes, a test plan is necessary but it doesn’t have to be a paperweight that no one reads.  The test plan defines what testing will be done in specific terms. A single page test plan in any format works. The test plan provides a method of planning rapid testing in an effective manner.

Conduct risk based testing

Rapid, valuable testing needs to be risk based. Your QA resource won’t be able to cover multiple types of testing thoroughly in a rapid test cycle. The first step in the test plan is having the team define which areas must be tested because they inherently contain the greatest risk of failure. iOS8 features cover new MDM related administrative options and significant security testing impacts.

Define test types and unit testing

Define the type of testing based on risk that you can test. Based on the new features in iOS8, functional and security testing are critical. Handling the certificate usage, the handoff between devices and transferring confidential data means security and data sharing issues. It’s possible to combine testing into a single test suite covering multiple high-risk areas and  imperative to include developer written unit tests to assist in test coverage. If you plan it out in advance, you’ll know what functionality you are testing and how thoroughly.

Continuously test

Testing never stops. Continuous testing is executing all the other testing you didn’t have time to do. For example, the optional features in iOS8 mean you need tests when features are turned on and when they’re turned off as well as random combinations. Additionally, performance, compatibility, interface, services and operational testing may be options you need to plan for and execute between release cycles.