test IO

test IO

4.4
(43)

Crowdsourced QA for websites and mobile apps.

Work for test IO?

Learning about test IO?

We can help you find the solution that fits you best.

test IO Reviews

Ask test IO a Question
Write a Review
Filter Reviews
Filter Reviews
  • Ratings
  • Company Size
  • User Role
  • For Category
  • Industry
Ratings
Company Size
User Role
For Category
Industry
Showing 43 test IO reviews
LinkedIn Connections
Justin M.
Validated Reviewer
Verified Current User
Review Source

"Off to a great start"

What do you like best?

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.

What do you dislike?

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).

Recommendations to others considering the product:

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).

What problems are you solving with the product? What benefits have you realized?

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.

Sign in to G2 to see what your connections have to say about test IO
Mark K.
Validated Reviewer
Verified Current User
Review Source

"Very pleased with Test.IO"

What do you like best?

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.

What do you dislike?

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.

Recommendations to others considering the product:

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.

What problems are you solving with the product? What benefits have you realized?

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.)

What Software Testing solution do you use?

Thanks for letting us know!
Kyle M.
Validated Reviewer
Verified Current User
Review Source

"Fantastic way to improve testing at a startup"

What do you like best?

Results of testing are usually very useful and the quality of bug reports is excellent. All bugs have easy to follow steps to reproduce as well as device information, a video, and screenshots. Additionally, the variety of test devices means the test coverage obtained is much better than anything we'd be able to do in house at a smaller company.

What do you dislike?

The UI for test.io itself could use some improvement but at this point we work almost entirely in Jira which test.io integrates fairly well with. This integration has a few rough edges but nothing major that negates its benefits.

What problems are you solving with the product? What benefits have you realized?

Test IO provides a great way to obtain good test coverage across a variety of devices and use cases. This is something that would be impossible to do in house with our resources. Test IO helps us focus on developing new features and remaining competitive.

L. Fernando G.
Validated Reviewer
Verified Current User
Review Source

"Test.io changed the way we test!"

What do you like best?

The peace of mind our team gets by knowing that our app is being tested by users in the "real world", using real devices in varied environments.

What do you dislike?

Learning to interact with the crowd takes some practice. Luckily Test.IO's pricing model is ideal for experimenting and minimizing the cost of learning to use the crowd..

What problems are you solving with the product? What benefits have you realized?

We reduced the time spent on regression testing by 80%, so our internal testers can focus on collaborating with the developers and testing new features while the crowd does more mundane testing like regression sweeps and bug confirmation. This results in faster delivery with less resources.

An additional benefit we realized after using the crowd is that we need less devices for in-house testing. The crowd has such a large variety of devices we have managed to lean out our inventory.

Kareem E.
Validated Reviewer
Review Source

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

What do you like best?

- 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.

What do you dislike?

- 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.

What problems are you solving with the product? What benefits have you realized?

By pointing Testio to our production environment, we were able to identify business critical issues. Moreover, they help us create and maintain the QA level of confidence for our rapid deployment model.

Jason H.
Validated Reviewer
Review Source

"Test IO ensures nothing gets missed!"

What do you like best?

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!

What do you dislike?

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.

Recommendations to others considering the product:

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!

What problems are you solving with the product? What benefits have you realized?

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.

U
User
Validated Reviewer
Verified Current User
Review Source

"Quick and Useful Feedback"

What do you like best?

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.

What do you dislike?

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.

Recommendations to others considering the product:

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.

What problems are you solving with the product? What benefits have you realized?

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.

Anthony J.
Validated Reviewer
Review Source
Business partner of the vendor or vendor's competitor, not included in G2 scores.

"Smooth and Efficient "

What do you like best?

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.

What do you dislike?

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.

Recommendations to others considering the product:

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.

What problems are you solving with the product? What benefits have you realized?

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.

A
Administrator
Validated Reviewer
Verified Current User
Review Source

"Very cost-effective testing service"

What do you like best?

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.

What do you dislike?

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).

Recommendations to others considering the product:

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.

What problems are you solving with the product? What benefits have you realized?

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.

A
Administrator
Validated Reviewer
Verified Current User
Review Source

"Time-Saver, Money-Saver and Confidence Booster"

What do you like best?

Test.io has allowed us to rollout new site features with confidence, knowing that they've been seen by an international audience using dozens of different devices, platforms, etc. We no longer have to maintain a test bank of desktop and mobile devices ourselves.

What do you dislike?

Occasionally, we will get duplicate reports of the same issue by multiple testers. However, the benefits of this service FAR outweigh this minor inconvenience.

Recommendations to others considering the product:

Being able to have dozens of people from all over the world test your product on a variety of devices in a 24-hour period is invaluable. Not having to maintain a full testing suite of desktops, laptops, tablets and mobile devices saves time and money, allowing your development team to focus on fixing bugs and creating new features.

What problems are you solving with the product? What benefits have you realized?

We have seen a reduction in overall problems reported to our customer service team, especially from our international customers. What used to be virtually impossible (or at the very least impractical) for our small development team to test is now a breeze using the test.io platform.

Isaac M.
Validated Reviewer
Review Source

"Excellent customer service and exploratory testing."

What do you like best?

My teams account manager is always eager to help us out.

What do you dislike?

The plugin for Jira is a little clunky and does not allow for a lot of useful functionality like editing of a ticket before it is added to our system.

Recommendations to others considering the product:

This won't completely replace internal testing, but it does take a significant amount of weight off of the in house QA team.

What problems are you solving with the product? What benefits have you realized?

We are a small company less than 20 people, but have the project load of a 50 person company. I am the only member of the QA team and so the additional testing support from Test IO is very helpful.

A
Administrator
Validated Reviewer
Verified Current User
Review Source

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

What do you like best?

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.

What do you dislike?

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.

What problems are you solving with the product? What benefits have you realized?

Identifying bugs before the actual release of the product. Creating tests for different environments allows us to cross-check the problems of our products and get ready for a release without spending time to search bugs on every device one by one.

Alex M.
Validated Reviewer
Verified Current User
Review Source

"Test.io is Perfect for Our Testing Needs!"

What do you like best?

Test.io is incredibly responsive and was willing to customize their solution to fit our fast-growing tech startup. They had the best pricing (by far) of any option we evaluated and also coupled that with fantastic service. Hard to do better.

What do you dislike?

The product doesn't have every single bell and whistle, but if you need a feature, they'll build it for you!

What problems are you solving with the product? What benefits have you realized?

We've been able to better map the health of our product feature by feature, understanding where we have critical masses of bugs and need to spend more development time.

Mariia B.
Validated Reviewer
Verified Current User
Review Source

"Now I know how to get relevant results from crowd testers"

What do you like best?

Their management support and willingness to satisfy our needs in terms of specific tests needs and platform options overall.

And I've learned how to define test requirements

What do you dislike?

Crowd testers are not enough attentive while reading test description.

Duplicated bug reports come from different testers during one session

Recommendations to others considering the product:

Be very specific when submitting a test request and you'll get reliable testing results

What problems are you solving with the product? What benefits have you realized?

Getting real users feedback about common cases and, what is more valuable, about cases we don't use to check

Covering different devices

A
Administrator
Validated Reviewer
Verified Current User
Review Source

"One essential step in the QA"

What do you like best?

I really enjoy the easiness of starting and evaluate tests. Once setup the test creation is very simple and can be done under 10 minutes. Evaluating bugs is fast and nearly all issues can be viewed in followed in screen casts. The Jira integration works seamlessly.

What do you dislike?

The offer structure for me is very complex. I'd like to have more test types in my package, since it's very pricy.

Recommendations to others considering the product:

Take time for setting up test.io properly and integrate it as a fixed step in your testing processes in order to make full advantage out of it.

What problems are you solving with the product? What benefits have you realized?

test.io is already a inherent part in our release management for apps. The crowdsource testing is an essential supplement to the normal feature testing.

Mike S.
Validated Reviewer
Verified Current User
Review Source

"Part of our team"

What do you like best?

Its such an innovative platform...we use crowdsourcing for other elements of our business (such as logos) so why not QA right? This gives us on-demand fresh eyes for less than the cost of having ONE full-time QA person in-house. Pretty amazing!

What do you dislike?

This is a newer platform, so its still evolving. But that means you have a voice in how it improves...so gift and the curse really.

What problems are you solving with the product? What benefits have you realized?

We want to make our dev team's feedback look totally autonomous without our upper management being involved. Its a process, but we're getting close!

A
Administrator
Validated Reviewer
Verified Current User
Review Source

"Very easy way to kickstart a QA team"

What do you like best?

Being able to run a rapid test in <4 hours, easily have a QA team run a full analysis on the website without the headaches of managing a full-time internal QA team

What do you dislike?

Not being able to make tests from templates, sometimes crowdsourced testers can be a little eager to make up their own definition of a bug or make several bug reports for symptoms of an overarching bug.

What problems are you solving with the product? What benefits have you realized?

Website is constantly being audited for functionality and usability, while our team can instead focus on creating new features and fixing bugs that are already reported, instead of trying to find bugs that are often hard to find without the power of a large-scale crowdsourced testing team.

Keith B.
Validated Reviewer
Verified Current User
Review Source

"Excellent QA Resource and Tool"

What do you like best?

Their platform uses actual people to simulate real world tests you just can't get through automation.

What do you dislike?

I don't have any negatives to share, but if I had to answer something, I suppose at first it can be overwhelming to parse through the large number of findings a test typically turns up.

What problems are you solving with the product? What benefits have you realized?

We have found bugs around our shopping cart especially; which any fix there is obviously reflected in revenue and customer experience directly. We also found numerous suggestions on improving our UI/UX experience.

John-Patrick G.
Validated Reviewer
Verified Current User
Review Source

"Most Tests are good - some lack quality"

What do you like best?

Speed of the tests is mostly good to very good, options for tests are very good

What do you dislike?

quality, breifings are sometimes not read thoroughly, Feedback to issues is sometimes not really solving the problem (Redmine export not working)

What problems are you solving with the product? What benefits have you realized?

Testing of Websites, Shops and features

it gives a broader picture of what users might encounter when using our services, as one does not always realize these issues when you are heads deep in the project yourself

Adrian C.
Validated Reviewer
Verified Current User
Review Source

"Invaluable test resource"

What do you like best?

It's an easy way to get eyes on all platforms and devices. We often get bugs in areas of the app we ourselves tested.

What do you dislike?

It is hard to communicate directly with the testers to get more info on how to reproduce an issue, but the team leads are very responsive.

Recommendations to others considering the product:

Be very explicit in your instructions so you can get the best results in your tests.

What problems are you solving with the product? What benefits have you realized?

Multiplying our QA team's size and efficiency without increasing head count.

U
User
Validated Reviewer
Review Source

"Amazing Company for Crowdsourcing Mobile App Testing"

What do you like best?

The communication between our team at BuzzFeed and the account management at Testio has been a real surprise as they have been treating us like we are there only account. Their attention to detail for any testing that we submit to them has been amazing and we have seen immediate returns and hope to continue more in the future.

What do you dislike?

I cant say at this time there are many things to dislike. I think at first we had some issues with process for submitting test runs but I believe that was due to the current process for on-boarding new companies and to make sure that we were getting the maximum results for our contract.

What problems are you solving with the product? What benefits have you realized?

I think that the biggest benefit that we have received so far is the ability to add on 10x the amount of testers than we previously were using for our regression tests and the value has been excellent.

Dan J.
Validated Reviewer
Review Source

"We avoided loosing thousands of euros by discovering critical bugs with schedules tests"

What do you like best?

Super fast bug discovery

Great support from the Test.io team

Tests easy to set up and deploy

Flexible in the case of unusual requirements for usability tests

What do you dislike?

General, template-based answers for usability tests

Not being able to do localization testing

Recommendations to others considering the product:

If you work in a fast paced environment, where continuous testing is essential, Test.io can provide very valuable support for the in-house testing team.

What problems are you solving with the product? What benefits have you realized?

We use Test.io to discover bugs in our products, prior and after deployment.

Besides finding potentially costly bugs in time, we were able to find critical bugs on the live platforms, which can cause loses in thousands of euros.

Nathan V.
Validated Reviewer
Review Source

"Bug Detection and Sanity Check Beyond Capability of Software"

What do you like best?

test IO gives us unique and helpful bug through human discovery. The best part of test IO is the value in allowing human users to use your product in ways that humans would, meaning bugs and user flow improvements are found. Ultimate QA tool.

What do you dislike?

test IO required a fair bit of set up and maintenance. While writing the tests is not difficult, it does required foresight and tweaking the test specs to your exact preference takes multiple weeks of tweaking.

What problems are you solving with the product? What benefits have you realized?

-Ultimate QA Tool

-New feature and new deploy sanity checks

-Bug discover through normal human use on product

U
User
Validated Reviewer
Verified Current User
Review Source

"Good amount of testers"

What do you like best?

The ability to have «close at hand» a big number of testers available to run a battery of tests on my product.

What do you dislike?

The UI is not pretty and sometimes convoluted. A better UX would boost the product a lot

Recommendations to others considering the product:

If your test flow is well defined and you don't have in-house QA this is definitely a good choice.

Need to have a very detailed set of instructions so there's a big investment in there at the beginning.

What problems are you solving with the product? What benefits have you realized?

Regression bugs and overall confirming that the app is not broken when new features are introced

Gareth P.
Validated Reviewer
Verified Current User
Review Source

"Helpful service, essential part of our QA toolbox"

What do you like best?

Having real users test the service is really helpful and helps to uncover edge cases that are hard to catch with automated testing or in-house manual test plans.

What do you dislike?

Turnaround takes 4-24 hours depending on test type, due to the type of testing (Crowd, manual)

What problems are you solving with the product? What benefits have you realized?

Ensuring quality, more efficient QA, frees up engineer time

Learn more about test IO

test IO Videos

Kate from G2

Learning about test IO?

I can help.
* We monitor all test IO reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. Validated reviews require the user to submit a screenshot of the product containing their user ID, in order to verify a user is an actual user of the product.