Why URL Patterns to Exclude in Jmeter's HTTP(s) Test Script Recorder not working?
When trying to do recording, in WorkBench's HTTP(s) Test Script Recorder, I used the suggested excludes for URL Patterns to Exclude:
.*.(bmp|css|js|gif|ico|jpe?g|png|swf|woff)
But in Recording Controller, I still got many css files, such as:
56 /project/web/css/common-styles.css
Why?
jmeter
edited May 8 '15 at 21:24
Thomas Dickey
6,02321125
asked May 8 '15 at 18:50
Victor
78129
add a comment |
When trying to do recording, in WorkBench's HTTP(s) Test Script Recorder, I used the suggested excludes for URL Patterns to Exclude:
.*.(bmp|css|js|gif|ico|jpe?g|png|swf|woff)
But in Recording Controller, I still got many css files, such as:
56 /project/web/css/common-styles.css
Why?
jmeter
edited May 8 '15 at 21:24
Thomas Dickey
6,02321125
asked May 8 '15 at 18:50
Victor
78129
add a comment |
When trying to do recording, in WorkBench's HTTP(s) Test Script Recorder, I used the suggested excludes for URL Patterns to Exclude:
.*.(bmp|css|js|gif|ico|jpe?g|png|swf|woff)
But in Recording Controller, I still got many css files, such as:
56 /project/web/css/common-styles.css
Why?
jmeter
edited May 8 '15 at 21:24
Thomas Dickey
6,02321125
asked May 8 '15 at 18:50
Victor
78129
When trying to do recording, in WorkBench's HTTP(s) Test Script Recorder, I used the suggested excludes for URL Patterns to Exclude:
.*.(bmp|css|js|gif|ico|jpe?g|png|swf|woff)
But in Recording Controller, I still got many css files, such as:
56 /project/web/css/common-styles.css
Why?
jmeter
jmeter
edited May 8 '15 at 21:24
Thomas Dickey
6,02321125
asked May 8 '15 at 18:50
Victor
78129
edited May 8 '15 at 21:24
Thomas Dickey
6,02321125
asked May 8 '15 at 18:50
Victor
78129
edited May 8 '15 at 21:24
Thomas Dickey
6,02321125
edited May 8 '15 at 21:24
Thomas Dickey
6,02321125
edited May 8 '15 at 21:24
Thomas Dickey
6,02321125
6,02321125
asked May 8 '15 at 18:50
Victor
78129
asked May 8 '15 at 18:50
Victor
78129
asked May 8 '15 at 18:50
Victor
78129
78129
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
I suggest reporting this issue via JMeter Bugzilla
In regards to the whole point of excluding scripts, images, styles, etc. from the load test - I totally disagree, in my view the load test needs to be as realistic as possible and JMeter simulation should be as close to what real browser do as you can do it.
Few recommendations:
- Real browsers fetch scripts, styles and images from the web page and use concurrent thread pool for it which varies from browser to browser. So tell JMeter to retrieve all embedded resources from the webpages and do it concurrently. The best place to configure this behavior is HTTP Request Defaults (by the way, you can use it while recording)
- As per point 1 browsers download images, styles, etc. but they do it only once, on subsequent requests these assets are being returned from browser's cache. To replicate this behavior add HTTP Cache Manager to your test plan.
- The absolute majority of web applications use cookies. To enable cookies support it's quite enough to add HTTP Cookie Manager which provides support, access and control of cookies.
- It may also be required to send some request headers as in some cases output varies depending on headers presence and values like for "User-Agent", "Accept-Language", "Accept-Encoding", etc. It can be handled via HTTP Header Manager
answered May 17 '15 at 8:22
Dmitri T
22112
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f912469%2fwhy-url-patterns-to-exclude-in-jmeters-https-test-script-recorder-not-working%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I suggest reporting this issue via JMeter Bugzilla
In regards to the whole point of excluding scripts, images, styles, etc. from the load test - I totally disagree, in my view the load test needs to be as realistic as possible and JMeter simulation should be as close to what real browser do as you can do it.
Few recommendations:
- Real browsers fetch scripts, styles and images from the web page and use concurrent thread pool for it which varies from browser to browser. So tell JMeter to retrieve all embedded resources from the webpages and do it concurrently. The best place to configure this behavior is HTTP Request Defaults (by the way, you can use it while recording)
- As per point 1 browsers download images, styles, etc. but they do it only once, on subsequent requests these assets are being returned from browser's cache. To replicate this behavior add HTTP Cache Manager to your test plan.
- The absolute majority of web applications use cookies. To enable cookies support it's quite enough to add HTTP Cookie Manager which provides support, access and control of cookies.
- It may also be required to send some request headers as in some cases output varies depending on headers presence and values like for "User-Agent", "Accept-Language", "Accept-Encoding", etc. It can be handled via HTTP Header Manager
answered May 17 '15 at 8:22
Dmitri T
22112
add a comment |
I suggest reporting this issue via JMeter Bugzilla
In regards to the whole point of excluding scripts, images, styles, etc. from the load test - I totally disagree, in my view the load test needs to be as realistic as possible and JMeter simulation should be as close to what real browser do as you can do it.
Few recommendations:
- Real browsers fetch scripts, styles and images from the web page and use concurrent thread pool for it which varies from browser to browser. So tell JMeter to retrieve all embedded resources from the webpages and do it concurrently. The best place to configure this behavior is HTTP Request Defaults (by the way, you can use it while recording)
- As per point 1 browsers download images, styles, etc. but they do it only once, on subsequent requests these assets are being returned from browser's cache. To replicate this behavior add HTTP Cache Manager to your test plan.
- The absolute majority of web applications use cookies. To enable cookies support it's quite enough to add HTTP Cookie Manager which provides support, access and control of cookies.
- It may also be required to send some request headers as in some cases output varies depending on headers presence and values like for "User-Agent", "Accept-Language", "Accept-Encoding", etc. It can be handled via HTTP Header Manager
answered May 17 '15 at 8:22
Dmitri T
22112
add a comment |
I suggest reporting this issue via JMeter Bugzilla
In regards to the whole point of excluding scripts, images, styles, etc. from the load test - I totally disagree, in my view the load test needs to be as realistic as possible and JMeter simulation should be as close to what real browser do as you can do it.
Few recommendations:
- Real browsers fetch scripts, styles and images from the web page and use concurrent thread pool for it which varies from browser to browser. So tell JMeter to retrieve all embedded resources from the webpages and do it concurrently. The best place to configure this behavior is HTTP Request Defaults (by the way, you can use it while recording)
- As per point 1 browsers download images, styles, etc. but they do it only once, on subsequent requests these assets are being returned from browser's cache. To replicate this behavior add HTTP Cache Manager to your test plan.
- The absolute majority of web applications use cookies. To enable cookies support it's quite enough to add HTTP Cookie Manager which provides support, access and control of cookies.
- It may also be required to send some request headers as in some cases output varies depending on headers presence and values like for "User-Agent", "Accept-Language", "Accept-Encoding", etc. It can be handled via HTTP Header Manager
answered May 17 '15 at 8:22
Dmitri T
22112
I suggest reporting this issue via JMeter Bugzilla
In regards to the whole point of excluding scripts, images, styles, etc. from the load test - I totally disagree, in my view the load test needs to be as realistic as possible and JMeter simulation should be as close to what real browser do as you can do it.
Few recommendations:
- Real browsers fetch scripts, styles and images from the web page and use concurrent thread pool for it which varies from browser to browser. So tell JMeter to retrieve all embedded resources from the webpages and do it concurrently. The best place to configure this behavior is HTTP Request Defaults (by the way, you can use it while recording)
- As per point 1 browsers download images, styles, etc. but they do it only once, on subsequent requests these assets are being returned from browser's cache. To replicate this behavior add HTTP Cache Manager to your test plan.
- The absolute majority of web applications use cookies. To enable cookies support it's quite enough to add HTTP Cookie Manager which provides support, access and control of cookies.
- It may also be required to send some request headers as in some cases output varies depending on headers presence and values like for "User-Agent", "Accept-Language", "Accept-Encoding", etc. It can be handled via HTTP Header Manager
answered May 17 '15 at 8:22
Dmitri T
22112
answered May 17 '15 at 8:22
Dmitri T
22112
answered May 17 '15 at 8:22
Dmitri T
22112
answered May 17 '15 at 8:22
Dmitri T
22112
22112
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f912469%2fwhy-url-patterns-to-exclude-in-jmeters-https-test-script-recorder-not-working%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
