Jmeter - During Run, appropriate pages are not displayed as response data
My issue in detail -
Steps followed - 1. Recorded few steps which includes Login page then home page and then logout functionality..
(used (a) blazemeter -- recorded the steps, extracted the .jmx file, imported it into Jmeter
(b) used HTTPs Test script recorder (by setting proxy))
2. Added Listener - View Result tree
3. Ran the test
Observation:
Run Results steps in the Result tree appears as pass (most of them).. HOWEVER, when i analyse the HTML format of response (in Response data tab) home page and logout page are not loaded itself.. it still shows Login page itself..
Can some one please help me to get through this issue..
Many many thanks in advance...
performance jmeter
New contributor
add a comment |
My issue in detail -
Steps followed - 1. Recorded few steps which includes Login page then home page and then logout functionality..
(used (a) blazemeter -- recorded the steps, extracted the .jmx file, imported it into Jmeter
(b) used HTTPs Test script recorder (by setting proxy))
2. Added Listener - View Result tree
3. Ran the test
Observation:
Run Results steps in the Result tree appears as pass (most of them).. HOWEVER, when i analyse the HTML format of response (in Response data tab) home page and logout page are not loaded itself.. it still shows Login page itself..
Can some one please help me to get through this issue..
Many many thanks in advance...
performance jmeter
New contributor
add a comment |
My issue in detail -
Steps followed - 1. Recorded few steps which includes Login page then home page and then logout functionality..
(used (a) blazemeter -- recorded the steps, extracted the .jmx file, imported it into Jmeter
(b) used HTTPs Test script recorder (by setting proxy))
2. Added Listener - View Result tree
3. Ran the test
Observation:
Run Results steps in the Result tree appears as pass (most of them).. HOWEVER, when i analyse the HTML format of response (in Response data tab) home page and logout page are not loaded itself.. it still shows Login page itself..
Can some one please help me to get through this issue..
Many many thanks in advance...
performance jmeter
New contributor
My issue in detail -
Steps followed - 1. Recorded few steps which includes Login page then home page and then logout functionality..
(used (a) blazemeter -- recorded the steps, extracted the .jmx file, imported it into Jmeter
(b) used HTTPs Test script recorder (by setting proxy))
2. Added Listener - View Result tree
3. Ran the test
Observation:
Run Results steps in the Result tree appears as pass (most of them).. HOWEVER, when i analyse the HTML format of response (in Response data tab) home page and logout page are not loaded itself.. it still shows Login page itself..
Can some one please help me to get through this issue..
Many many thanks in advance...
performance jmeter
performance jmeter
New contributor
New contributor
New contributor
asked Dec 27 '18 at 18:01
Jyothishree. R
12
12
New contributor
New contributor
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
Most probably your test scenario simply fails to perform the login. There could be different reasons for this, the most popular mistakes are:
- Missing HTTP Cookie Manager. Modern web applications widely use cookies for authentication purposes, maintaining sessions and storing client information
- Missing correlation. Modern web applications widely use dynamic parameters for i.e. security reasons or client state tracking
So first of all try adding HTTP Cookie Manager to your test plan. If it doesn't help - record the same scenario one more time and inspect generated scripts. If you will see the differences - all the different values need to be correlated, to wit:
- You will need to extract the value from the previous response using suitable JMeter PostProcessor and store it into a JMeter Variable
- In the next request you should replace recorded hard-coded value with the variable from the previous step.
add a comment |
Observation: Run Results steps in the Result tree appears as pass (most of them).. HOWEVER, when i analyse the HTML format of response (in Response data tab) home page and logout page are not loaded itself.. it still shows Login page itself..
Yes, this is why for every test one is expected to check for results. A simple HTTP 200 response (HTTP OK) is not sufficient as unexpected, but valid, pages may be returned which will be inappropriate for the business process. If your virtual user continues while off track then the odds are high that you will run into an unhandled exception (HTTP 500) as you begin presenting data to the server which is out of context to the state of the business process flow.
This is one of the ways where you can check for the maturity of the performance tester, the maturity of the tester, and the value of what is being delivered. If, when you look at the script, you find that the tester is not checking for expected results being returned in the content (vs just the status), you can be assured that the maturity of the tester is low and the value of the delivery also matches. You can likely find corresponding data points in the handling of data (dynamic and user provided), monitoring, analysis, etc...
As a tester, each step has an expected result. Check for it. This is true for manual testing. This is true for automated functional testing. This is true of performance testing. This is true independent of the tool(s) used.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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
});
}
});
Jyothishree. R is a new contributor. Be nice, and check out our Code of Conduct.
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%2fstackoverflow.com%2fquestions%2f53949070%2fjmeter-during-run-appropriate-pages-are-not-displayed-as-response-data%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Most probably your test scenario simply fails to perform the login. There could be different reasons for this, the most popular mistakes are:
- Missing HTTP Cookie Manager. Modern web applications widely use cookies for authentication purposes, maintaining sessions and storing client information
- Missing correlation. Modern web applications widely use dynamic parameters for i.e. security reasons or client state tracking
So first of all try adding HTTP Cookie Manager to your test plan. If it doesn't help - record the same scenario one more time and inspect generated scripts. If you will see the differences - all the different values need to be correlated, to wit:
- You will need to extract the value from the previous response using suitable JMeter PostProcessor and store it into a JMeter Variable
- In the next request you should replace recorded hard-coded value with the variable from the previous step.
add a comment |
Most probably your test scenario simply fails to perform the login. There could be different reasons for this, the most popular mistakes are:
- Missing HTTP Cookie Manager. Modern web applications widely use cookies for authentication purposes, maintaining sessions and storing client information
- Missing correlation. Modern web applications widely use dynamic parameters for i.e. security reasons or client state tracking
So first of all try adding HTTP Cookie Manager to your test plan. If it doesn't help - record the same scenario one more time and inspect generated scripts. If you will see the differences - all the different values need to be correlated, to wit:
- You will need to extract the value from the previous response using suitable JMeter PostProcessor and store it into a JMeter Variable
- In the next request you should replace recorded hard-coded value with the variable from the previous step.
add a comment |
Most probably your test scenario simply fails to perform the login. There could be different reasons for this, the most popular mistakes are:
- Missing HTTP Cookie Manager. Modern web applications widely use cookies for authentication purposes, maintaining sessions and storing client information
- Missing correlation. Modern web applications widely use dynamic parameters for i.e. security reasons or client state tracking
So first of all try adding HTTP Cookie Manager to your test plan. If it doesn't help - record the same scenario one more time and inspect generated scripts. If you will see the differences - all the different values need to be correlated, to wit:
- You will need to extract the value from the previous response using suitable JMeter PostProcessor and store it into a JMeter Variable
- In the next request you should replace recorded hard-coded value with the variable from the previous step.
Most probably your test scenario simply fails to perform the login. There could be different reasons for this, the most popular mistakes are:
- Missing HTTP Cookie Manager. Modern web applications widely use cookies for authentication purposes, maintaining sessions and storing client information
- Missing correlation. Modern web applications widely use dynamic parameters for i.e. security reasons or client state tracking
So first of all try adding HTTP Cookie Manager to your test plan. If it doesn't help - record the same scenario one more time and inspect generated scripts. If you will see the differences - all the different values need to be correlated, to wit:
- You will need to extract the value from the previous response using suitable JMeter PostProcessor and store it into a JMeter Variable
- In the next request you should replace recorded hard-coded value with the variable from the previous step.
answered Dec 28 '18 at 10:45
Dmitri T
69.1k33458
69.1k33458
add a comment |
add a comment |
Observation: Run Results steps in the Result tree appears as pass (most of them).. HOWEVER, when i analyse the HTML format of response (in Response data tab) home page and logout page are not loaded itself.. it still shows Login page itself..
Yes, this is why for every test one is expected to check for results. A simple HTTP 200 response (HTTP OK) is not sufficient as unexpected, but valid, pages may be returned which will be inappropriate for the business process. If your virtual user continues while off track then the odds are high that you will run into an unhandled exception (HTTP 500) as you begin presenting data to the server which is out of context to the state of the business process flow.
This is one of the ways where you can check for the maturity of the performance tester, the maturity of the tester, and the value of what is being delivered. If, when you look at the script, you find that the tester is not checking for expected results being returned in the content (vs just the status), you can be assured that the maturity of the tester is low and the value of the delivery also matches. You can likely find corresponding data points in the handling of data (dynamic and user provided), monitoring, analysis, etc...
As a tester, each step has an expected result. Check for it. This is true for manual testing. This is true for automated functional testing. This is true of performance testing. This is true independent of the tool(s) used.
add a comment |
Observation: Run Results steps in the Result tree appears as pass (most of them).. HOWEVER, when i analyse the HTML format of response (in Response data tab) home page and logout page are not loaded itself.. it still shows Login page itself..
Yes, this is why for every test one is expected to check for results. A simple HTTP 200 response (HTTP OK) is not sufficient as unexpected, but valid, pages may be returned which will be inappropriate for the business process. If your virtual user continues while off track then the odds are high that you will run into an unhandled exception (HTTP 500) as you begin presenting data to the server which is out of context to the state of the business process flow.
This is one of the ways where you can check for the maturity of the performance tester, the maturity of the tester, and the value of what is being delivered. If, when you look at the script, you find that the tester is not checking for expected results being returned in the content (vs just the status), you can be assured that the maturity of the tester is low and the value of the delivery also matches. You can likely find corresponding data points in the handling of data (dynamic and user provided), monitoring, analysis, etc...
As a tester, each step has an expected result. Check for it. This is true for manual testing. This is true for automated functional testing. This is true of performance testing. This is true independent of the tool(s) used.
add a comment |
Observation: Run Results steps in the Result tree appears as pass (most of them).. HOWEVER, when i analyse the HTML format of response (in Response data tab) home page and logout page are not loaded itself.. it still shows Login page itself..
Yes, this is why for every test one is expected to check for results. A simple HTTP 200 response (HTTP OK) is not sufficient as unexpected, but valid, pages may be returned which will be inappropriate for the business process. If your virtual user continues while off track then the odds are high that you will run into an unhandled exception (HTTP 500) as you begin presenting data to the server which is out of context to the state of the business process flow.
This is one of the ways where you can check for the maturity of the performance tester, the maturity of the tester, and the value of what is being delivered. If, when you look at the script, you find that the tester is not checking for expected results being returned in the content (vs just the status), you can be assured that the maturity of the tester is low and the value of the delivery also matches. You can likely find corresponding data points in the handling of data (dynamic and user provided), monitoring, analysis, etc...
As a tester, each step has an expected result. Check for it. This is true for manual testing. This is true for automated functional testing. This is true of performance testing. This is true independent of the tool(s) used.
Observation: Run Results steps in the Result tree appears as pass (most of them).. HOWEVER, when i analyse the HTML format of response (in Response data tab) home page and logout page are not loaded itself.. it still shows Login page itself..
Yes, this is why for every test one is expected to check for results. A simple HTTP 200 response (HTTP OK) is not sufficient as unexpected, but valid, pages may be returned which will be inappropriate for the business process. If your virtual user continues while off track then the odds are high that you will run into an unhandled exception (HTTP 500) as you begin presenting data to the server which is out of context to the state of the business process flow.
This is one of the ways where you can check for the maturity of the performance tester, the maturity of the tester, and the value of what is being delivered. If, when you look at the script, you find that the tester is not checking for expected results being returned in the content (vs just the status), you can be assured that the maturity of the tester is low and the value of the delivery also matches. You can likely find corresponding data points in the handling of data (dynamic and user provided), monitoring, analysis, etc...
As a tester, each step has an expected result. Check for it. This is true for manual testing. This is true for automated functional testing. This is true of performance testing. This is true independent of the tool(s) used.
answered Dec 29 '18 at 17:26
James Pulley
4,6471913
4,6471913
add a comment |
add a comment |
Jyothishree. R is a new contributor. Be nice, and check out our Code of Conduct.
Jyothishree. R is a new contributor. Be nice, and check out our Code of Conduct.
Jyothishree. R is a new contributor. Be nice, and check out our Code of Conduct.
Jyothishree. R is a new contributor. Be nice, and check out our Code of Conduct.
Thanks for contributing an answer to Stack Overflow!
- 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%2fstackoverflow.com%2fquestions%2f53949070%2fjmeter-during-run-appropriate-pages-are-not-displayed-as-response-data%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