I don't show my Ranorex reports to anyone but my direct supervisor, and then only when he asks (which isn't very often!!
). My QA director doesn't want to see them, the manual testers just want to know if it passed or failed, and the devs just want to know why it's broken if it fails.
So I have my tests all report their final status to my DB (all my data is in SQL Server) and I have a dashboard build in MS Lightswitch HTML that anyone can use to look at actual scenario results, manage data sets, and queue Jenkins jobs.
Note: My tests are VERY dynamic, in that certain test cases do or don't run based on what the current scenario/data set requires. I manipulate the SQL data connectors at runtime to force the queries (I use stored procedures for everything) to bring back just the data for this particular scenario and test case combination. For instance, my testing is against our Point-of-Sale (POS) system. So each scenario is a collection of transactions that are all related (for example: purchase something -> fulfill the purchase -> return a part, is one scenario). So, at the end of each transaction, I report to the DB and then aggregate all the transactions in each scenario.
For Jenkins this means that I also have some very specialized Groovy scripts that collate data to make sure the job starts the right set of store/AUT combinations. And then I pass that info to Ranorex so it knows what test scenarios to run in any given configuration.
** I'm in the process of rewriting much of this right now because the dev team has moved to TeamCity and we are being told to do that as well so everything is integrated. TC doesn't do things the same way as Jenkins, so if we go through with this I basically will have to recreate much of the Jenkins server-agent architecture. It's a pain to retool, but I love the development side, so I'm having a blast!
Edit for grammar
Shortcuts usually aren't...