Anyone Want an Automation Results Dashboard Utility?

Experiences, small talk, and other automation gossip.
User avatar
Ciege
Ranorex Guru
Posts: 1335
Joined: Thu Oct 16, 2008 6:46 pm
Location: Arizona, USA

Re: Anyone Want an Automation Results Dashboard Utility?

Post by Ciege » Fri Feb 03, 2012 6:56 pm

I've uploaded a new version (0.15a) that will remove that trailing \ automatically if it finds one... So now you should at least be able to see the name "Debug" (which is the name of the root folder) in the main view of the utility.
If this or any response has helped you, please reply to the thread stating that it worked so other people with a similar issue will know how you fixed your issue!

Ciege...

let
Posts: 17
Joined: Wed Oct 20, 2010 7:00 pm

Re: Anyone Want an Automation Results Dashboard Utility?

Post by let » Tue Mar 06, 2012 5:52 am

Awesome awesome tool. I was looking for a quick implementation for getting/sharing results files and this is going to work great for what I need. Thanks for making this available!

User avatar
Ciege
Ranorex Guru
Posts: 1335
Joined: Thu Oct 16, 2008 6:46 pm
Location: Arizona, USA

Re: Anyone Want an Automation Results Dashboard Utility?

Post by Ciege » Tue Mar 06, 2012 3:51 pm

let wrote:Awesome awesome tool. I was looking for a quick implementation for getting/sharing results files and this is going to work great for what I need. Thanks for making this available!
Hey, thank you for that... Glad that it is working out for what you need!
If this or any response has helped you, please reply to the thread stating that it worked so other people with a similar issue will know how you fixed your issue!

Ciege...

atom
Posts: 357
Joined: Sun Dec 07, 2008 11:14 pm
Location: Dublin, Ireland

Re: Anyone Want an Automation Results Dashboard Utility?

Post by atom » Tue Apr 10, 2012 7:19 pm

I was thinking of taking the tool we use and publishing it
We created a TestResult class that has properties such as:
- Test Name
- Product
- Module
- Version
- Execution Result (Pass, Fail, Error)
- etc.
And we save it to Oracle (pretty easy to convert to MySQL say)
We then also save the ranorex log file + other output files to Oracle blob (from a .zip)
We then developed a dev express client to view all results from Oracle (filtering, sorting, grouping etc.)
Once the result is generated we added a workflow for manual investigation, for example test is executed and produces Fail, the investigation workflow means we can assign the failure to a tester to investigate, and the tester can add comments against it, and an investigation status. As for us we generate 5000+ results per release, so tracking failures and who is investigating them, and how many left to investigate is quite important.
Sound useful?!
We called it (Automation Result Storage and Evaluation = ARSE for short :D )