{"id":59066,"date":"2019-07-26T13:37:49","date_gmt":"2019-07-26T11:37:49","guid":{"rendered":"https:\/\/www.testbirds.com\/?p=59066"},"modified":"2021-10-08T18:39:45","modified_gmt":"2021-10-08T16:39:45","slug":"an-overview-testing-methods-for-online-shops","status":"publish","type":"post","link":"https:\/\/www.testbirds.com\/en\/blog\/an-overview-testing-methods-for-online-shops\/","title":{"rendered":"An Overview: Testing methods for Online-Shops"},"content":{"rendered":"
As you might have picked up already, in July we address E-Commerce testing a lot on our Testbirds blog. In the last weeks we already tackled down some different testing methods: we emphasized the importance of cross-device testing due to the ongoing mobile-shift<\/a>, showed how an Exploratory Bug-Test is executed<\/a> and explained how much optimisation potential lies in testing in general<\/a> (if you missed it: with crowdtesting we once helped a client increase his conversion rate by 30%!). In this week\u2019s e-com series blog post, we want to present you with a rather simple thing: An Overview. What are the most common testing methods for web shops. Whether if it\u2019s when creating an online-shop from conception phase to prototyping and to post-release stage, or also when the web shop is already running or a relaunch is planned.<\/p>\n Yes, an online-shop needs to have an appealing design with an outstanding portfolio of products and services. A solid structure that is intuitive and simple is equally important though, because websites that make it easy for users to navigate, are a necessity for success. To put it into marketing-terms: Customer-centricity is key, especially during conception phase. With a Testing Method called Card Sorting<\/a>, the customers\u2019 needs are included into the development process from the very beginning. The target group helps define an intuitive navigation and menu structure.<\/p>\n With Card Sorting, a representative tester group<\/a> of a client\u2019s target customers sort and categorise virtual cards to define a clear and logical navigation structure. Usually there are two different options: the 50-100 testers either receive topics and must cluster them into new topics, e.g. they create their own menu structure; or they receive pre-defined topics and must group different items and words under those topics. With both options the outcome is a comprehensive feedback towards clarity and structure, which gets analysed by Testbirds project managers who also formulate concrete recommendations for improvement.<\/p>\n Card Sorting in short:<\/b><\/i><\/p>\n A next step towards a well-functioning online-shop is prototyping. Whether if it\u2019s a click-dummy that contains the first versions of designs and navigation structures or even just first pictures and PDF files of the final website, a Prototype Evaluation Test<\/a> is outstandingly important, because uncertainty is a huge matter to contend with. Will the product be accepted by the target group? Are different features necessary and understandable? Operational blindness makes it nearly impossible for an unbiased view on the software, risking missing important details and developing an unsuccessful product. An effective way to gain some insights into the customers minds is asking the target group for constructive feedback before the development phase takes place. One common testing method to do so is by executing Remote Interviews.<\/p>\n In Remote Interviews<\/a>, the target group specific selection of testers share their screen and their thoughts in a video conference about a client\u2019s digital product. Normally in 30-minute sessions with one tester at a time. The client is able to remotely watch, communicate and guide the tester during the whole testing process and is so able to control the procedure by direct interaction. The biggest advantages of this test method is the flexibility and direct feedback that make readjustments possible even during the testing phase. The interviews get recorded and can be re-evaluated at a later point.<\/p>\n Remote Interviews in short: <\/b><\/i><\/p>\n With every online-shop<\/a> it is most crucial to make sure that functionality <\/a>and user-friendliness<\/a> are flawless and on par. Whether it is during the development phase or after release, or even if an online-shop is already running for many years, the most common testing methods are functionality tests and usability tests. We have clients, who need our help right after a relaunch of their online-shop, because the release was too error-prone due to a lack of testing beforehand. Another client had his web shop for several years, which looked fine at first glance, but still the crowd found 249 bugs on the site.<\/p>\n If a website does not meet the expectations of its users, or if users are unable to easily fulfill the intended actions, alternatives offered by competitors are often just a click away. Seemingly small features like headlines or an image next to the \u201cbuy\u201d button can have serious consequences. Therefore, aspects like text to image ratio can be hugely influential. Although developers and designers are experts when it comes to their company\u2019s software and digital products, they will never have an unbiased view due to organisational blindness. In a Usability & UX Study<\/a> feedback from the crowd regarding usability and user experience of a webshop gets collected by conducting up to 10 use cases with up to 5 qualitative and 8 quantitative questions. The tester group can be chosen from over 65 demographic criteria and of course is adapted to exactly represent a client\u2019s target customer.<\/p>\n Usability and UX Study in short: <\/b><\/i><\/p>\n It is no news how fatal it can be if the basic functions of a webshop don\u2019t work, especially in the ever-growing complexity of the device-landscape. The main purpose of the shop is to sell products and if this purpose cannot be fulfilled, well there is no reason for it to exist. Online-shops hence need to be extensively checked for functional errors and bugs on all devices. In a blog post<\/a> 2 weeks ago, we already explained how Exploratory Bugtests<\/a> are executed in more detailed, for this blog post, we hence stick to a short summary:<\/p>\n Exploratory Bugtest in short: <\/b><\/i><\/p>\nCard Sorting during Conception phase<\/h3>\n
\n
\n
Prototype Evaluation via Remote Interviews<\/h3>\n
\n
\n
QA and UX during Development and Post-release<\/h3>\n
Usability and UX Study<\/h4>\n
\n
\n
Exploratory Bugtest<\/h4>\n
\n