- Last Active
thank you for that explanation. That's about what I had figured and sort of "proven by experience" by separating them into tst to excel pairs. but as you pointed out, changing to data repository instead of excels will be our next iteration. it …
that will be the next step. but nicole had some trouble using globals on jenkins so I wanted to figure that step out first.
tnx @benken_parasoft and @Ireneusz Szmigiel I will try this today. but I had to delete the global data sources yesterday as the .tst files opened really slowly with so many (72!) excel data sources configured as global. is that your experience…
hi benken, that's just from the forums markdown. the single line code blocks still reformat the conained text. trust me, it's all double slashes except for the colon escape slash... i'll try to attach the file itself.
my localsettings.properties file: soatest.license.use_network=true soatest.license.network.host=### soatest.license.network.port=### soatest.license.network.edition=server_edition datasources.global.location=D:\workspaces\workspace\mvp.svs.so…
prefect! that's what I was looking for. this way I don't have to script the entire XML and change the activeDataSourceName every time. thank you
ok, i will try this and come back should i have any more issues. tnx as always
this will work for global data sources that are not defined locally in the tst file? and by creating a new workspace via cli are initially nowhere defined? I do have the globaldatasources.property file. the question would be how to pass this …