Writing an application specific recorder
I am working with a mature MFC application that currently supports automation through COM, and am trying to evaluate the advantages of developing a custom event recorder within the application. The application currently includes a scripting engine, but not a recorder. Microsoft products do this to some extent, through macros, but the recorder is not great.
We have an existing customer requirement to add functionality to log all user actions and input data to a file for audit purposes, so my thinking is, why not make this an annotated, replayable script file, rather than a simple text log. I see the following pros and cons for this;
We will have a recorder that works at a high enough level of object abstraction that it will produce robust, readable scripts for functional testing purposes.
End users get a facility to record and replay scripts / macros.
We get a great mechanism for automating demos and tutorials, capturing defect specifics, etc..
It will cost a lot more to develop than a simple event log. All the COM interfaces will have to become identical to the corresponding GUI interfaces.
It will involve significant change in the way we use our existing testing tools, although GUI testing will remain pretty much the same.
My question is has anyone gone down this road before, and if so, what are the pitfalls that I am missing?
Re: Writing an application specific recorder
Note sure but if possible I would just go for a simple event log and develop a script to process the log seperately.