Tag Info

I work for a small company with four developers and two testers. Our product is a web-based application that we deploy to Amazon EC2. The application targets holders of a special kind of bank account. I will describe the process we use with external participants, i.e. with participants who are not our employees (we also run informal usability tests with ...

They can - and should be. Sit with the designers as they develop their wireframes and prototypes. Help them out with their scenarios and personas. Make yourself a cardboard iPad and try out the layouts - see here for a real world example ( and an aside, I dont really understand what the difference between QA testing and usability testing is - well I sort of ...

I have worked in two different scenarios: a large project to develop a scheduling app for a government agency and an established commercial product. In both, usability was integrated into the testing but in very different ways. For the large development project, we invited local representatives from the customer into our test lab during development (i.e. an ...

My answer is 2 parts, first in direct response to your question: You should definitely keep usability in mind while testing your product. Just because the product matches the specification, does not mean that it is intuitive, simple and concise. If it's difficult for you to understand or use, then you can pretty much bet it will be even more difficult for ...

I've been involved with all of the above. In my first QA role, I managed a team that was responsible for ensuring compliance to UI Standards. At another company, we did somewhat formal Usability Testing, bringing in existing customers to explore the application's usability in an inexpensive manner: ...