Testeum.com – Application crowdtesting platform

Case study : Gondwana Hotel

Bastien SERAFIN — Wed, 17 Jan 2024 22:52:05 +0000

Test with users from abroad

“Gondwana Hotel” are two hotels located in Noumea, New Caledonia. They are the first eco-friendly, cultural, and artistic hotels in New Caledonia.

The management team decided to update the related website, for both modernizations, and to attract Australian visitors.

Meet the family: at Gondwana City Green and Gondwana City Art

Gondwana Hotel is a family business with two establishments where it is good to rest while respecting the environment. The Gondwana Hotel City Green, 3 stars, is the first hotel certified High Environmental Quality Overseas. The Gondwana Hotel City Art is a 2 stars establishment offering accommodation in Noumea and offers an immersion in the Caledonian artistic universe through 24 rooms embellished by local artists, showing their unique and authentic works. One can find within the hotels a multitude of services to fully enjoy a stay.

Gondwana Hotel challenges:

Gondwana Hotel relied on a digital exposure to attract foreign guests, especially from Australia, New Zealand and Japan. Despite the website to be completely translated into English, and some efforts put on SEO, online ads and third-party booking platforms, traffic and conversion rate were a bit disappointing. Hotel team especially had doubts regarding UX and about the English translation of the website, while not having any real options to test this with foreign users.

Testeum Solution:

The stakeholders in the project were Gondwana Hotels, as the solution customer, and Tealforge web agency, their local supplier for developing the website, providing a link to the application Testeum. We provided Gondwana Hotel with a turnkey package including the test copywriting, the test campaign management, and the finalized test reports delivered to both the Tealforge development team and Gondwana Hotel.

During the test campaigns, users are invited to give structured feedback, pointing out any issue with the UX or translation. This allows the Hotels Gondwana team to review the message on the website and gives a good basis for discussion with the development team.

Details:

Audience: 5 English speaking users, from Australia.

Conditions: The testers installed a screen recording app to share their actual journeys during the tests.

The alternatives to Testeum services are:

Friends or family: get one’s relatives to test the release candidate.

Focus group: use a marketing agency to gather people matching audience criteria.

Development team fully responsible for the testing.

Detailed benefits:

Actual feedback from a specific audience: especially from people you couldn’t interview.

Fresh eyes from testers: real world feedback like end users would do.

Increased confidence in the application, resulted from this feedback from potential users.

Traffic and conversion increase: for Australian users by a 4 factor.

Conversion rate also doubled, getting direct sales more important than third parties booking platforms.

KPI’s

Costs:

700 € for a turnkey offer.

Included :

4 hours of project management,
1 Test campaign for a 30 minutes journey done by 5 testers.

Duration:

7 days to complete the campaign.

Results:

28 bugs, including 17 suggestions on site UI or UX related features.

L’article Case study : Gondwana Hotel est apparu en premier sur Testeum.com - Application crowdtesting platform.

Improve UX through user testing

Bastien SERAFIN — Wed, 08 Nov 2023 03:24:23 +0000

Shareflat is a French startup which provides students from Western Europe with a small ad platform. This platform creates unique flat rental opportunities for students willing to set for a mid to long term period. Shareflat used user testing to smoothen both sides of the user journey on the platform.

Meet Shareflat : the innovative flat sublet platform

Shareflat, was founded in France by Mathis and Tom. They’re both students and faced some issues to find cost effective flat rental services when switching from their business school during a couple months through a student exchange program. They had the idea to share small ads for flat sublet services, which are perfect for students switching from one campus to another for a couple months, and not willing to definitely change their flat rental.

Shareflat challenges :

After a couple months since the platform went online, Shareflat had some great (and justified) review in media but even with traffic peaks, founders noticed that user retention was low. They suspected that some friction points existed in the user journeys, and they wanted to pinpoint these.

Shareflat also has a promoter score challenge, with this niche service not being famous on their market so founders wanted to test proof the content of the website to check whether the value proposition was clear or not.

Finally, some new features had been released right before the test campaigns, and Shareflat wanted to check their implementation.

Testeum Solution :

The stakeholders in the project were Shareflat founders, since they develop and maintain the platform themselves, and Testeum. We provided Shareflat with a turnkey package including the test copywriting, the test campaign management, and the finalized test reports delivered directly.

After the test cases editing, and the campaign launch, the platform just notifies the testers matching Shareflat criteria, with cherry-picked profiles. Thus, very few resources are committed to running tests with Testeum, test reports are directly shared with founders, and the test report structure also allows to check some hypothesis on UI/UX and clarity of content.

“We needed some feedback about our UX, and new features. Testeum testers did a great job at pinpointing some issues from UX in different user journeys.”

Details :

Audience : 10 French speaking desktop and mobile users, from western Europe countries.

Conditions :

The testers had to switch role from answering a small ad to posting a new one.

The alternatives to Testeum services are:

Friends or family : get one’s relatives to test the release candidate.

Focus group : use a marketing agency to gather people matching audience criteria.

KPI’s

Duration :

8 days total: with both campaigns happening on the same time.

Results :

33 bug reports, including 14 suggestions on app UI or UX related features.

Costs

350 € for a turnkey offer.

Included :

2 hours of project management
2 Test campaign for a 30-minute journey done by 10 testers.

Detailed benefits

Fresh eyes from testers :

Real world feedback like end users would do, especially on some content.

Remarks from testers in real time reports,

allowed to challenge the user interface.

Increased confidence

in the application, resulted from this feedback from potential users.

L’article Improve UX through user testing est apparu en premier sur Testeum.com - Application crowdtesting platform.

Crowdtesting Uncovered: Testers’ Perspectives

Zoé Thivet — Tue, 17 Oct 2023 04:52:50 +0000

In the dynamic software testing landscape, crowdtesting has become an essential practice, harnessing the collective power of skilled individuals around the world. Among the ranks of these testers are Olaitan Majekodunmi, Kevin Jubin, and Devillers Poaty-Meaty, each of them bringing their unique expertise to Testeum’s testing community. In this article, they give their personal testimony about their experience in crowdtesting. We’ll delve deeper into their motivations, their evolution, and the deep connection they make between their daily work and this dynamic testing ecosystem.

Kevin and Devillers have been testing apps via Testeum for years now, and Olaitan for a few months.

The three of them perform some software testing in their jobs (from time to time for Kevin, and as a specialty for Devillers and Olaitan).

What were your initial motivations for getting into crowdtesting?

KJ: Being able to test apps and get paid for it is really great, so I was immediately interested.

DPM: I was motivated by the desire to contribute to the improvement of software products by reporting issues and providing constructive feedback. I especially wanted to gain experience by testing various types of applications.

OM : I started crowdtesting because I wanted to find a technology specialty that I would like participating in.

“Being able to test apps and get paid for it is really great, so I was immediately interested.”
Kevin Jubin

What are your motivations now?

KJ: Being recognized as a good tester. It was even validating to see myself at the top of the leaderboard on the website (even though I’m not anymore because of a big test where several of my bugs were invalidated, grr).

OM: When I discovered website testing, I found out that it’s a niche that I really understood perfectly and I didn’t struggle to understand it. I enrolled in numerous courses related to it and applied for jobs. Technology is the future, so I need to make sure I participate in it. The money from crowdtesting also encourages me.

DPM: I am now motivated by the desire to ensure software quality and contribute to end user satisfaction.

“I am now motivated by the desire to ensure software quality and contribute to end user satisfaction.”
Devillers Poaty-Meaty

What link do you make between your job and crowdtesting?

OM: Through crowdtesting, I am able to develop new skills, such as improving my ability to understand and communicate with others. I am also able to expand my understanding of website testing by learning about the many types of website testing.

DPM: Crowdtesting allows me to acquire new skills and improve my expertise in the field of testing. I have gained experience in various technology domains by working on a variety of projects. Crowdtesting trains me to detect bugs, evaluate the user interface, understand client requirements, and ultimately develop strong communication and adaptability skills.

KJ: I work in HRIS (Human Resources Information Systems) and we have tests to do very often. It allowed me to develop good reflexes on Testeum.

“Through crowdtesting, I am able to develop new skills, such as improving my ability to understand and communicate with others.”
Olaitan Majekodunmi

Do you have a funny bug anecdote that made you laugh?

DPM: I have quite a few. One of the bug anecdotes that made me laugh the most was a bug with a numerical field. It was impossible to input numbers using the numerical keyboard, but I managed to bypass it by activating the voice keyboard. When dictating the numbers, the field didn’t show an error even though it should have. It was funny to see the developers dictating numbers to reproduce the bug.

Who would you advise to get started with crowdtesting?

OM: I would recommend this to those who are aware of changes and willing to learn new things because no one has all the answers. Additionally, I’ll suggest it to those who are good communicators.

DPM: I would recommend crowdtesting to anyone starting out in testing, looking to gain experience, and who enjoys a challenge. I would also recommend it to people with experience in testing who have been on the same project for a long time.

KJ: I think that as long as a person is conscientious, it doesn’t matter if they’re in the field of IT or an experienced tester; they can get into crowdtesting. One of the important aspects is user experience, and ultimately we are all users.

Conclusion

In the field of participatory testing, Olaitan, Kevin and Devillers exemplify the spirit of innovation and collaboration. Their experiences transcend simple testing; they represent a commitment to advancing software quality, enriching user experiences, and continually upgrading their skills. To those embarking on this journey, take their advice, because in this global network of testers there is a place for anyone who is passionate about shaping the future of technology.

Join Testeum if you wish to live your own crowdtesting adventure!

Featured image: Midjourney

L’article Crowdtesting Uncovered: Testers’ Perspectives est apparu en premier sur Testeum.com - Application crowdtesting platform.

Case study : Topicks

Bastien SERAFIN — Wed, 13 Sep 2023 04:47:07 +0000

Improve UX before app release

Download the case study Topicks

Topicks, a new social network mobile application, went through an exciting development project.

Testeum assisted Topicks in improving the UX, UI, user retention and features from the app right before its release, with a comprehensive software QA based on a global reach with targeted users and environments.

Meet Topicks: the new social network application.

Topicks, founded is Australia, is a new mobile app for social networking.

The idea was that many people between the ages of 35 and 45 were abandoning social media because there were too many ads. They tend to create private groups to discuss points of interest. At some point, the idea came up to create an innovative social networking app, with two main principles: to be topic-oriented, instead of person-oriented, and to include benevolence by design, without the possibility to despise users’ comments.

Topicks challenges:

By the end of the development phase for the MVP, the goal was to have a workforce of people genuinely interested in testing the app, with global reach, and the ability to provide suggestions for improving both the UI and functional aspects, which is – generally speaking- impractical to set up.

The risk of not doing so was that the app would not suit its audience and would be quickly abandoned by users. That’s where Testeum comes in.

Testeum Solution:

The stakeholders in the project were Topicks, as the solution customer, their supplier for developing the software, providing a link to the release candidate of the application, and Testeum. We provided Topicks with a turnkey package including the test copywriting, the test campaign management, and the finalized test reports delivered to both the development team and Topicks.

After the test objectives editing, and the campaign launch, the platform just notifies the testers matching Topicks criteria, which really eases the connection with testers. Thus, very few resources are committed to running tests with Testeum, test reports are directly shared with developers, and the test report structure also facilitates communication between Topicks and the development team.

Finally, Topicks team can prioritize development tasks based on their vision.

Details:

Audience: 10 English speaking IOS users, from a dozen countries.

Conditions: The testers installed a screen recording app to share their actual journeys during the tests.

The alternatives to Testeum services are:

Friends or family: get one’s relatives to test the release candidate.

Focus group: use a marketing agency to gather people matching audience criteria.

Development team fully responsible for the testing.

Detailed benefits:

Fresh eyes from testers: real world feedback like end users would do.

Remarks from testers in real time reports, allowed to challenge the user interface.

Increased confidence in the application, resulted from this feedback from potential users.

Cheree, founder of Topicks

“I needed testing services with a global reach. Testeum services were seamless and very efficient.
It made the communication with development team much easier”

KPI’s

Costs:

530 AUD (315 €) for a turnkey offer.

Included :

2 hours of project management,
1 Test campaign for a 30 minutes journey done by 10 testers.

Duration:

12 days total: the request of 10 testers, and the conditions on screen recording increased the campaign duration, but with first feedback in less than 6 hours, development team could quickly take it into account.

Results:

21 bugs, including 12 suggestions on app UI or UX related features.

L’article Case study : Topicks est apparu en premier sur Testeum.com - Application crowdtesting platform.

10 Types of bugs that Testeum will help you find

Zoé Thivet — Wed, 13 Sep 2023 01:08:03 +0000

Here is a top 10 list of bug types that Testeum can help you to spot before publishing your software.

1. Functional Bug

This is the most well-known type of bug, so let’s start with it!

A functional bug is simply a bug that will make your users say: “It’s not working.” It could be a button that does nothing when clicked, a link that leads to a 404 error, or a calculation that doesn’t happen correctly.

How about an e-commerce website that applies taxes twice instead of once?

With Testeum, crowdtesting is a cost-effective way to spot bugs… that will truly bug your users.

2. Portability Bug

Has your company invested in test phones to control how your website looks on mobile devices?

We have some bad news for you. That’s not sufficient to ensure that the site displays correctly for all your users.

But the good news is that crowdtesting can boost your confidence level as it allows you to launch your app in contexts you might not have considered. Older phones, lesser-known browsers, unique configurations (have you thought about testing your display in dark mode on your phone?) Each crowdtester tests with their environment and habits, which reveals bugs that your testing team might never have found.

3. Localization Bug

If your application is intended for a global audience (or even just multiple countries), it’s essential to ensure that localization works correctly.

Translation errors, cultural missteps (example: using the metric system in a context where it’s not in use), or data formatting issues (example: a website intended for a French audience where it’s impossible to use accented letters like ‘é’ or ‘è’) can harm the user experience and put off your target audience.

Crowdtesting can help you identify these localization-related problems and ensure that your application is tailored to different markets you’re targeting.

4. UX Bug

According to your criteria, your application may not be buggy. But from the perspective of someone with fresh eyes, what’s displayed may be incomprehensible, leading them to conclude ‘It’s a bug’. That’s what we can call a UX problem.

If your application deviates too far from the common experience expected by your target audience, they may disengage and silently leave your service. This is what hurts the most when users leave without explaining why!

With crowdtesting, you can be assured of obtaining feedback in line with what users would provide.

5. Error Handling Bug

This is a specific case of usability bug. Users aren’t perfect: they make mistakes in input, skip essential steps, etc.

It’s crucial to think about the most common errors to guide the user back onto the path that brings them value. The problem is that these errors are difficult to be anticipated by the design team or your internal testing team.

By exposing your product to a representative population, Testeum also allows you to understand the errors your future users will make and manage them effectively.

6. Input Data-Related Bug

This is a specific case of a functional bug. Your testing team has undoubtedly tested your forms and various screens by entering all kinds of data. However, this data may not necessarily be representative of what your final audience will enter when the application is in production.

Crowdtesters often use data that is similar to what will be used in real-life situations. They have data sets that you didn’t anticipate. Last names with potentially unsupported characters, documents in different formats than you had planned, etc.

A striking example is presented in this TEDx talk: a black person had to use a facial recognition service and discovered that it didn’t detect their face. The testing team for this product certainly hadn’t trained its model enough with faces other than white ones.

Crowdtesters bring diversity and unpredictability to input data. Don’t underestimate this value.

7. Accessibility Bug

If a crowdtester tells you ‘We can’t see what’s written’, don’t take it lightly; it’s an accessibility bug. If the contrast between text and background is insufficient, or if the font is too small or too unconventional, it creates reading difficulties for a more extensive range of people than you might imagine.

People with permanent vision problems, people who forgot their glasses, or even simply those who have a headache!

8. Concurrent Access Bug

This is a specific case of a functional bug.

Your testing team checked that it was possible to view or modify a resource in your application, but did it test whether this resource could be viewed or modified simultaneously by several people?

By involving multiple testers who don’t know each other and don’t coordinate, Testeum creates test scenarios that your application hadn’t experienced before. This is how new bugs are discovered, and this is how product quality can improve!

9. Performance Bug

Your testing team didn’t detect any performance problems, but perhaps that’s precisely because it’s your testing team.

Crowdtesters will use your application in different contexts where performance problems are more likely to occur. They will use 3G, or even slower networks. They will use the application from different geographical locations or on less powerful devices.

Keep in mind: to achieve top performance, proactive anticipation is crucial before taking the production plunge.

10. Security Bug

Security vulnerabilities are a major concern for any company offering digital services.

Even though crowdtesters primarily represent your target audience (and your target audience does not include hackers!), it’s possible for one of them to discover a vulnerability.

It’s then up to you to fix it; prevention is better than cure!

By using Testeum, you can anticipate many issues and thus ensure better engagement from your future users.

Check our blog for other articles.

L’article 10 Types of bugs that Testeum will help you find est apparu en premier sur Testeum.com - Application crowdtesting platform.

Catch all those bugs!

Zoé Thivet — Wed, 13 Sep 2023 00:10:49 +0000

1500+ qualified crowdtesters with you 24/7

That's what Testeum is all about!

In just a few clicks, our platform lets you launch a test campaign.
Load your scenarios, choose your environments and the desired profile of your testers, and off you go!

Accessible to all budgets (VSEs, SMEs, startups and major accounts), Testeum aims to revolutionize crowdtesting.

Got an application to test?

Expect to catch a lot of bugs!
Registration is free; no card number required.

Want to join the team instead?

Testeum favors an ethical model for remunerating testers!

L’article Catch all those bugs! est apparu en premier sur Testeum.com - Application crowdtesting platform.

Crowdtesting a Caledonian Mobile App

Bastien SERAFIN — Wed, 19 Jul 2023 23:48:46 +0000

They created an app, Testeum tested it.

In 2023, we decided to offer a test campaign every month to an innovative project in New Caledonia, the country where our platform was first developed, and to which we are eager to give back.

In this article, we will share the testimony of the team behind the first project to use Testeum in this context, namely the “Domaine NC” mobile application.

Who are you ?

I am Adrien Sales, I’m the product manager of “Domaine NC”, and I am Laurent Schaeffer, the developer of this mobile app.

What is your app for ?

LS : Simply put, this mobile application is used to view the domain names in New Caledonia in a mobile-friendly and compact manner. It allows users to view information about a domain name and receive notifications when it’s about to expire.

AS : We have created a disruptive user experience to facilitate a management process that was previously done manually… with the risk of forgetting to renew the purchase of the domain name. This can have a significant impact on our digital business because if your domain name expires, you disappear from the web and lose visibility, or even worse: transactions. We wanted to highlight the value of this data and its’ potential.

What are the quality risks of this application ? What could go wrong ?

AS : One of the risks is having a suboptimal or overly complicated user experience. We were also worried about having poor response times… or even worse : no response (for example, a nasty 500 error) !

What questions did you want the crowdtesting campaign to answer ?

LS : We needed to make sure that each user could easily access the information they were interested in.

AS : Indeed, we wanted to ensure ease of use for a novice user. We also wanted to know if our performance was passable, good, or excellent (we aimed for instant search and display).

How did you organize your test campaigns ?

AS : First, we defined a very limited scope of features based on our MVP through a dedicated milestone on GitHub. Then, we organized a very simple first test campaign to get feedback from testers on this perimeter.

LS : After fixing bugs reported during this first testing session, we launched additional test campaigns: one for each feature.

What did you think of the crowdtester's feedback ?

LS : We discovered a different perspective from ours, which allowed us to improve the application on a UX and functional level.

AS : We discovered very relevant test scenarios. For example, one person searched for the maximum size accepted by our domain name input field. Some tests even allowed us to improve the security of our API! We had new ideas to simplify usage, such as adding placeholders to guide users.

We also received feedback on a pure functional bug : the automatic search was supposed to happen only after 3 characters were entered, but that was not the case. We therefore improved the app’s speed and reduced the number of API calls.

How did you find the platform itself ?

AS : The dashboards are beautiful and very easy to understand! Everything is ready to use. We were able to copy and paste them as is to organize our teamwork with very little effort.

LS : The platform is easy to use and allows for optimal organization of campaigns.

In your opinion, how should a crowdtesting approach be articulated with other testing practices ?

AS : From what I’ve seen, I think crowdtesting allows you, for example, to test release candidates or betas in real-world conditions (on a target infrastructure). For instance, I was able to measure the impact on the performance of the API and see if the entire chain was holding up well: it was really end-to-end! Awesome and tremendously effective.

I would like to see an organizational description that integrates crowdtesting with all other testing phases, and appear in the release planning.

I think that running a crowdtesting campaign with Left Shifting would make sense in a LEAN approach, which prioritizes Time To Market, quality, and more generally the entire delivery chain. We implemented a complete CI chain that allowed us to deploy the version on stores with a simple button press, literally. Thus we can focus on compact perimeters and quickly close loops with high software quality. We did everything via GitHub/Fastlane cloud tools.

What advice would you give to someone considering a crowdtesting approach to test their product ?

AS : I would advise them to :

Raise awareness with their team : present the key concepts of the platform to the team and sensitize them to Left-Shifting. They can show examples of crowdtesting campaigns : wins, failures, very concrete examples. They can also present approaches (one big test campaign vs. several small ones) and share testimonials.
Sensitize the team to the fact that testing a feature is part of the development costs… and therefore must be taken into account from the beginning.
When designing the test campaign, propose a complete journey to make the most of the platform (ROI).
Have a Product Owner (PO) with a very clear product vision.
Involve the team (Devs, Scrum Master) so that crowdtesting is a project phase like any other… If possible, include complete newbies to the team who know nothing about the business domain.
Bonus : create a user club for those who have used the platform and create a guide of best practices together.

Oh, what is shining on the ground ? A lamp ? HA, here is the Testeum genie, you can make 3 wishes for new features on the platform !

LS : Do we have 3 each ? I’ll make 2 for myself:

1) The ability to export test data to other platforms (like GitHub for example) or in JSON format, and

2) Provide an API to retrieve test data and/or other data from the platform.

AS : I’ll make 3 wishes !

1) Being able to trigger webhooks to create issues automatically (GitHub issues for example) or trigger workflows (IFTTT, Zapier, Power Automate, etc.), in an event-driven mode, or as a part of CI chains.

2) Provide an API to consume feedback and campaign data for B2B integration or reporting purposes.

3) Being able to target professional QA profiles (in addition to current criteria : age, gender, country, and type of owned equipment).

Thanks to Adrien and Laurent for this testimony !

L’article Crowdtesting a Caledonian Mobile App est apparu en premier sur Testeum.com - Application crowdtesting platform.

How to integrate crowd testing into your quality strategy ?

Bastien SERAFIN — Fri, 02 Jun 2023 05:11:41 +0000

Testeum is a crowdtesting platform that offers several direct advantages :

Real-world testing in realistic environments
Portability testing
UX testing
Internationalisation testing
Geolocation testing

But it also offers some indirect benefits, such as the possibility of acquiring new users who know your services perfectly !

However, questions remain that prevent some organizations from taking the plunge : how does it work in practice ? How can crowdtesting be integrated into one’s organization and quality process ?

How does crowdtesting work ?

Simply put, on one side, we have an organization and its’ digital service (website, mobile app etc), and on the other side, tech lovers looking for extra income. Crowdtesting consists of connecting these two groups in a relevant and organized way, using a crowdtesting platform. The platform allows organizations to broadcast their tests and allows testers to provide their feedback : successful tests, failed tests, bugs found, and so on.

For example, on Testeum platform, dashboards are available and updated in real-time as tests are run by crowdtesters.

What crowdtesting platform to choose ?

This matter will obviously have a considerable impact on your crowdtesting journey ! There are currently many platforms, each offering its own specificities and added value. Testeum cannot be the judge of course. But we promise this is the only question in this article we won’t attempt to answer.

What can crowdtesting actually test ?

The offers may vary, but in most cases, functional tests, usability tests and portability tests are the most frequently offered.

When to deploy crowdtesting ?

When you already have relatively good confidence in the quality of your version, crowdtesting allows you to find the bugs that may have escaped you, and/or that you would not have been able to find internally. It also allows you to improve your internal testing strategy, as what is discovered during the crowdtesting phase can help you level up your regression tests.

Crowdtesting can also be deployed earlier, but be careful to still ensure sufficient quality: it would be unfortunate to receive bug reports that you could have easily spotted yourself !

How to choose scenarios to be tested ?

Obviously, the first scenarios you should choose are critical ones : “If this feature doesn’t work, we’re screwed !”

End-to-end tests are excellent candidates for crowdtesting. Some general test goals examples :

Sign up on the website,
Complete your profile,
Browse the items,
Use the search engine of the website,
Make a payment,
Check the invoice.

Also think about tests that are not automated, or difficult to automate.

How to write tests for crowdtesting ?

First guideline : keep it easy to understand.

First and foremost, it’s important to keep it simple. Crowdtesters who will access your product may not necessarily be familiar with your field of expertise. Therefore, it’s important to explain any specific vocabulary.

If your website is intended for the general public, such as an online store, the risk of misunderstanding is relatively low, but be careful with web jargon ! For example, the term “modal” is not well-known by the average person, and it might be better to use the term “popup” (even if it’s not exactly the same thing) to ensure everyone understands. Similarly, words like “breadcrumb,” “footer,” “widget,” should be expressed with simple terms.

Second guideline : keep your tests independent

This good practice is valid for both crowdtesting and other testing contexts.

Each test case must be able to be played in any order, without affecting the other tests. If you have a test case, for example, “Creation of a user named Yummy,” do not have another test case “Deletion of the user Yummy.” Otherwise, beware of the snowball effect if the first test in the series fails!

Playing tests in any order is a worthwhile exercise. It is also interacting with the application in a way that is closer to reality; in production, users follow their own path and take steps in the order they want, which is not necessarily the one we had imagined.

Also, keep in mind that the same test case could be played by several different testers. Pay attention to the related constraints :

duplicates (multiple people may try to create the user “Yummy” and receive an error message “This user already exists”)
concurrent access (on some websites, it is only possible to have one active session per user, with an automatic logout system).

Is crowdtesting relevant for testing B2B services ?

Of course ! Crowdtesters are there to carry out test scenarios, and if they are specific enough, there is nothing stopping you from having your B2B services tested by them.

In a wider perspective, getting feedback from users outside of your marketing target can be very interesting; for example, it could make you aware of certain problems that you have not yet encountered in production, but which could arise later if you open up to other audiences or geographic areas.

We can't find any more bugs internally, what can crowdtesting bring us ?

You have tested to the best of your abilities, within a limited time frame, with limited resources, and undoubtedly some biases -as we all have! Crowdtesting allows you to break free from these material and intellectual limitations: your service will be tested on a range of machines of all brands, sizes, and years, by people from all walks of life.

The bugs found during crowdtesting campaigns are therefore as varied as they are unpredictable.

Here’s a juicy example. One of our crowdtesting campaigns revealed that on a website, a certain button was clickable using a mouse, a trackpad button… but not with “tap-to-click” !* No one had found this bug internally, yet the feature had been in production for a few weeks and seemed remarkably stable. Was that infamous button the “Pay My Order” button? The story doesn’t say… but just imagine !

To get down to business we recommend reading this feedback, which recounts a crowdtesting experience with Testeum. Happy reading !

* “Tap-to-click” is a feature of laptop trackpads or touchpads that allows you to click on an element by simply tapping on the pad, rather than pressing a physical button.

L’article How to integrate crowd testing into your quality strategy ? est apparu en premier sur Testeum.com - Application crowdtesting platform.