Applause headquartered in Framingham in Massachusetts offers application testing services.
Leaving a video review helps other professionals like you evaluate products. Be the first one in your network to record a review of Applause, and make your voice heard!
Applause headquartered in Framingham in Massachusetts offers application testing services.
- No setup fee
- Free Trial
- Free/Freemium Version
- Premium Consulting / Integration Services
7 people also want pricing
AutomationHQ™ (AHQ) is a complete TAAS (Test Automation As Service) solution. Its NLP driven, cloud-based No-Code test automation platform is presented as ideal for agile delivery team. Any one in agile team can develop In-Sprint test automation in plain English with AHQ. User can create virtual…
TryMyUI.com is a remote usability testing platform that offers affordable, cross-platform services for testing and improving the user experience. The product allows you to watch videos of real people using your website or app to see where (and why) users get frustrated, lost, or confused. People…
- Tech Details
- Applause is great for testing our iPhone/Android app across many different mobile phone models including different versions of the operating systems and helps us find those obscure bugs and eliminate them before launch.
- Applause is great for testing our iPhone/Android app across many different languages and user groups from around the world and helps us find those obscure language bugs such as cropped text or poor translations and eliminate them before launch.
- The Mobile Beta Management tools for pre-launch app development are particularly excellent in order to get user feedback. It allows the user to shake the phone and add a comment about what they like or do not like or to report a bug. The platform allows me and the developers to see the screen where this occurs as well as what was happening in the SW code leading up to the incident. It also allows for surveys to get specific feedback with statistics.
- In using MBM (Mobile Beta Management), it would be better to have the surveys be based on completion of a specific task instead of time or number of app access. This might be a little more complex to set up, but would be well worth it.
- A "stakeholder management" view would be nice to allow those not normally using the tool to get a quick status of testing.
- A "stakeholder management" view for MBM would be nice to allow those not normally using the tool to get a quick status of progress and user feedback.
Also, if you want to do pre-launch app research without the restrictions of the appstores (only need the email of users who you want to try the product and no time limit for using the build), then Applause MBM is great!
Applause helps us launch our mobile apps quickly and frequently by augmenting classic testing approaches with real-world testing. Risk of a failed launch is greatly reduced because we have the happy path coverage locked down on each and every release.
- Provides excellent platform, device, and OS coverage across the board. We don't have to worry about purchasing a barrage of devices for in-house testing. It's expensive and doesn't provide a good return for the money.
- Your Project Manager actively manages your project. They are available almost 100% of the time during business hours to ensure your test needs and concerns are being handled.
- Applause's test management software is rapidly advancing. It's fairly feature packed and provides good visibility into what's going on with your testing.
- Though Applause effectively manages their testers, there can be a gap at times between lining up the testers and getting the results you want. It's a fine balance between fresh eyes gleaning new or glossed over bugs but running the risk of being product ignorant vs. returning testers generating more in-depth issues and risking test exhaustion and jaded perspectives.
- Applause's Test Management software really needs backward integration with Jira. Currently they support forward integration, but if you're managing your issues internally, all that information (state, comments, etc.) cannot be conveyed back to Applause.
- Fast ramp-up - minutes after activating a test cycle I will see testers jumping in, starting discussions in chat, and logging defects found.
- Able to test on every device we've ever asked for.
- Expertise in areas like scripting and test automation, accessibility, and more.
- Good integration with our JIRA defect tracking system.
- A great test team lead assigned to a test cycle to vet and approve bugs entered by test team members.
- Videos attached to defect reports when screenshots don't cut it.
- Defect reports can at times be confusing or not quite up to the standards we have internally but video attachments almost always clear up any confusion.
- At times I'll find a limitation with the platform but so far I've always found a workaround, and they are making continual improvements to the platform.
- They are able to spin up skilled QA resources quickly and effectively.
- They provide an elegant, intuitive interface to interact with testers and the defect reports.
- The main disconnect we encountered had to do with our development process and types of applications. The provided testers were great for the initial functional pass and for regression validation. But for in-depth analysis of features in subsequent deliverables, we passed a point of diminishing returns due to general stability and lack of time for the testers to discover the underlying nuances and complexities of the applications.
- Even with lengthier cycles, testers were not easily motivated to dig deeply beyond the high level stability to investigate the depths of the programs. This could be helped on our company's part by creating more detailed requirements and test cases but the "out of the box" model from Applause doesn't seem to have good "in-depth" review beyond the top level exploratory.
Key things for a company to consider as you engage Applause would be to make sure you have clear direction and understanding of what you hope to accomplish. You can just set the Applause team loose at the product and you'll get some defect reports. But you'll have much better results if you can provide good information and instructions to the team.
You should also plan on having a person dedicate some time (exact amount will vary by project) to the Applause project in terms of answering questions at the start of and during the test cycle as well as time to review, rate and comment on the submitted tickets at the end of the project.
- In-the-wild testing - it cannot be done internally. It's impossible to cover the wide matrix of devices and OS versions.
- Exploratory testing - more eyes see more. Every mind is unique and thinks of a workflow differently - provides better coverage of the product.
- Care provided by test lead is essential - they help a lot with initial bug triage and bug transfer to our internal systems.
- Retest of found tickets once they are fixed - saves time!
- Applause people make a good effort to create a relationship, it's not just business.
- The service is quite expensive.
- The first year of using the service is about finding the right balance. It can initially be more time consuming then the previous model without Applause service.
- The model motivates the testers to not go very deep during testing - they are paid by bugs found. Means there are cases when they go for only the low hanging fruit.
- Great interface for reporting bugs and interacting with testers. The platform integrates with JIRA so issues can be pushed directly to our project.
- Project manager was very helpful and responsive. Once I sent him all the scope details, he was very quick about getting a test cycle up and running, even at 6pm on a Friday.
- I felt like I still spent a lot of time validating bugs that were reported by testers. I understand that testers are paid based on the number and importance of bugs they find, so superfluous bugs were reported fairly often.
- Backwards integration with JIRA would be helpful, so the bugs in the Applause platform are always in sync with the bug statuses in JIRA.
- Excellent customer service
- Easy-to-use customer portal
- Fast, thorough results that can easily be obtained and reported on from our end
- Repeated issues (duplicates) reported
- Some areas of their admin portal are tricky or confusing
We use it in our company as Quality Assurance. We have a team of Android\IOS developers and basically not so many QA's and using the site we are able to run our tests, receive and fix bugs and much more even with no QA people.
- Providing help and support for their customers.
- I think that they can improve their UI and response times.
- Applause was able to accomplish what our internal test team could not. We had an international issue that was occurring with customers in Colombia that we could not reproduce or simulate through a VPN. Calling in Applause, they were able to quickly find testers in that country with the specific cell phone carrier that we needed. The testers there quickly replicated the problem and from there we were soon able to create a fix.
- Finding testers through the Applause ecosystem in International areas and throughout a variety of demographics allows for us to more effectively simulate real world usage as we load test against our applications.
- Applause was able to find many more authentic localization issues that a third party localization company missed. Having real-world testers from Applause that really understand the language from a native speaker perspective, helped us to find many additional issues after our initial localization builds were handed off.
- Some testers are not well versed in the platform. This is the exception.
- They are always quick to answer your questions and are helpful whenever you need something.
- They have great testers that follow the guidelines and make it easier for clients to manage their issues.
- They will always keep in contact and ask for your feedback to make their services even better!
- One feature that I can see so far that needs to be improved is the way that the video submissions are handled. Because every time you try to open up a video on a bug submission you either need to download a big file or sometimes it does not open up.
- Often will provide video proof of various bugs.
- Have an extremely wide range of phones and devices.
- Quick turnover time.
- Their website (dashboard) can take some getting used to
- Testers can come from any background and sometimes do not have full knowledge of the cellphones.
- Finding crucial bugs.
- Finding important but non critical bugs.
- Creating test plans.
- Sometimes the person reporting a bug isn't clear in their bug description or steps to recreate.