What is our primary use case?
We are mainly using it for automated testing for some devices that we're not able to have physically. We are also using the Perfecto service to do manual testing.
We deploy builds daily, and we have an automated pipeline that goes directly to Perfecto. We do it on a daily basis.
How has it helped my organization?
If anyone who doesn't have company-issued devices wants to do testing of our mobile application, we can always provide them access to Perfecto, and they can play around with the app there. That has been really nice.
We recently set up a couple of test cases for automated testing. Being able to run them automatically and being able to see the success and failure rate of those runs every day has saved us a lot of time. It has also been helpful in identifying issues, and it has also been helpful in terms of the timeframe and being able to find them a lot sooner.
It works well when it comes to executing cross-platform testing. I would give it a positive rating in that regard. We're able to test on Android and iOS devices pretty seamlessly.
We are utilizing Perfecto's cloud-based lab to test across devices, browsers, and/or OSs. The device lab is very important for our testing operations. If we have issues with the devices being offline, we wouldn't be able to run our automated tests.
Perfecto's device lab has helped us to scale our testing operations. Currently, our company doesn't issue Android devices to us. I have an iOS device that's company-issued on which I can do manual testing. For Android testing, we've been leveraging the Android device in Perfecto. It is pretty important, and it has been helping us to determine what our baseline is with the Android builds. Because we're not able to physically see it, having it in Perfecto is super helpful.
It has saved us the cost and effort of having to maintain our own virtual test environment. It is hard to quantify in dollars, but in time, it has probably saved up to 100 hours, not more than that. As we build out our test suite more, it would save us even more time. Running those automated tests running as compared to someone manually testing the application and finding issues would definitely save time. Being able to find issues a lot quicker results in us being able to fix them a lot quicker.
It has helped to speed up our testing efforts, and it has also affected our software quality. It has improved the quality of our software due to us being able to find and fix the bugs a lot sooner.
What is most valuable?
Manual testing is definitely valuable. The insights feature is also valuable. I just started looking into that to get more data around the results of the testing. I'm looking to explore that one a bit more, but definitely, the manual testing and the insights are the top ones.
Their team is really great to work with. They're very flexible, and they always show care. They prioritize our work, our company, and our working relationship. I appreciate the ad hoc sessions that they schedule to provide help with troubleshooting, provide the information that we're looking for, or do a demo of a new feature that they have. They're always willing and very quick to get that scheduled for us. I appreciate that a lot.
What needs improvement?
If we could run an accessibility test in Perfecto against builds, it would help us a lot. Currently, that's a very manual process for us. We haven't found a tool that can do accessibility scans for iOS and doesn't depend on engineering effort. Having a feature related to that would be really awesome for us.
Buyer's Guide
Perfecto
January 2025
Learn what your peers think about Perfecto. Get advice and tips from experienced pros sharing their opinions. Updated: January 2025.
832,138 professionals have used our research since 2012.
For how long have I used the solution?
I've been using Perfecto for about a year and a half.
What do I think about the stability of the solution?
We have had some issues in terms of our environment, and it's hard to say whether it's because of Perfecto, or it is actually our app build that is introducing some of those errors that we have to maintain. So, overall, I would rate Perfecto a seven out of ten because sometimes, we also have lagging with some of the devices. We get error messages, but we're not quite sure what's causing them. However, whenever we do submit tickets for them for support, they're resolved pretty quickly. So, I would rate it a seven out of ten for stability.
What do I think about the scalability of the solution?
We have an end-to-end (E2E) environment that we deploy for testing in Perfecto. Currently, it just supports our product team, which has about 10 people. In the Credit organization or department, we're the only mobile team. The web team, with about 50 people, is evaluating using Perfecto, but currently, our product team is the only one that I'm aware of in our organization. In the main organization, there is another app team that uses Perfecto. They use it a ton more than we do just because their product is much bigger. Their team roughly has 200 people.
There is a ton of potential for scalability because the other team that uses it is huge as compared to ours. They use it pretty heavily. They run thousands of tests a day, and I'm able to see their metrics as well. So, it definitely has a huge capability for scaling.
How are customer service and support?
Their support is amazing. We have a technical consultant from Perfecto with whom we work. Whenever we need help with troubleshooting, he's very responsive over email. He is also very responsive in terms of scheduling a working session with the engineering team. It is easier to troubleshoot that way. Their customer support is great. I would rate them a ten out of ten.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We didn't have anything else in place before.
How was the initial setup?
I wasn't involved in its deployment. In terms of maintenance, across the enterprise, I'm sure everyone has their own scenarios, but in our product team, we do have to have maintenance. We run into scenarios a lot where there are issues with our end-to-end environment, and we have to invest some time to make sure that everything is running as expected.
It is not a scheduled maintenance per se. Usually, if we have a line of sight to some updates that are coming from Perfecto, we can account for them, but a lot of the time, they are the changes within the app, which as such wouldn't be considered as maintenance. So, we do have to maintain it, but it is not scheduled maintenance, and we do have to put in effort just to make sure everything is running. Usually, just a pair of engineers do that, and it's more on an ad-hoc basis as opposed to on a scheduled basis.
What was our ROI?
We started seeing its benefits in the last three months. Last year, we were still doing a lot of the initial setup, and we weren't utilizing it as much for testing, but this year, we are getting a lot more usage out of it. It is just because of the way the team has been working. It is not a limitation of the tool.
What's my experience with pricing, setup cost, and licensing?
I am not sure about its pricing, but from our perspective, licensing has been easy. Anytime I have new users or requests for users that want to get added, it's a very simple process. I just give the architectural owner of the product the name and email address, and they're able to easily add a new user. We don't have any issues in regards to getting licenses, but I don't have any insights into pricing.
Which other solutions did I evaluate?
I personally didn't evaluate other options. This is our enterprise tool. When they selected it, they did evaluate other options, but it was done way before we got the tools. So, I'm not sure what the other options were.
What other advice do I have?
Perfecto has a lot of taped demos and webinars and informative videos to help you discover the features of the tool. They are very good to get more familiar with how to use it and how to find the best features that work for your team. I would also recommend working closely with their account management team. Their customer support has also been very helpful. When we get stuck and we don't really know which direction to go, we have a contact, as opposed to just trying to figure it out ourselves. It is always easier to just talk to someone from their team to get a more clear direction. So, the informational videos that they offer as well as leaning on the actual representative from the company to help you define the best use of the tool for each product are the way to go.
At this time, we are leveraging Perfecto's reporting and analytics very lightly. We're just using the default dashboards that come with the tool. We're just getting into having more useful data and using it more. I expect to be doing more with that. These analytics will be important for us because we'll be able to understand our failure versus pass rate for a lot of the automated testing. We won't be able to understand why those failures are occurring, of course, but at least, it will give us an indication of fixes that we need to address which might have got missed with manual testing.
Perfecto's cloud-based lab provides same-day access to new devices, but it is not too important for us. It depends on what the time window is. Usually, we get it within a week of our original request, and that seems to work fine for us. So far, we haven't had an immediate need to have the device available on the same day.
Perfecto supports a range of open-source technologies, but I don't have enough experience with that. Currently, we're using Appium by default, and I don't know if that's a limitation of Perfecto or an industry limitation.
I would rate Perfecto an eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
Disclosure: PeerSpot contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.