| || |
Reqs traceability for GUI scripts using datapools
I have seen similar postings but without resolutions. My question regards data-driven testing and how to achieve requirements traceability for Robot automated test scripts via TestManager.
We currently use shell scripts which perform datapool functionality and then specific scripts which drive functionality related to specific requirements. A datapool row is considered one "testcase", or one record of data for a script (or scripts) to execute.
Can traceability be achieved while using this approach? If not, and we do away with the shell script, how do we execute tests multiple times, once for each record of data?
Is there another way to employ the use of datapools while maintaining traceability?