sjwalter
15 years agoNew Contributor
DDT with Project Test items
I've watched the DDT webinar, but have trouble seeing how I can solve my problem with my script based tests. Everything I find talks mainly about running DDT loops against Keyword tests, whereas all my tests are scripts.
Basically I have a slew of tests, written in TC8.1, arranged on the Test Items tab for the (one) project in the suite. See attachment 1. These run fine and are driven by several Project.Variables. I have to run these tests for different values of those project variables. At the moment I have routines that set those variables for one or other of the test cases I wish to run, which I run manually, and then I hit F5 to run the tests that I've selected.
What I would like to do is to describe those different parameter sets in, say, an Excel spreadsheet and then to run Platform Iteration as many times as I have rows in the sheet. That is, I would like to have something like I've mocked up in attachment #2 - a head "test" perhaps (just a script function) that is akin to a driven DDT function as described for the keyword tests, and which represents one iteration of the tests and which sets up the variables so that the underlying tests run. Is this do-able? Or am I going about it the wrong way? Or am I being as clear as mud? :-)
Any help gratefully received
Stephen
Basically I have a slew of tests, written in TC8.1, arranged on the Test Items tab for the (one) project in the suite. See attachment 1. These run fine and are driven by several Project.Variables. I have to run these tests for different values of those project variables. At the moment I have routines that set those variables for one or other of the test cases I wish to run, which I run manually, and then I hit F5 to run the tests that I've selected.
What I would like to do is to describe those different parameter sets in, say, an Excel spreadsheet and then to run Platform Iteration as many times as I have rows in the sheet. That is, I would like to have something like I've mocked up in attachment #2 - a head "test" perhaps (just a script function) that is akin to a driven DDT function as described for the keyword tests, and which represents one iteration of the tests and which sets up the variables so that the underlying tests run. Is this do-able? Or am I going about it the wrong way? Or am I being as clear as mud? :-)
Any help gratefully received
Stephen