What is done in user testing, and how different versions of browsers tested?
User testing is when real people test out the interface and functionality of websites, apps, products or services and provide feedback. This is a helpful process to go through before launching a new website as the feedback can be used to make sure how it looks and functions facilitates the experience developers are hoping their user is experiencing. Feedback on the entire experience is generally gathered, including users' emotions, responses, and behaviors from the beginning to end of using the website. In this process is also usability testing. Whether or not the website is usable is determined by if the user can navigate and/or use the website easily while reaching the intended purpose in using the website.
Surveys and focus groups can also be used to gather data either to help determine what data is most important to gather when testing the website, or data that helps provide information on what is working better than intended, as intended, or not as intended on the website. A developer can also utilize A/B testing when user testing, which involves sending two versions of the website to two separate groups, gathering feedback to see which version is meeting the intended experience or goal for the website better.
One important part of user testing is testing across multiple browsers, called “cross-browser testing”. This type of testing is critical to knowing the user experience is not only wonderful but consistent no matter what browser the user is using, even as technologies keep evolving and changing. This process can be done manually or through automation, and involves testing the website across different types of browsers and different types of devices. It also includes testing the website for accessibility with assistive technologies.
Cross browser testing begins with a list of what features are going to be tested on what browsers and what devices. This list can be developed by analyzing what browsers and devices are most popular, as well as analyzing what has been used to access the website in the past (if not a brand new website). A baseline is determined and then the testing is executed either manually or through automation (automated interactions with the website through code). When testing how the website works on multiple operating systems, testers can use emulators/simulators or have a device lab of their own (or one available remotely). This testing is often done during development, and in the staging/pre-release stage.
Sources: