Our typical process

1.

It begins with a conversation

Software testing is a process designed to uncover and communicate information about a product’s quality. To best assist you in publishing quality products, we first need to understand your reality, your process and your goals. As such, the first step is to talk, to get to know each other and to mutually validate that we’re a fit.

2.

We adapt our services to your development process

From large multiplatform projects to simple websites, no two projects are alike. Moreover, every development team has a preferred way of working and we know how challenging it can be to modify this process. When you work with us, we designate a single individual to be your point of contact. This person is an internal, full-time employee of our company based in Montreal, Canada. On average, our project managers have 7 years of testing experience. They can assist you in preparing test cases, discuss the ideal test strategy for your project, and manage the entire process for you from A to Z.

We do not require you to work any differently than you do now – we adapt to your process. As practioners of the context-driven school of testing, we adhere to the notion that your testing team should serve your project, not run it.

Whether you require sporadic ad hoc testing between sprints or ongoing assistance throughout your project’s lifecycle, we’re here to help, when you need it. Whether you work with Jira, Lean Testing, Test Rail or Excel, we’re flexible. What works best for you is what works for us.

3.

We deliver the most value in short, focused rounds of tests

To get the most value from crowd testing, we recommend multiple short rounds of testing, each with a clear goal. Instead of testing an iOS application on all the iOS devices, consider testing multiple iterations of the app each on a subset of devices. We have found this way of working to be easier to manage and that it allows our partners to really see how their products are progressing over time.

Of course, different projects have different needs. We regularly work on testing projects that require anywhere from 1 to 60 testers. The most we’ve ever done is 400 testers testing a project. A typical round of testing takes about 48 to 72 hours, but it can be longer or shorter based on the testing mission. This is something you can discuss with your project manager. They’ll be able to guide you.

The bugs that are reported by our testers are submitted to our proprietary bug tracking system, Lean Testing, which is free to use. Before they become visible to you, they are reviewed to ensure that they are: a) valid b) complete and c) well-written. We strive to deliver a clear and concise list of results that your development team can immediately tackle without any back and forth.

4.

Results and next steps

When a round of testing is completed, you receive a detailed test report. This report highlights the test strategy that was chosen, the issues that were found and precious information about the overall state of your project. You can then export the list of bugs to your preferred bug tracker, or work directly in Lean Testing to assign tasks to your team.

You do not have to evaluate the testers that participate nor do you have to manually re-invite them. We take care of that for you. Of course, we’re eager to get your feedback on the process and to constantly find ways to improve. We encourage you to make the time to talk with your project manager, discuss the results, and talk about next steps. Maybe they’ll recommend holding off until some of the important bugs are resolved. Maybe they’ll recommend more tests on different platforms. It’s up to you to decide what to do next, but we’re always there to assist you in the decision making process.

How Crowd Testing helps ensure software quality

1.At the prototype phase

When you've got a solid functional prototype ready, we can assist organize focus groups to uncover valuable feedback before you get too far in the development. We regularly design and administer usability studies for a diversity software products ranging from ecommerce sites to mobile applications.

2.During the development phase

As your developers are completing portions of your final product, it can be beneficial to test them before your team turns the page. Our testing team can focus exclusively on the new features, immediately when they are ready to go!

3.Prior to launch

The bulk of the testing effort generally occurs shortly before launch. (This is called "Integration testing.") Once your product is in a near-final state, we'll recommend exhaustive tests on every meaningful platform in your target market. This part of the process typically requires a few rounds of tests to ensure that your audience is delighted when your product is released.

4.Post launch

Work doesn't stop when you publish an app or site. It fact, that's just the beginning! Your users expect regular updates and improvements. We work with a lot of agile teams who require testing help between and during their sprints. We can thoroughly test your updates before you publish them to ensure that the new features function as expected and that the existing features haven't been affected by the modifications that were made.

No two software projects are alike. Let's talk about your ideal scenario.