Forum Discussion
jhopfner
14 years agoOccasional Contributor
Thanks for the reply David.
Because this test will be ran 3 times a night (each time with different server/database values for the variables), it's not logical for us to put the script as the first test item; if we do this the server/database variables will always contain the same values, unless we modify them manually.
The way we've currently been doing it is making 3 copies of the project, each contains the different project variable values we need. This is very tedious however; when we want to make a change to the script we have to copy the project again 3 times and modify each one to contain the correct values for each variable. This is why it would be nice to be able to modify these variables first from the script and continue running the rest of the keyword tests.
Better yet, it would be great if a user could modify these variables directly from the command line and run the test, something like:
10pm - "C:\Program
Files\Automated QA\TestExecute 7\Bin\TestExecute.exe" /run
"\\VisEntTest\VisPJSuite\Visions Enterprise Testing Project Suite.pjs"
/project:VisClient /var:Server=orion /var:Database=newdev /SilentMode
11pm - "C:\Program
Files\Automated QA\TestExecute 7\Bin\TestExecute.exe" /run
"\\VisEntTest\VisPJSuite\Visions Enterprise Testing Project Suite.pjs"
/project:VisClient /var:Server=aries /var:Database=testing /SilentMode
... and so on.
I know this isn't currently possible, however it would be a great feature addition. For now, is there any way to modify the variables through a script and continue running the rest of the keyword tests?
Because this test will be ran 3 times a night (each time with different server/database values for the variables), it's not logical for us to put the script as the first test item; if we do this the server/database variables will always contain the same values, unless we modify them manually.
The way we've currently been doing it is making 3 copies of the project, each contains the different project variable values we need. This is very tedious however; when we want to make a change to the script we have to copy the project again 3 times and modify each one to contain the correct values for each variable. This is why it would be nice to be able to modify these variables first from the script and continue running the rest of the keyword tests.
Better yet, it would be great if a user could modify these variables directly from the command line and run the test, something like:
10pm - "C:\Program
Files\Automated QA\TestExecute 7\Bin\TestExecute.exe" /run
"\\VisEntTest\VisPJSuite\Visions Enterprise Testing Project Suite.pjs"
/project:VisClient /var:Server=orion /var:Database=newdev /SilentMode
11pm - "C:\Program
Files\Automated QA\TestExecute 7\Bin\TestExecute.exe" /run
"\\VisEntTest\VisPJSuite\Visions Enterprise Testing Project Suite.pjs"
/project:VisClient /var:Server=aries /var:Database=testing /SilentMode
... and so on.
I know this isn't currently possible, however it would be a great feature addition. For now, is there any way to modify the variables through a script and continue running the rest of the keyword tests?
Related Content
Recent Discussions
- 3 hours agoSvetaG