NOTE: User Acceptance Testing (UAT) and Regression Testing are a part of the RedstoneXperience project methodology and included in every Redstone WebCenter Project. Usability Testing is an additional service provided by Redstone that we will cover in today’s edition of WebCenter White Board.
Usability Testing measures the degree of ease with which a software product or Web application can be used to achieve required goals effectively and efficiently by assessing the level of difficulty involved in using a user interface.
User Acceptance Testing is the last phase of the software testing process where actual software users test the software to make sure it can handle required tasks in real-world scenarios, according to specifications.
Regression Testing is a type of software testing used to determine whether new problems are the result of software changes.
Definitions by http://www.techopedia.com/
Help us help you. Help us help you. Hey everybody and welcome to another edition of WebCenter Whiteboard with Redstone Content Solutions. My name is Michael Lawrence. I'll be your host today. We're going to talk about usability testing and helping us help you. It might sound a little familiar. It's a famous movie line from Jerry McGuire that Tom cruise said. We felt it was a great title for today's video on usability because not a lot of companies approve of usability when it comes down to software projects and budgets and timelines. They don't see the value there so we're going to talk about helping us, a software consulting company, help you with usability to improve your ROI, on your projects.
To understand what usability is, you've got to understand what usability isn't. What it isn't is a test of user. We aren't testing how well they can use the website or do they know where to go or how to use it. It's not their fault. What we are trying to do is test how well the website or the software tool communicates desired actions to the user. For example, can the user see the “learn more” if it's just in the text form or is it better as a button?
Next, we're going to talk about how this process works. How do you go from changing text to a button or changing the color? So you're going to create the software, the tool. Then you are going to test it. You are going to have users whether they are internal, external, or temp employees. You are going to have them go through the software. You are going to give them desired actions you want them to take, or processes to go through. You are going to see how well they can get through them on their own.
You are going to use this. You are going to test this. Once you create it you are going to test it. After you test it you are going to improve it. Users had a hard time seeing the “learn more” and they didn't know how to go to the next page or the next part of the workflow. So you are going to make it a little bit bigger. You are going to change the color. We are going to make it a button because buttons say “click me” versus text maybe read, click, is a hyperlink, you don't know. You are going to turn it into a button. Once you do that you are going to repeat. You are going to have the users test this with the new button. You are going to see how many users can get through to the next level. This is just a little basic idea of what usability testing is.
I think its wash, rinse, repeat. Once you create it, test it, improve it, you are going to repeat, test it again. It's going to be an interative process and you’ll want to do that through the entire software development life cycle, which I will cover why in a couple of seconds here. There are various amounts of different testing you can do. There are A and B testing, where you have layout 1 versus layout 2 or you can just change one thing at a time a little bit here, a little bit there, but the most important thing is you have to have a comparative benchmark. You have to have a base score and then grade and score your changes, your improvements versus your base score. That's a little overview of what usability is and how you can test it.
Now, we are going to talk about what happens due to a lack of testing. A lot of times you are going to end a software project with broken software. It’s not going to work, pages might be missing, hyperlinks might not work. They might lead to the wrong page. You might have people being navigated to dead ends with nowhere to go. It might be a little confusing. Another thing you are going to do is jeopardize timelines as a result of the broken software. You are going to get to the end of the project and you're going to discover all these issues because you haven't been doing usability testing but the project ends in a week and you have 20 problems that you weren't expecting to have to deal with this week which is also going to jeopardize your budget. So do you pay people overtime to get these done? Do you jeopardize the timeline and push it back some more? What gives? Something's got to give. You've either got to live with the changes, pay more money or move the deadline.
What this is going to do is diminish your credibility. If your website is not working, your customers are going to be upset. For example, if you are in ecommerce and your shopping cart has some glitches or if it's constantly reloading or it’s navigating dead ends that they don't want to go to or they can't find the information they want.
What usability testing is going to do for you is it’s going to give you the ability to fix them now. Instead of finding these mistakes at the end of the project, you are going to be able to find them as you go and fix them as they come up before they can escalate and get worse, and dealing with them one at a time versus twenty or so all at once at the end of the project when stress level is already high. Fixing them as you go is going to allow you to finish on time. You are going to come to the last week of the project timeline and you're not going to have a backlog of issues because you fixed them as they came. This can lead to finishing under budget, saving money, saving time, and finishing under budget. All are great benefits. The end result of this is going to be satisfied customers.
You're going to be satisfied because you allowed companies like Redstone to come in and do our job and do it effectively. Test it, improve it, repeat, repeat. Then you are going to have satisfied customers. Your customers are going to be satisfied because the software works for them. The bottom line is usability is going to improve your ROI. You are going to finish on time under budget. You are going to have a better software, happy customers, more ecommerce buys, more website visits, longer time spent on the site. There are a number, number, number of benefits that come from usability testing — super important; one of the reasons for the video today.
I hope you enjoyed it. If you have any questions, comment below. Look forward to chatting with all of you and remember Redstone Content Solutions, we deliver. Have a great day.
| || || |