OpenText Functional Testing Lab for Mobile and Web Reviews

• Management of a pool of devices that can be made available globally for automated, manual or performance tests, via a slick interface.  
• Strong integration with HPE tools, ALM, UFT, Sprinter and LeanFT, and the integration with non HPE tools.  
• Strategic solution that pulls in real world analytics from AppPulse Mobile to aid in definition of strategy and integrates with Network Virtualisation to see how the device will run under real network conditions.  
• Primary usage is on real devices but also supports emulators.  
• The 2.0 release extends capability to AWS device farm.

It is enabling a global strategy to be put in place.  Our largest implementation is with a global team.  The solution provides a controlled device farm with the right devices (selected based on analytics), that are readily available (can be reserved), have the right app and can be used for manual or automated tests.  

Manual testing (with Sprinter) is accelerated with steps being captured automatically with exploratory testing, storyboards being captured and device logs etc. automatically being attached to defects (that can be sync'ed back to non-HPE tools or raised directly in non-HPE tools).  Net effect, developers get the right info to address issues quickly and efficiently.

Automation allows fast and efficient testing across a range of devices, this would not be feasible manually.  The skills and good practice used for non-Mobile directly apply. Shared Object Repositories and Application Models make a big difference for maintainability - object recognition has always been a HPE strength.

There has been a notable shift in emphasis, from the on device get it to work, to strategy and how the full benefit of the solution, with analytics and NV is used.  

Mobile Center development is moving at pace.  With versions prior to 2.0 I found that configuration was trickier than it should be, particularly with aspects such as NV.  With 2.0, the NV installation is straightforward and integrations are performed prominently via the UI.  I had one issue on installation of the stack for MC 2.0 (MC, UFT, LeanFT), I found a workaround and found that I also had responsive support.

This is a solution that's easy to use. It also gives us the possibility to use real devices connected either on the Mobile Center server or on our own computers. And it works with both iOS and Android devices.

We now have the ability to test our app on real devices instead of just on virtual devices.

There are couple of improvements I'd suggest. First, it would be helpful to have a Windows Server version instead of just Linux. Second, I think it would be a good idea to have an interface to manage the server, specifically to run Android Debug Bridge (ADB) commands.

I've used Mobile Center for 4 months.

Deployment was an issue. Each time we set it up and deployed, it failed and we had to relaunch it again.

Also, we weren't able to set up the Windows components.

Other than the deployment issue, once it was running we didn't have any issues with stability.

Scalability is not a relevant issue with this solution.

I never used customer service.

I never used technical support.

We had not prior solution to this.

The initial setup was complex because Mobile Center is only supported on Linux. There was also the issue with deployment failure once we did set it up.

We're able to test different mobile apps at the same time with the defects gadget.

We've not set it up properly yet, so my experience is limited, but the ideas and possibilities that this tool has are incredibly useful.

Because of connection errors, we've haven't yet been able to set it up properly at my company.

I've used it for one month.

We have a specific department that deals with customer service.

We have a specific department that deals with technical support.