Can someone help me with a query I have regarding the testing of data produced within Excel.
To be precise, I have a Excel spreadsheet with a macro that allows the user to enter some parameters and click a button, which performs some calculations and returns some data. It's this data that I want to validate and in such a way that the test asset is easy to maintain and it can report any unexpected data within individual cells
I've currently automated the launching of Excel and written to the registry to disable the macro security warning; however, I would appreciate some advice as to how best to test the data:
1. Should I do a file comparison against a pre-defined Excel file?
2. Or programmatically validate each individual cell?
I've been using the script extension successfully for Office 2003; however, I noticed that it says it is not compatible with Office 2007. The problem is our test environment uses Office 2007. Is there any way to extend this script extension to 2007?
Sure. Extract the code from the extension and make the modifications. :-)
The tcx file is, essentially, a ZIP compressed file. Change the file extension from tcx to zip and open it up in your chosen tool. Then extract out the source code, make the modifications to it, drop it back in the zip, rename the zip again back to a tcx and you're good.
Of course, doing so means that you've altered the code supplied by someone else (in this case, SmartBear) so they can't be held responsible for any mistakes your code may have. But this is the beauty of script extensions in that they are, for the most part, open source code.
Automated Testing Evangelists
Definition expert - noun - Unknown drip under pressure