DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6734>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=6734 Variables enhancement Summary: Variables enhancement Product: JMeter Version: unspecified Platform: All OS/Version: All Status: NEW Severity: Enhancement Priority: Other Component: Main AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] There are two different types of variables needed: simple variables used to replace a value, and a more dynamic variable can can obtain a new value with each interation & thread. The first one is simply a means of doing a replacement for the entire test run. An example of this would be the server name (which probably should be a variable by default) and port. I might want to change the server the test goes against, but I would waqnt the entire test to go against that machine. The second type would read it's values from some data source (text file, properties, whatever, with maybe a JTable to enter / edit them) and would change it's value each time a new thread or interation is started. This would be for things like usernames & passwords. In a lot of applications, different users will have different web pages, and you would want to ensure that the basic functionality to all users works regardless of which user is logged in. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
