Skip to main content

Difference between UI and UX in software testing

I lately noticed that there is some confusion going on around the software testing in regards to user facing parts of the system. Testers mention that they are planning to “run some UI testing” or others speak about “strange UX on that system”. I would like to spent some time today and emphasizing the main 3 differences between UI and UX and how we are testing each one, and by whom.
But let’s start from the beginning what is UI and what is UX?
UI is a User Interface, usually referring to anything that can be visually seen by the user when interacting with the system. That will include colors, page design, logos, element shapes, etc.
UX is a User eXperience, usually referring to anything that can be done by the user when interacting with the system. That will include what can be clicked, what can be done, what will be returned back to user and in what way, etc.
With that understanding we can now define the 3 most important identification points for each one

UI - User interface

  1. Visual Design
  2. Branding
  3. Layout

 UX - User experience

  1. User Stories
  2. Personas
  3. Usability


From the above we can clearly see that for a functional tester there is really nothing to test in the UI section and a lot to do in the UX. While the Content, Marketing and Design departments of the software product will have to spent considerable amount of time to verify UI elements compliance with branding guidelines, proper resolution, visual presents and so on. Those need to be tested in different environments and resolution to verify proper presents on all expected devices, all that without any emphasis on functionality of each component but mostly on how well it looks and feels on the screen.
On the other hand functionality of each visual component will have to be covered by proper testing department to verify that it all according to expectation and matching the pre-defined user stories for each scenario. Usability of the components usually is being tested by the representatives of the users, and the business defining the possible user personas that will be using the system and proper testing will be required to verify that those pre-defined personas can accomplish all the required tasks on the new system in an acceptable manner.



Comments

Popular posts from this blog

7 Most Popular Test Types in Software Testing

Today we are going to return back to basics of software testing and discuss the 7 most popular test types that are being used in every software testing effort. Those different test types cover all the levels of the software to make sure that the final result matching the expectations from every possible angle. Here is our list: Unit testingSmoke testingRegression testingFunctional testingIntegration testingUser Acceptance TestingPerformance Testing


Now let’s have a deeper dive into each one of those by using a simple example of an imaginary system that was created in order to manage warehouse activity including shipments, inventory and goods receptions from suppliers.
Unit Testing This type of testing is usually performed by the developers and is covering the very basic development component. In this test developers are testing the straight forward functionality of a functional piece of code to make sure that it is performing according to their expectations. In our example: This test w…

Story Points estimation for Scrum with Fibonacci vs Shirt Sizes vs Linear - 7 minute guide

It is all began long time ago when Development Teams were constantly asked to provide estimate and they were having a hard time to properly face the task. Let's admit it, there are so many things that can change, happen, and simply go wrong during the development process that one can hardly expect a proper estimation of hours for each task. That why a relative estimation with Story Points came along.

Story Points Estimation
Its a different way to estimate the effort of the Scrum Development Team with-in Agile methodology, which means that instead of estimating hours of work the team estimates each effort relatively to other efforts in the project.
Let's assume that a developer knows that specific 'Task 1' is much harder than another 'Task 2' it is hard for him/her to quantify that harder feeling in hours of additional work but it is possible to say that it much more work. This situation is being address by Story Points when each story point is representing som…

What is the velocity of an Agile scrum methodology?

Let's discuss some of the important measurements in Agile, and that is the Velocity of the Scrum team work.
Based on Wikipedia definition Velocity is " ...the rate of change of its position with respect to a frame of reference and is a function of time...", which when transferred to the scrum world can be summarized as: The amount of work that the scrum team completed in a single measure of time - in a sprint.

How we Calculate Velocity?
Velocity is actually a very simple to calculate, it is done but totaling the number of story points of fully completed user stories from the sprint backlog. So if a current sprint included 4 user stories: 2 with 8 story points each, one with 3 story points and one with 32 story points. and by the end of the sprint the 32 one was not fully done the velocity calculation will be:
8+8+3=19
Note: the 32 story points are not part of the velocity calculation as this user story was not completed.

What Velocity is used for?
The velocity is used i…