43% of all order cancellations of online purchases are due to technical malfunctions.<\/strong> This statistic<\/a> makes it abundantly clear how often not even the basic functions at webshops are working. It also makes me want to bluntly state the following: Through thorough webshop testing and respective UX optimisation, the number of online orders can be increased<\/a> by a maximum of 43%.<\/p>\n
We use the help of a global online community<\/a>, that tests software under real conditions for user-friendliness (Usability and UX<\/a>) and functionality (Quality Assurance<\/a>) issues.\u00a0In one of our former blog posts we wrote about the importance of cross-device testing of webshops<\/a>. Of course, a flawless UX<\/a>\u00a0across all devices is crucial, especially due to the on-going shift in purchasing towards mobile, but what\u2019s even more important is that the basic functionalities of a webshop actually need to work. In this post, we want to explain how exactly this can be tested.<\/p>\n
A common approach to test the functionality of a webshop is to execute an Exploratory Bug Test<\/a>. The website <\/a>gets tested with user stories and predefined tasks while still allowing testers to maintain the freedom to complete each step their own way. Every detail of the testing procedure is documented by the crow. This process of testing outside of laboratory environments helps discover the bugs that lead to the most common errors encountered after a product\u2019s release.<\/p>\n
What exactly the crowd tests, is planned by one of our Project Managers together with the respective client. Based on the structure of the online shop and predefined testing goals, they develop user stories and tasks and set the test up in our testing platform, the Nest<\/a>. The Test script could look something like the following:<\/p>\n
Use Case1 | Overview<\/em><\/p>\n
Use Case 2 | Product Search and Filter<\/em><\/p>\n
Use Case 3 | Detail Page<\/em><\/p>\n
Use Case 4 | Add to bag<\/em><\/p>\n
Use Case 5 | Buying a specific product<\/em><\/p>\n
Use Case 6 | Registration<\/em><\/p>\n
Use Case 7 | Login<\/em><\/p>\n
Please try to log in with your new account from use case 7.<\/p>\n
Use Case 8 | Account<\/em><\/p>\n
For a webshop test it is just as important to choose the right tester group in order to make the results as relevant as possible for the respective target group of the clients online-shop. For the right size and selection, our project managers choose the candidates with over 65 criteria from the crowd and examine, which testers suit best for a specific test case. Demographics such as age, gender, income but also information about testing devices, testing experience, specific shopping preferences etc. can be important criteria for building the tester group, that at the end matches the target group of the client.><\/p>\n
\u201cCrowdtesting has proven to be efficient. We can start testing on a Monday and see the results on Tuesday. It\u2019s a powerful addition to our development process.\u201d <\/em>,said Lieven Swinnen, Manager e-Business Landal GreenParks<\/p><\/blockquote>\n
Once everything is set up, a test can be executed relatively fast. The first results are often already there after 1-2 days. The raw data are accessible for the client as well and the testers make screenshots\/videos, that document technical problems and mark down every bug they find during the Exploratory Bug Test of the webshop. The final results are then consolidated and summarised by the project manager in a final test report.
<\/p>\n
Benefits of Crowdtesting<\/a><\/h5>\n
According to Hobson&Company<\/a>, Crowdtesting<\/a> can lead to an increase in customer retention rate by 10%<\/strong> – evidence of how effective it can be to include crowdtesting into your testing processes as an ongoing solution.<\/p>\n
What other beneficial impact Crowdtesting <\/a>can have on both the efficiency within your testing processes and for your business, we will share with you in another blog post next week.<\/p>\n","protected":false},"excerpt":{"rendered":"