On 11 September 2013 09:28, Milamber <[email protected]> wrote: > > I've prefer keep the word "proxy" in the name.
That's the part I really want to get rid of, because of the potential confusion with the other proxy settings. > "Test" is an ambiguous word, means in my mind "test" (like beta-test). Word > like "script" seems better. Well, we use Test already quite a lot, as in Test Element / Test Script. Since JMeter is all about testing, I think using Test is OK. > - HTTP(S) Proxy Recorder > - HTTP(S) Proxy Test Recorder > - Web Proxy Recorder > - Web Proxy for Test Recorder > - Web Proxy for Script Recorder > - Web Proxy Script Recorder > > > Web Proxy Recorder is my favorite. > How about Web Test Script Recorder or Test Script Recorder - HTTP(S) or HTTP(S) Test Script Recorder > > Le 11/09/2013 09:00, Philippe Mouawad a ecrit : > >> HTTP(S) Test Recorder would be a good name I think. >> But if we do the change we absolutely need to keep all references to >> JMeter >> Proxy Server as it is referenced on many links and documentations. >> >> Did you have some time to think about summariser enabling ? >> >> Great changes you made sebb ! >> >> Thanks >> >> On Tuesday, September 10, 2013, sebb wrote: >> >>> The HTTP Proxy Server test element is used to record browser sessions >>> as test plans. >>> >>> The name does not describe its function (it describes the >>> implementation). >>> Having Proxy in the name means it's more easily confused with the >>> proxy settings that may be needed to run tests. >>> >>> I wonder if it would be a good idea to rename the test element to >>> something like >>> >>> HTTP(S) Test Recorder >>> or >>> Test Recorder - HTTP(S) >>> or >>> Test Recorder - HTTP/HTTPS >>> >>> I did consider "Test Recorder" on its own, but that might be taken to >>> imply that it can record other test types (e.g. JDBC), which it cannot >>> at present. Even if we did implement JDBC recording, it would likely >>> need a different GUI as the options would be completely different, so >>> I think the name needs to include HTTP(S). >>> >>> I think the rename will only affect the component reference docs - and >>> we can add an anchor for the old name. >>> >>> Thoughts? >>> Would it help to rename the element? >>> >>> If there is agreement, I'd like to do this before the next release. >>> There are other major changes to the recorder which also need >>> documenting. >>> >> >
