Ranorex Forum

Hiya,

The Ranorex Log file is nice, but is limited when you want to analyze ALL validations from ALL tests for a release cycle. To do this you will have to manually open each log file, and search... not nice.

My feature request, and its something we have done ourselves here, is that we use the Ranorex log for messages only, and output all validation results to an Oracle database.

We then have a client tool, whereby you can view/sort/group/filter all validations accross all tests, and export to Excel/PDF too.

As far as I know, most automation vendors seem to forget that analysis of results is the main point about testing, and therefore don't offer ways to centralise results storage and analysis. As Ranorex is already a great product, adding this feature would make it even better!

Just a thought!

Until now, Ranorex has concentrated its efforts on the automation side of UI testing, e.g. a good object recognition. With the next major versions we would like to improve our testing features, e.g. better support for data-driven testing. Writing to and retrieving data from databases is a key requirement for data-driven testing; saving reports to databases fits into the data-driven approach, so I added a feature request to our database

Actually, the Ranorex Reports class already allows attaching new kinds of loggers to it (see Report.AttachLogger method). You just need to implement the IReportLogger interface so that the new logger stores log messages in a database. Then you attach that logger to the Report class. From then on all your Report.Info or Report.Warn statements will be forwarded to the new database logger and thus stored in the database.

Regards,
Alex
Ranorex Support Team

ok sounds good...
In terms of data model of validations results, when using Report class you get properties:

-Date
- Level
- Category
- Message

It would be great to assign arbitrary number of properties to a log entry that can be passed to the custom logger. For example items such as:

- Product
- Version
- Module
- etc.

We are already planning to extend the reporting functionality in our next major version
Better structuring and custom data will be definitely in there. So if you have any further thoughts on the subject, please do not hold back

Michael
Ranorex Team

atom wrote:It would be great to assign arbitrary number of properties to a log entry that can be passed to the custom logger.

BTW, you can already to that, too. Just implement the IReportLogger.LogData method in your custom logger and use the Report.LogData method to pass your custom properties to the logger.

Regards,
Alex
Ranorex Support Team