JM

Justin M.

Senior Manager, QA & Development

Mid-Market (51-1000 emp.)

5/14/2019

"Off to a great start"

4.5/5

What do you like best about Test IO?

Good UI, clean bug reports, the ability to run multiple cycles at the same time, and results in days (or hours) instead of a week. Review collected by and hosted on G2.com.

What do you dislike about Test IO?

Not much. Inability to see some defect reports until very end of the cycle. Sometimes hard to find testers for the more obscure environments (although test IO will work with you on this). Review collected by and hosted on G2.com.

Recommendations to others considering Test IO:

The bug fix confirmation does cost extra but it's been worth it for our team, to have a tester retry and tell us if fixed or not. It is very fast to request the BFC, and they usually respond back very quickly (like same day). Review collected by and hosted on G2.com.

What problems is Test IO solving and how is that benefiting you?

Our internal testing team doesn't have the kind of availability to jump on certain projects, but test IO makes it very easy to spin up a team fast. We also don't have access to all the hardware and software configurations that the test IO community has. Review collected by and hosted on G2.com.

JP

Jesse P.

QA Manager/ Engineer

Small-Business (50 or fewer emp.)

11/22/2019

"TestIO good investment"

4.5/5

What do you like best about Test IO?

The ability to have my content tested over night. Review collected by and hosted on G2.com.

What do you dislike about Test IO?

The Language barrier can make things a little difficult, this can be over come by explaining things a little more clearly than you would think you have to do. Review collected by and hosted on G2.com.

MK

Mark K.

Head of Consumer Product

Small-Business (50 or fewer emp.)

5/8/2019

"Very pleased with Test.IO"

4.5/5

What do you like best about Test IO?

Testers appear to do *a lot* of testing of our site, often finding obscure bugs along with the more noticeable ones that occur in more common user flows. Bugs are reported with clear steps to reproduce, screenshots, and videos. I appreciate the range of testing devices and operating systems, which include many devices that our user base has that our internal staff doesn't use as their primary device. The Jira integration makes it easy to create new bugs with the content from the Test.IO testers. Review collected by and hosted on G2.com.

What do you dislike about Test IO?

The Jira app could use some small improvements. I often need to reload the Jira page in order for the call-to-action buttons of the Test.IO bugs to work. (Not sure if that's a Jira or Test.IO app issue.) Also, the Jira app does not show the browser/OS info (although that is passed along if you create a Jira issue), so I'm sometimes forced to log into the Test.IO site if I want to find that information. Review collected by and hosted on G2.com.

Recommendations to others considering Test IO:

You do need to spend some time creating documentation of the "features" of your application so the testers will know what and how to test. This can be done over time, however. As you run more tests, it becomes apparent what gaps there may be in your descriptions, so you can improve on that. Review collected by and hosted on G2.com.

What problems is Test IO solving and how is that benefiting you?

I sleep better knowing the site is extensively QA'ed each week -- we have a test scheduled after each weekly release. Test.IO has helped us efficiently discover, prioritize, and fix problems that impacted our users. Our on-staff QA is freed up to spend more time collaborating with our dev team on new features, while Test.IO can do the majority of regression testing (outside of automated testing.) Review collected by and hosted on G2.com.

JH

Jason H.

Lead Web Developer

Small-Business (50 or fewer emp.)

5/22/2019

"Test IO ensures nothing gets missed!"

5/5

What do you like best about Test IO?

I really like the depth that Test IO goes into when testing sites. Examples of this would be finding a link that was an absolute URL and pointing to a staging site, or finding straggler Lorem Ipsum text on an internal page, and so forth. They really help save our reputation in these situations by ensuring that any mistakes are found before we go live! Review collected by and hosted on G2.com.

What do you dislike about Test IO?

My only dislike would be that, sometimes the report includes issues that are not actually bugs, but more design suggestions. At the point that we're submitting to Test IO, we're already firm on the design elements and are just interested in bugs, so these particular suggestions don't really help us overall. But I just skip over those items in the report and continue on with the bugs. Review collected by and hosted on G2.com.

Recommendations to others considering Test IO:

Test IO is another layer of protection for ensuring that your website has a successful launch without there being any unforeseen or overlooked bugs or hiccups. With Test IO, I can be sure that it won't be a client or a post-launch visitor that finds something someone on our end may have missed!

Give it a try and see if it works for you! Review collected by and hosted on G2.com.

What problems is Test IO solving and how is that benefiting you?

Problems solved include finding lingering issues on the site that we missed on a first pass internally. This benefits us greatly by ensuring that the client (or even worse, a visitor once the site is live) doesn't encounter them. Review collected by and hosted on G2.com.

UR

Verified User in Retail

Mid-Market (51-1000 emp.)

5/17/2019

"Quick and Useful Feedback"

5/5

What do you like best about Test IO?

I like that we can get instant feedback on features that we put on our digital products and in-depth usability feedback when sending over surveys. Review collected by and hosted on G2.com.

What do you dislike about Test IO?

I dislike that if I am running a survey that requires me to cross-reference for the tester user names, the interface does not list the tester user name per bug report sent in. I have to click into each bug report to see who sent it in, which is not the most efficient approach. Review collected by and hosted on G2.com.

Recommendations to others considering Test IO:

My advice to those considering test IO would be to think about what your use cases are going to be. Make sure that you optimize the usage of the platform if you do intend to go with them. They are able to take surveys for you, evaluate if your homepage updates align to what was expected, and they will catch bugs that you yourself may not necessarily find because you are so immersed in your product. Review collected by and hosted on G2.com.

What problems is Test IO solving and how is that benefiting you?

With test IO we are trying to do the following: 1) ensure that the site is fully functional and running optimally as much as possible 2) determine what parts of the site are not working as expected and know what to fix immediately or in a future update and 3) gather user feedback to help determine what are ideal implementations for select features. In terms of benefits, the test IO team is very good at finding bugs that we do not necessarily find and also provides perspectives that we may not necessarily consider but should. It is very easy to get tunnel-visioned when trying to test a product that you are exposed to every single day. Review collected by and hosted on G2.com.

AJ

Anthony J.

Web Designer

Mid-Market (51-1000 emp.)

5/16/2019

Business partner of the seller or seller's competitor, not included in G2 scores.

"Smooth and Efficient "

5/5

What do you like best about Test IO?

The results are great and they have a pretty quick turnaround time. Also, they attempt to reproduce the issues found on multiple devices for sanity. Also, I love the way how you can easily duplicate and/or edit tests for each cycle. Testers seem pretty thorough and accountable. I also love how you could potentially have multiple cycles running at once for multiple project/platforms. All in all, test.io is a great platform with awesome admins and testers. Review collected by and hosted on G2.com.

What do you dislike about Test IO?

I can't really think of any downsides. The interface is great and it's very user-friendly. I think the communication is great as well with the emails for when a test starts and completes. Also, appreciate the support from Justin Tanisawa. Review collected by and hosted on G2.com.

Recommendations to others considering Test IO:

Don't hesitate and give it a try. Pretty sure you won't be disappointed with the results. It's easy get started and it's super straightforward for tech-savvy and non tech-savvy individuals. Review collected by and hosted on G2.com.

What problems is Test IO solving and how is that benefiting you?

We're solving the issue of not having enough internal testers on our team in order to do all of our regression testing. The testers at test.io feel in the gaps to ensure we finish up testing in a timely manner. So we've definitely realized the benefits of having test.io as a part of our testing team to feel better about our release because they help out tremendously with our exploratory testing each and every cycle which is an important part of our manual testing that needs to be achieved. Review collected by and hosted on G2.com.

KE

Kareem E.

QA Tech Lead

Mid-Market (51-1000 emp.)

4/30/2019

"Great business partner, with an innovative crowdsourcing QA approach "

4.5/5

What do you like best about Test IO?

- Devices pool: We always have access to devices that we need for our cross-compatibility Coverage testing.

- Fresh eyes: This concept involves thousand of testers that can help uncover new/different issues from various experiences and perspective

- Types of testing coverage: Mainly rely on Coverage testing and Focused testing

- Reports: I got an EoW report that summarizes my weekly testing activities, besides the actual test execution summary

- Continues Support: Sometimes the JIRA integration feature might be overwhelming. Yet, operational POC can always help configure and set it up to as needed

- Roadmap visibility: They always take feedback to improve their platform. Moreover, you get a peek on new features in the pipeline that will help using the platform. Review collected by and hosted on G2.com.

What do you dislike about Test IO?

- Two-way sync and the JIRA process flow might be a bit confusing. Luckily, our operations POC helped us set it up.

- Redundant/ Existing tickets within JIRA projects (internally) can be handled in a better way to link them to the Know Bugs list that Testio finds.

- Sometimes we still get the same reported bug, after being rejected or even accepted. Review collected by and hosted on G2.com.

AH

Verified User in Health, Wellness and Fitness

Small-Business (50 or fewer emp.)

4/30/2019

"Very cost-effective testing service"

4.5/5

What do you like best about Test IO?

The quality, quantity and coverage of the bugs found is impressive, and an integral component of our test strategy. The exploratory nature of the test.io testing approach tends to uncover interesting bugs - I'm often amazed at how creative the test.io testers are in exploring deep and detailed flows. Review collected by and hosted on G2.com.

What do you dislike about Test IO?

I'd like to see out-of-box support for regularly scheduled (templated) regression test runs. The UX-specific testing could also benefit from cohorting (being able to select specific audiences of UX testers for a given test). Review collected by and hosted on G2.com.

Recommendations to others considering Test IO:

The more detailed the expected user flows are the better test coverage you'll receive. With the exploratory testing approach you don't want to be too detailed - just enough for the testers to understand context and the rough outcome you're looking for. Review collected by and hosted on G2.com.

What problems is Test IO solving and how is that benefiting you?

Exploratory and device testing at scale are the biggest problems test.io solves for us. The randomized nature of the exploratory testing generates bugs we would never be able to find with our small dedicated internal testing team. The device testing, though not deterministic, still gives quite decent OS and phone coverage at a fraction of the cost of implementing a full-scale Selenium Grid-type automated solution. Review collected by and hosted on G2.com.

MT

Mahima T.

Software Engineering Project/QA Manager

Small-Business (50 or fewer emp.)

11/25/2019

"Easy access to variety of resources"

4/5

What do you like best about Test IO?

It is very easy to get all kinds of browser, device and location tests done through testio. Review collected by and hosted on G2.com.

What do you dislike about Test IO?

It still needs someone to create the tests for them Review collected by and hosted on G2.com.

AI

Verified User in Internet

Mid-Market (51-1000 emp.)

5/15/2019

"Easier Way to Gather and Manage your Product's Bugs"

4.5/5

What do you like best about Test IO?

Test.IO highly eases our process of finding and identifying bugs. Thanks to the testers, we can test our products in many kinds of different devices and browsers. Also, the team leads are doing a very well job on eliminating out of scope bugs. And I have to say that Test.IO has magnificent customer support. Anytime we got stuck on a process, we got immediate help from their support. Review collected by and hosted on G2.com.

What do you dislike about Test IO?

API section can be improved with more options to make API calls and with more detailed user guides. Also, the user interfaces can be improved. Review collected by and hosted on G2.com.