It is rare to see a website without a form that you will use for contact or to register. The interaction on this type of web pages requires a lot of processing when you have to check the validity of the user input. This article explores the testing of web forms from the usability perspective.
Using patterns of yore (like Martin Fowler’s supervising controller, effective use of presenters and view model state), this presentation discusses the everyday really annoying impediments to user interface(UI) testing. You will learn what parts of the UI need testing and effective ways of testing them.
Without a full user-centered process, performing a usability test at the end of the development process merely serves to highlight the unacceptable nature of the design. It’s a sad and frustrating result, but there is usually little that can be done except to release the poor design.
With Selenium and Jenkins, you can extend Selenium processes to include screenshot comparisons, enabling automatic UX compliance at the speed of your Continuous Integration workflow. Learn how to compare screenshots from one Jenkins run to a repository of known quality, in order to insure that not only does your website work well, it also looks well.
2Q2U (Quality, Quality in use, actual Usability and User experience) is a specific model used to evaluate the quality of the User Experience (UX) of a mobile application. This article presents a way to use the model and step through the process of doing a real evaluation on the road to improving a mobile application’s usability and UX.
A Model Based Approach To Evaluating and Improving Mobile User Experience was the first article of Philip Lew that introduced the context that creates the need for a model-based approach to evaluate mobile user experience. This article presents the concepts of the ISO 25010 model and 2Q2U (Quality, Quality in use, actual Usability and User experience).
With the increased importance of targeting mobile devices in the software development world, we need better tools to assess the quality of the user experience (UX) on these devices. This article introduces the context that creates the need for a model-based approach to evaluate mobile user experience so that different software, or versions of the same software, can be evaluated in a consistent way.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates