Welcome to the new Parasoft forums! We hope you will enjoy the site and try out some of the new features, like sharing an idea you may have for one of our products or following a category.
Environment reference does not work on slave machines during LoadTest
Options
LegacyForum
Posts: 1,664 ✭✭
SOAtest
Version: 5.5.3 (Build date: November 18, 2008)
Copyright © 2001-2008 Parasoft Corporation
GRS enabled, Server enabled
1000 Virtual Users
Java Version: 1.5.0_11
We are using environment file reference rather than importing environment in our tst project. When we run load tests on remote machines, we get error of can't read environment property from all the tests that run on the remote machine. This seems to work when we remove the environment reference and instead replace it with imported environment. Is it a known issue?
Version: 5.5.3 (Build date: November 18, 2008)
Copyright © 2001-2008 Parasoft Corporation
GRS enabled, Server enabled
1000 Virtual Users
Java Version: 1.5.0_11
We are using environment file reference rather than importing environment in our tst project. When we run load tests on remote machines, we get error of can't read environment property from all the tests that run on the remote machine. This seems to work when we remove the environment reference and instead replace it with imported environment. Is it a known issue?
0
Comments
-
This can be solved by copying the environment files to the remote machine which you are using as a slave. When you synchronize the slave machines, only the version (including SP version) is verified / synchronized - not the files your test is dependent upon.0