Enhanced printing support
I think it would be nice if TestComplete/TestExecute had additional support for printing and verifiying "printed" values.
On the current automation project I am working on, we have coded a solution that works OK, but would be better if SmartBear added additional functionality. There were items that required some time to work around, but would have been much easier with more support built in.
The first thing that would be nice is if TestComplete/TestExecute had an integrated virtual printer. The printer settings could be specified in the project settings and controlled programmatically through TestComplete. Controlling the settings through TestComplete would allow the test to guarantee consistency of the settings across all PC's executing the test via TestExecute. Settings can be problematic if they are specified manually prior to test execution (were the correct options selected). In my project, we used SnagIt and consistency of its options had to be manually configured and verified (ie, the TIFF output had multipage, 24 bit, and RLE(packbits) set).
An integrated virtual printer could also guarantee (or close) consistent output and operability across OS's. A built-in funtion(s) to allow interacting with the printer (provide a printer name, filename for saving, etc...) would be easier to use. Also, any errors encountered while attempting to print could be returned for handling. In my project, we automated the Print dialog (printer selection, clicking print) and the Save-As dialog (we used the function for saving a file after learning about it). Occassionally, SnagIt encoutners an error "unable to open message queue". This requires us to stop the test and open and close SnagIt. The test needs to be restarted. If there was an error status returned, we could easily build in logic to have the test flow around it.
Lastly, it would make it easier to create check points involving the output of a print job. In my project, we printed the report to SnagIt as a multipage TIFF. I wrote code to to split out each page individually, used TestCompletes image comparison functions against each page, and kept track of the overall pas/fail of the report. There was a fair amount of "glue code" and C# required to accomplish this. The image comparison functionaity made it "easy" to verify the contents of the report (it was an image already and it wouldn't have made sense to attempt to use PDF files) (we required the use of transparency, masking, pixel tolerance, and color tolerance to handle variable portions of the reports and for slightrendering differences).
Smartbear wouldn't need to develop their own printer, they could integrate an open source printer or partner with someone else for it.
On the current automation project I am working on, we have coded a solution that works OK, but would be better if SmartBear added additional functionality. There were items that required some time to work around, but would have been much easier with more support built in.
The first thing that would be nice is if TestComplete/TestExecute had an integrated virtual printer. The printer settings could be specified in the project settings and controlled programmatically through TestComplete. Controlling the settings through TestComplete would allow the test to guarantee consistency of the settings across all PC's executing the test via TestExecute. Settings can be problematic if they are specified manually prior to test execution (were the correct options selected). In my project, we used SnagIt and consistency of its options had to be manually configured and verified (ie, the TIFF output had multipage, 24 bit, and RLE(packbits) set).
An integrated virtual printer could also guarantee (or close) consistent output and operability across OS's. A built-in funtion(s) to allow interacting with the printer (provide a printer name, filename for saving, etc...) would be easier to use. Also, any errors encountered while attempting to print could be returned for handling. In my project, we automated the Print dialog (printer selection, clicking print) and the Save-As dialog (we used the function for saving a file after learning about it). Occassionally, SnagIt encoutners an error "unable to open message queue". This requires us to stop the test and open and close SnagIt. The test needs to be restarted. If there was an error status returned, we could easily build in logic to have the test flow around it.
Lastly, it would make it easier to create check points involving the output of a print job. In my project, we printed the report to SnagIt as a multipage TIFF. I wrote code to to split out each page individually, used TestCompletes image comparison functions against each page, and kept track of the overall pas/fail of the report. There was a fair amount of "glue code" and C# required to accomplish this. The image comparison functionaity made it "easy" to verify the contents of the report (it was an image already and it wouldn't have made sense to attempt to use PDF files) (we required the use of transparency, masking, pixel tolerance, and color tolerance to handle variable portions of the reports and for slightrendering differences).
Smartbear wouldn't need to develop their own printer, they could integrate an open source printer or partner with someone else for it.
