Background

At Ericsson, a team CI is responsible for continuous testing and integration of code. About 35 agile development teams depend on the test results, they need to know if the builds have been successful or if there are faults in the software. They get the results by email, with a link to a web interface, Maoni, where the test results are displayed in a table. The different teams are responsible for the different parts of the software but they all receive the same e-mail.

The current web interface is experienced as difficult to use, the users have trouble navigating, understanding it and the learning curve is steep.

UX Challange

My assignment was to significantly improve the user experience of Maini. I needed to understand how users used Maoni and to understand the mental model the users that chose not to use it. I observed users, asked them to think out loud and had a short discussion in the end.

I could see that two very different types of users were using Maoni. The developers and the managers. The developers needed to quickly see if the failure was due to bugs in the software or due to test bench problems. By making a quick call they could focus and spend their valuable time investing the right failures. The managers, on the other hand, wanted to get an overview of the quality of the software so that they could make decisions whether the quality of the software was good for the software to be released to customers.

The challenge was to design an interface that would meet the needs of both user groups. They the important information to be displayed in a simple way, but they also wanted to be able to dig deep and investigate issues by accessing the powerful database behind the GUI.

UX Solution

Based on the observations and the interviews with the users I decided to design multiple graphical views displaying the test results in different ways, but also keeping a generic view in form of a matrix where the user could access the whole database.

One of the graphical views, Program Overview, would show the latest test runs and all the teams. The managers could easily see the quality of the software, see how each team is doing and if they had a critical bug in their part of the software that would be immediate attention.

Another view, the Team View, is for the specific teams. The user chooses a team and sees if the software is the team that has been failing or not. The users can see failed and skipped test cases that belong to the team and history, comment and old bug-reports associated with those specific tests.

The Branch View will visualize the different release branches making it easier for both developers and managers to navigate.

And, the Matrix View would be the generic view with a table, table setting, and filter. I clearly separated the table settings and the filter, have noticed during the early observation that users would add a filter when intending to add a column and vice versa.

The users will also have their own settings where they can adjust their e-mail settings, save filters and get information about the latest updates.

Ericsson has a design system and UI components that I used when designing the interfaces. Dark theme is the preferred and default theme but can easily be changed via a switch.