Thursday - Reporting and Learning

It's Thursday - an important phone call at 10:00, and then back to the reporting.

groovy & jenkins & reporting

groovy is a language that is employed in the jenkins workflow.  What I find interesting is that build results and testing results need to be modified to fit the situation.  

In one case, I'm using pytest and I need  to extract specific information from that to feed to my influxDB system.  Then, that data is taken in by a grafana dashboard to display the status of builds.

Although I have managed to get the reporting data for robotframework results, I will finish up the edits to report in a consistent fashion.

A future client will dictate their needs for reporting output.  In my previous work, each layer of management from lab tech to CEO require different data.  The key is to find a satisfactory view for all parties.  At times, this will require different view dashboards for each party.

Ideally, a consensus can be reached and only one dashboard is required.

Today's activity is to unify the reporting to align to one standard set of results to view for each of my projects.

This unification will involve:

• total tests
• test pass count
• test fail count
• build SUCCESS 

This way, a consistent report can be produced. 

Going forward, a third project will be added in (gtest) and fortunately, this process should go much smoother.