07-15-2011, 01:49 PM
(This post was last modified: 07-15-2011, 02:00 PM by prachi.aug23.)
I ran the same script today and it worked ! Finally!
Time is a problem here though .
It took around 1 hour to convert OneNote to PDF for 2568 pages .
It printed pages from 19.5.2011 till date . I thought it will print just for today,15.7.2011 .Did I miss something to update in the script .
The pdf doc is open now , it shows the content upto 1568 pages , rest of the pages still loading for almost an hour .Its stuck after 1568 pages .
While running script , I got the message box as "0" , meaning success!
Now,I should again get a message box for :Was the PDFOkay? , which I didn't get yet almost 3 hours from the printing and script is still running.
I think its waiting for the content to be displayed in all 2568 pages.But isn't it a long time?
I closed the PDF and then it showed the message box :Was the PDFOkay? I clicked yes . Also, I do not see any log file generated this time.
Moving ahead a next step ,as you mentioned in your very first post about what to do once PDF is generated , my thoughts---:
1. To manually see it and then decide whether the checkpoint passes or fails? [One Manual Step] ---Manually we can see in One Note too , so skipping this option .
2. To just attach it somehow to the Report Results for archival and bug reporting? [Auto] ---As per my understanding , we attach the PDF to results , but verification part is again manual . And since there are many print actions , so if we verify the PDF at one shot , its time taking to first get the reference to the test it corresponds to and then verifying the data .
3. To automatically look for a specific string in the pdf to ascertain the success of the checkpoint? [Auto] --This is best approach once it is implemented .It allows to know the pass/fail status merely looking at the test result report .No debugging and no manual verification required.
Thanks again for all your efforts and time.
Time is a problem here though .
It took around 1 hour to convert OneNote to PDF for 2568 pages .
It printed pages from 19.5.2011 till date . I thought it will print just for today,15.7.2011 .Did I miss something to update in the script .
The pdf doc is open now , it shows the content upto 1568 pages , rest of the pages still loading for almost an hour .Its stuck after 1568 pages .
While running script , I got the message box as "0" , meaning success!
Now,I should again get a message box for :Was the PDFOkay? , which I didn't get yet almost 3 hours from the printing and script is still running.
I think its waiting for the content to be displayed in all 2568 pages.But isn't it a long time?
I closed the PDF and then it showed the message box :Was the PDFOkay? I clicked yes . Also, I do not see any log file generated this time.
Moving ahead a next step ,as you mentioned in your very first post about what to do once PDF is generated , my thoughts---:
1. To manually see it and then decide whether the checkpoint passes or fails? [One Manual Step] ---Manually we can see in One Note too , so skipping this option .
2. To just attach it somehow to the Report Results for archival and bug reporting? [Auto] ---As per my understanding , we attach the PDF to results , but verification part is again manual . And since there are many print actions , so if we verify the PDF at one shot , its time taking to first get the reference to the test it corresponds to and then verifying the data .
3. To automatically look for a specific string in the pdf to ascertain the success of the checkpoint? [Auto] --This is best approach once it is implemented .It allows to know the pass/fail status merely looking at the test result report .No debugging and no manual verification required.
Thanks again for all your efforts and time.