Introduction
We perform testing on the features of an application to understand its behavior and try to enhance its functionality and logic. But do we perform testing on the UI part too? Yes, We must perform testing on the UI part because the first thing the users notice is UI. If the UI is not good, even though we have a responsive and perfect functionality, the users may not feel like using it. So to understand the UI, we first build a user flow and then perform testing. Let’s discuss user flow in this article.
UI User Flow
User flow represents the steps or actions that a user needs to go through or actions they perform on the website to access and use it. We must understand the entire project to prepare a User flow diagram. We define the user flow by considering three factors
- Conditions - a particular role or action done by user.
- States - a GUI component.
- Actions - physical interaction of user that changes state.
Let’s take an example of a homepage on a Social Media App/website.
Here, the homepage is a state, and the actions possible are; login/Sign in and register/Sign up with similar designs.
When the user clicks on either option after filling in the details, it will land them on a dashboard page. Now we have four pages/states.
- Homepage
- Login page
- Register page
- Dashboard
The user flow will look like this
This user flow diagram explains all states on a website and the actions performed at each state till the last state.
7+ registered 
