gilta03 et al,
"How to use the header/footer/join parameters on separate scripts in the automation feature of ARD?
To see the answer to this question, please visit https://comm.support.ca.com/kb/automaton-configuration-export-header-footer-join/kb000072370 "
I have been trying to use the header/footer parameters in the Automation feature but the behavior I am experiencing is a bit different. From the Automation Configuration window, Export tab, Headers and footers sub-tab, I am trying to use Flow header and footer as well as Path Headers and footers.
After exporting the test cases into automation scripts the results are as follows:
When I select to merge scripts, the Flow header and footer is brought in but no path headers (and footers).
When I select separate scripts the path headers (and footers) are brought in but no Flow header and footer.
Either way, the results will cause me grief as the headers are always to do with imports, definitions and pre-reqs for the test case execution.
Technically, there are workarounds such as creating a additional step in the flows to cater for the headers. However, this is far from ideal as the flows should be only capturing the business logic and test cases independently from the technology of the scripts they will be generated to.
Please let me know if there is an alternative way, or a fix for this. Other than should I raise a support ticket?
In ARD version 2.8, automation was reworked to add Section Headers. Which version of ARD are you working on? Depending on that we could try to replicate this behaviour and confirm if it is an issue.
1. When I select to merge scripts, the Flow header and footer is brought in but no path headers (and footers).
- is a bug if true
2. When I select separate scripts the path headers (and footers) are brought in but no Flow header and footer.
- is an expected behaviour
The version I am using is 2.8.000.21
So it should have been addressed based on your comment.