It would be great if this group could develop guidelines/best practices for mobile testing our websites before they are launched.
This is something that my group has bumped up against quite a bit . We know that we need to do mobile testing as we are developing our web sites and web applications. However, we cannot get to non-public websites without being on the network. So, this limits our ability to do any mobile testing to only those employees with USGS mobile phones. There are a few issues with only being able to use USGS devices – in my experience, many USGS employees with mobile devices have iPhones which behave differently than other devices, so we would not get a broad picture of how the application works across devices. Also, it limits our pool of who can do the testing since they would need to be internal and would need to have a USGS mobile device. My group has tried to deal with this in a couple of ways. We have used desktop emulator tools to test out how an application will look on mobile, but is quite different from how someone would actually interact with the site when holding a device in their hand. We have also created a "beta" tier of a website that is public, but has a nonsense URL so that it would not be easily discoverable. For many of our products, this has been an OK solution; however, I could see some products being more sensitive and this practice being more risky.
There is also a question of being able to do efficient mobile development of the software, which is hard to do right now because you cannot start up a local host on the network unless you have a USGS device. This means that you need to push your changes up the chain and merge into a repository then deploy to your test tier before you can see what effect your change had. This may be a question for the software dev cluster, though.