Originally published on Medium
A decade long in Quality Engineering and Test Automation and my observation has been that, something that is generally missing when it comes to Test Automation is the visibility. Yes! You heard it right. The Visibility!
It is often the case that the technical aspects do not matter much, as much as the non-technical ones.
At times, I even got a feeling that Test Automation was becoming the responsibility of only the QAs when every member of the team is responsible for the Quality aspect. And the reason for that was as well missing Visibility of Test Automation at times. Since you don’t see whats going on day to day basis, you don’t hold yourself responsible for it. And at times, don’t see much of value in it as well. To an extent —
Out of Sight, Out of Mind.
One of the first and the foremost thing that the team practicing Agile believes in is Visibility. Visibility in the form of Story Walls, Barometer (To track overall sprint progress), Build Monitors, Burn down Charts, Ice-cream Meters (Who is attending Stand ups on time and who is not) is very common among the team practicing Agile.
Visibility of automation is not only important for Quality Analysts or Test automation engineers but for every member of the Scrum team i.e. BAs, Devs, UX Designers, Product Owners, Product Managers and Business Stakeholders. Test automation metrics are direct indicators of the health of the product and hence hold very high significance. Metrics help making effective decisions.
The first Test Automation dashboard I had created was exactly a decade back using Jsps and MySql. Post that, I had been using Spring Boot, MySql and UI framework from time to time. But, with the rise of Node.js and the mammoth rate at which the JS frameworks are coming up, this time I thought of exploring something beyond the traditional stack.
As, I was exploring various options, something that grabbed my attention was Cube.js. I looked at some of the examples usecases on the Cube.js website. Looking at the live demos, I realized that this is what I was looking for. Had a quick glance at the documentation and found it to be neatly organised, detailed and up to mark. Joined the Slack channel to see how is the support and it was pretty good. Almost, all the queries answered with a descent turn around time. My personal experience — I asked two queries on the Slack channel and both were resolved within minutes.
So to be precise, what Cube.js needs from its user is solid understanding of your database. And it does heavy lifting in terms of wiring or chaining the components. A bit of plumbing gets the show up and running in few hours if not minutes. In less than two days, I created this Test Automation Dashboard. Database that I have used is MySql. Database schema is as in the snapshot below.
Let us have a look at each of these tables -
- TbExecution — This table holds the details about the test automation execution. Every time, test automation execution is triggered, a new Execution entry is added in this table.
- TbFeature — This table holds the details of all the features in a particular product.
- TbTestplan — This table holds the details of the testplan in all the features. The relationship here is many to one i.e. one feature will have multiple testplans.
- TbTestcase — This table consists of all the testcases that belong to all the testplans. The relationship here is many to one i.e. one testplan will have multiple testcases.
- TbExecutionDetails — This is the table that holds the execution results of all automation runs. It has the execution status of every testcase in a testplan across features executed during a specific test automation execution.
One of the basic things about this entire set up of MySql and Cube.js is, it is Test automation framework agnostic. Meaning, irrespective of you using TestNG-Selenium or TestNG-RestAssured or Jasmine-Protractor or Mocha-SuperTest or any other framework of your choice, all you got to focus on is updating the MySql database post the end of the automation execution. As long as, the underlying language used for test automation is able to connect to the MySql database and update the results post execution, desired charts/metric will be displayed by Cube.js.
Test Automation Frameworks in different languages updating the results in MySql database
The goal behind creating this Test automation dashboard is to answer some of the questions regarding the overall test coverage. Questions like -
In last 5 automation executions, what is the overall test case pass percentage?
- In last 5 automation executions, what is the overall pass to fail test case count in the total test cases executed?
- What are the total test cases executed, pass, fail and pass percentage for last 5 executions?
- What are the the total test cases executed, pass, fail in a Test plan in every Feature?
Now that, we have understood, what was the goal behind coming up with this dashboard, let us take a look at its folder structure. The database schema and the folder structure can be cloned from here. Folder structure is as in the snapshot below.
In the cloned git repository, additional folder that you see — mysql-schema is the one that holds the MySql database schema. That is the sample test data along with the database schema that we will be using to generate the charts as in the snapshot above.
Step 1: Verify if Pre-Requisites are properly installed -
a. NodeJs & npm
Step 2: Set up the “testautomationresults” database using the “testautomationresults.sql” file from “mysql-schema” folder.
Step 3 : Git clone the repository using the command below
git clone https://github.com/Shreyasc27/testautomationdashboard-cubejs.git
.env with appropriate MySql details
cd testautomationdashboard-cubejs npm install npm run dev
As in the cmd above, open url
http://localhost:4000. Development environment as below will be displayed.
For further exploring this development environment, refer to the document on the Cube.js website.
cd testautomationdashboard-cubejs\dashboard-app npm install npm run-script npm run-script build
Running above commands will generate a
build folder in
cd build npm install http-server -g http-server
Copy the generated “build” folder to any other directory
The software industry moves fast. But if you keep up, you can have an incredible career.