Mobile Field Testing Strategy – Part #2
Guest Post by Dean Murphy:
Before continue reading this part of the guide, you may want to head back to the first chapter:
Welcome back…in part 1 we explained that testing your mobile solutions under lab conditions may cause problems when the solution is piloted or goes live. Last week, in part 2, we looked at some of the elements to consider when preparing for testing in the Analyze phase.
This week the Plan section outlines the activities that should be conducted to facilitate the execution stage along with the resources, materials and equipment required to conduct field testing.
|Test Approach Document||Produce a test approach document that includes the rationale for the field testing along with matrices of test cases and conditions. The approach document should also include anticipated timescales and contingency plans.|
|Communication||Initiate a communication strategy that ensures all project team members and stakeholders are aware of the field test initiative and the goals.|
|Reporting||Define a set of reporting metrics that are in-line with existing project reporting mechanisms. Reports could include the following:
This information can be broken down by code release to track improvements.
|Manual test scripts||Produce test scripts for each major usage pattern identified in the analyze stage. Include a test step for each user action e.g. open application, log on to application, etc. Ensure the scripts also factor in the use of third-party software such as satellite navigation, security software, etc. and follows any health and safety guidelines.|
|Automated test scripts||Produce automated test scripts for each major usage pattern identified in the analyze stage. Automated testing could reduce the need for manual testing during a field test tour and may reduce the size of the test team.|
|Baseline performance tests||Carry out baseline performance tests in the lab using the manual and automated field test scripts. These will provide a set of baseline test data that can be compared to the field tests results. Metrics could include screen transition timings, real-time data response times and time required to execute a test script.|
|Test tour||Using the cellular coverage maps, plan a test tour that will cycle between strong, weak and no signal zones. The tour should include a test script sequence, this sequence should ensure that each test case is executed at each test location. Multiple days may be required to execute a complete set of test cases.|
|Exit criteria||Agree the field testing exit criteria with project stakeholders.|
|Anti-static bags||It is sometimes difficult to find a true no signal zone within the boundaries of a field test area. A device placed inside a transparent anti-static bag can reduce the signal level by up to 25% which, in weak signal areas, is enough to create a no signal zone. Ensure there are enough anti-static bags (including spares) for each field test device.|
Come back next week as we move on to the Execute and Review phases.
About the Author:
Dean Murphy has been working in the field of mobility for 12 years and has broad experience of many mobile implementations from push email to large scale enterprise solutions. Dean is a Solution Consultant with ClickSoftware and helps customers understand how they can solve their business problems through the use of the ClickSoftware Mobility Suite and the ServiceOptimization Suite.