Test Quality Utility at USLI
This project is one of the best learning technical opportunities I've had.
​
The purpose of this application is to retrieve USLI's software deployment information from Azure DevOps and have it in an interface that makes reading the data easier for developers, automates sending emails, and shows the developers on schedule, among other features.
​
What I have been working on was displaying the information regarding the software deployment releases on the homepage. Keep in mind that this project was a blank page when I started!
The information for the application directly comes from USLI's Azure DevOps pipelines. I will focus on the release pipeline with the ID # of 10, shown on the right.
​
Below is a screenshot of the URL for this pipeline. Notice the Definition ID is specified as 10. This is the collective ID for the releases within this "Databases - Test" pipeline.
Let's pay attention to the first release in this pipeline. This release has a unique Release ID of 85281.
​
These are the statuses of the "release environments" within this release:
When clicking on the release, you can see more details for each release environment. See how the statuses (4 gray and 1 yellow) correspond to each other in both screenshots.
​
While the statuses of the latest deployed release in the pipeline is definitely important for developers to know, the status of the last completed deployment prior to the current release is also important for them to know. This gives the developers a better understanding of the overarching issues in the pipeline. This is further elaborated on below.
This is what the home screen looks like immediately after opening the application. Each release loads in asynchronously.
Each of these headers represents the releases from Azure. The dropdowns contain information about the "release environments."
Here is the pipeline ID of 10, as seen earlier. Notice the corresponding Release ID of 85281 within the header.
This is what the release environments of Release 85281 looks like on the TQU app. These slides break down each row and compares it to Azure.
Pay attention to this part of the table! There is a limit set to how far we want to go in the release pipeline history. This number is customizable in a configuration file.
The rows with failures show up before the other rows in the table!