8 Reasons to Save your Automation Results in Database
Most of the frameworks have a reporting system where the reports are written onto html or text files. While this might be useful for easy viewing of the result, it may not be enough in all cases. For applications with large number of regression test plans, there arise a need for easily accessible historic results. Having your test results saved into a database will help you in this regarding.
Why Save your Automation Results in Database?
Build trend graphs and tables
Previous execution results saved in database can help build trend graphs and tables which could be used to analyze the application health over time or release/build.
Automation Results in database can be used to automatically categorize the types of failures. We can identify a set of failures caused by a bug and tag those test cases with the bug number thus enabling us to see the effect of each bug on the application over each build.
Historic status of individual test cases
We will be able to see the historic status of individual test cases thus getting information like when or which build a particular test case has started failing, or when a previously failing test case has started passing etc.
Categorize test plans for easy analysis
It enables us to automatically categorize the test plans based on any criteria like testplan owner, functional area etc. This enabling easier analysis for the test plan or functional area owner.
Combine different execution results into one
There can be cases where multiple executions(for different test plans or functional area) are made on a single build and consolidating the results into one result can be a real pain. By having the results in database, it becomes easy to combine the results of multiple executions into a single result.
Enable rerun of failed test cases
In our framework, we have a feature to rerun just the failed test cases for the same build. Since the result data is stored in database, the results of the rerun just updates the previous result(same build/execution) while maintaining an audit trail.
Full control of the result data
We have full control over the data and by querying the database, we can to find any type of failures or other data.
Build an Automation Dashboard
We can build a Dashboard over the database to create a centralized reporting suite incorporating all the information provided in above steps. This could be a web application and/or a mobile application with takes data from the database.
- Selenium WebDriver Cheat Sheet
- 3 Things to Avoid in Test Automation
- Selenium WebDriver Tutorial Series
Let us know in the comments below, which other reasons makes you save your results in the database.