1. Sign up in a few clicks
2. Provide a link to your product
3. Get a price
4. Pay and start testing
5. Get tested app within 24 hours
Ideally, features are areas of your product incorporating a range of functionalities or user stories.
What a QA Supermarket Feature may contain:
- User stories to cover / functionalities to test
- What is considered a bug and what is intended behavior
- Known issues for this feature
For an e-commerce website, the feature set might look like this:
- Registration & Login
- Filters and Sorting
- Product List
- Product Detail Page
If you are still not sure how to proceed, please do not hesitate to reach out to your Customer Success Manager via chat, or check out the “DEMO”
The number of participants depends on many factors, such as devices selected, bug report language, test type, start time, and duration.
For instance, you might, unfortunately, face low participation if you run a Rapid Test in German on a limited set of devices with a specific iOS version late at night.
That said, a typical test cycle will entail around 40 testers.
You can run as many tests as you need at the same time.
If something on a website or in an application does not work as intended to, this “error” is called a bug.
Here in QA Supermarket, we use the following classification:
1) A Functional Bug is related to the intended function. For example, a button doesn’t submit a form as it was intended to the search doesn’t react to the user input the app crashes.
2) A Content Bug relates to the actual website or app content such as text, labels, pictures, videos, icons, links, data, etc. Typical content bugs are:
– Broken links or images (404s)
– Defective redirections in general
– Missing text, e.g., an empty tooltip
– Missing content, e.g., an empty content area
– Missing translations, e.g., a button on an English website having French labels
– Some products are missing in search results but the search function itself works.
3) A Visual Bug relates to the graphical user interfaces of websites or apps. For example:
– Layout framework problems, e.g., misaligned texts or elements
– A responsive design issue, e.g., an element is displayed on one mobile device but not on another
– Text or elements unintentionally overlap each other, are cut off, or not fully visible
4) A Usability Suggestion is feedback on the existing features, functions, or layout of your website or app and how to improve user-friendliness. For example:
“Link your phone number in the header to allow visitors to contact you easier” or “Add a ‘remove all’ button to the cart”
Software testing companies did not just appear out of nowhere. If every developer could hire QA specialists and work just as efficiently, no one would ever outsource. What are the advantages of using a specialized company over testing in-house?
1. DEVICES AND CONFIGURATIONS
Many bugs only exist on certain devices. They cannot be reproduced on emulators. Therefore, even your best tester will not find these bugs without the right device. Do you have a large stock of devices? We do!
Staff members only test their own projects. Therefore, they see a limited number of projects and a much smaller number of bugs. Our crowd deals with a much wider variety and encounters a large number of bugs. This means they can seek out and find bugs more efficiently.
Before a product release, functionality is urgently implemented, time starts to run out, and the volume of testing grows. The cost of a mistake also increases before a release. It is dangerous to make a bad first impression. Can you triple your staff of experienced QA engineers 3 weeks before release? Not likely. But you can start testing in any volume at any time and start fixing bugs in two days
Crowdtesting (or crowdsourced testing) is a practice that harnesses crowdsourcing efficiency and diversity for software testing. Software such as mobile apps, SaaS, native desktop applications, or websites in various development stages gets distributed to a large group of people, crowdtesters. They run software on their computers or mobile phones to inspect it for defects and areas for potential improvement. In QA Supermarket, these crowdtesters don’t need any specific scripts; usually, ask them to evaluate sections or features of an application using their experience and best judgment to unearth and identify problems. After being examined by a senior tester for quality, reports from testers flow back to the customer.
Product, development, and QA teams can use a crowd for such types of testing as regression, feature, usability, user story, cross-browser, accessibility, performance, routine sanity, and so much more. The power of crowdtesting comes from vast pools of testers with different skills, habits, experiences, and devices. Their broad hardware coverage combined with their human intelligence gives even fast-moving development teams real-world testing capabilities that wouldn’t have been possible a few years ago.
You can always calculate the testing price using the configurator on the Homepage.
QA Supermarket created the easiest way to test your software at affordable pricing. The routine work of processing and evaluating your project, which is usually done by a person, is excluded since all these steps are done automatically on our platform. That’s why we can provide you with high-quality but low-cost services.
To get an accurate price for your project you need only to add a link to your software and describe requirements (if any). Right after that, you will see the final cost.
While testing with QA Supermarket, you will receive:
1) Flexibility to test and pay only when needed.
2) Fast QA Service with a few-clicks start.
3) Professional manual testing by experienced crowd (real-user experience).
4) Detailed bug reports in real-time.
5) Low-cost but efficient QA resources on-demand.
You have to make only several clicks to start a test with QA Supermarket.
As soon as it is launched, you will receive bugs. It takes about 24 hours from payment to get the first bug report!