Recently, someone I met brought to my attention that my site had a display bug. While this can be fairly common and might seem uneventful, it made me wonder about crowd-testing my sites or apps.
Most developers out there are probably already familiar with applications such as Browser Stack or Lambda Test that let you test your sites in different environments, to make sure your users won’t be encountering bugs.
But theses apps require you to manually check your site, thus spending loads of time clicking through different settings and pages.
An alternative would be to go to “device rooms”. Some companies and agencies have put together rooms full with devices using different OS and browsers. While this can be very useful, it is physically impossible for them to get and maintain all existing devices even if you wanted to focus on the main, most recent ones.
So I thought about the message I was sent, letting me know there was a problem with one of my pages. I thought “wouldn’t it be great if you could have a group of people paid to test your site and basically do all the bug reporting, instead of asking your team to do it or doing it yourself.”
Well, of course it exists, and I am sure that for more advanced developers and especially those working in security, these tools have already been in their arsenal for ages. The name for it is “Bug-bountying”, but “crowd-sourced bug reporting” is equally eloquent.
In this article I try to give you a comprehensive list of all the options and tools that can help you save time finding bugs, whether they are functional or cosmetic.
It’s important to know that 88% of people will abandon an app because of bugs, so it’s easy to make an ROI assessment when you need to purchase a plan for bug-bountying.
It’s also interesting to know the distinction between testing types. on Lambda Test’s blog you will find the following descriptions:
- Accessibility Testing –To make sure your software is accessible to all, including people with special disabilities.
- Usability Testing –Testing of a website for its usability concerning user satisfaction.
- Exploratory Testing –Testing approach that includes simultaneous learning, test designing and test execution.
- Regression Testing –Testing the whole application after any new change has been made. The idea here is to check that the new change is not disrupting any of the pre-existing functionality.
With digital discovery being more mobile centric it is crucial that you be ready for mobile web pages with regression testing.
- Cross Browser Testing –Testing to ensure that your webapp is operable through different browsers, across various devices with different screen sizes.
Here are a list of crowd-testing websites in three categories: Display, Structural, Usability and Security
Am I responsivehttp://ami.responsivedesign.is/#
Cross Browser Testinghttps://crossbrowsertesting.com