06-04-2007 08:35 AM
06-05-2007 03:43 PM
06-05-2007 11:18 PM
Hi
I thank you for the suggesstion. Though I have seperate sequence files, I cannot run them in parallel as there would be resource conflict. My requirement is that the sequence calls in the main seq should execute step by step. At the end of execution it should generate seperate report for each sequence call steps executed.
When I enable 'run in new execution', the sequences starts to run in parallel. I want the flow to be in sequential steps, yet generate seperate reports for each step.
Regards
Gopal
06-06-2007 01:37 AM
Hi,
I think you would have to modifying your Process Model sequence file and maybe the report generation sequence file as well.
In the Process Model the steps that occur to generate the report are:
1 A step to determine the FilePathName - this uses the information obtained from the Report Options.
2. A step which calls Report.Reset ("") - which clears the report.
3. A step which calls Report.Reset (Locals.Report) - Locals.Report holds the current report text obtained from Test Report.
4. A step which calls Report.Save() - which save the report to the current file which was setup by the call in step1 above.
5. Finally, a step which calls Report.Load - which loads the report into the operator interface / Sequence Editor Report window.
Therefore, you are going to have to do as a minimum is steps 1,2, 3, 4. What you display at the end of the test for step 5 is a problem because clearly you may still what to display the complete test run not just the last test.
Also what you may consider, is what header and footer does each report have, and is the information available, or is there extra information that you will have to provide somewhere in your test sequence.
The Results for each top-level steps are contained in Locals.ResultList[] these will need to be stripped out so that you can then pass to the Test Report callback to generate each report.
Although what you might consider, is leave the Process Model to generate the normal report but modify the report generation sequence file to generate the extra individual step reports.
Regards
Ray Farmer
06-06-2007 09:43 AM
I just want to point out that when you call a subsequence in a new execution, you can specify the "Wait for Execution to Complete: Before Executing Next Step" option on the Execution Settings dialog box. This way you can get separate reports without introducing parallel execution into your sequence.
Ray's approach of modifying the process model would be best if you want this change to apply to a number of sequence files that you'd rather not individually modify.
The new execution approach is easier if you just have one sequence file for which you want this behavior.
06-07-2007 02:18 AM
Hi,
I am able to get individual reports by enabling the new execution and wait till the execution completes. In this case i get the serial number entry dialog box every time the sequence call in each step starts execution. Is it possible to avoid this?
Is it possible to disable the serail number input dialog?
Regards
Gopal
06-07-2007 10:27 AM
06-11-2007 12:08 AM
HI,
Thank you. Now got what i wanted. I changed the entry point.
I have one more query, I configured the report options call back for the main sequence. I gave a different directory path for the report. The report corressponding to the main sequence is getting generated in the specified directory. But the reports of the sequence calls are getting generated in the directory specified in the reports option menu.
Is it possible to make the reports generate at the required directory by making changes in the main seqnece alone?
Regards
Gopal
06-11-2007 03:23 PM