assertEquals undefined in debugging mode
I'm trying to debug cucmber test in order to figure out reason of failure:
org.junit.ComparisonFailure: expected:<#00[a3b5]> but was:<#00[0000]>
Here is the failing part of the code
String actualColor2 = String.format("#%02x%02x%02x", hexValue1, hexValue2, hexValue3);
Assert.assertEquals("#00a3b5", String.format("#%02x%02x%02x", hexValue1, hexValue2, hexValue3));
In debugging mode I can see all values, and actualColor2 is #00a3b5
But if I run test it fails on this line like actualColor2 is #000000
Tried to rebuild project, restart computer, etc.
string values looks fine
java selenium cucumber assert
add a comment |
I'm trying to debug cucmber test in order to figure out reason of failure:
org.junit.ComparisonFailure: expected:<#00[a3b5]> but was:<#00[0000]>
Here is the failing part of the code
String actualColor2 = String.format("#%02x%02x%02x", hexValue1, hexValue2, hexValue3);
Assert.assertEquals("#00a3b5", String.format("#%02x%02x%02x", hexValue1, hexValue2, hexValue3));
In debugging mode I can see all values, and actualColor2 is #00a3b5
But if I run test it fails on this line like actualColor2 is #000000
Tried to rebuild project, restart computer, etc.
string values looks fine
java selenium cucumber assert
add a comment |
I'm trying to debug cucmber test in order to figure out reason of failure:
org.junit.ComparisonFailure: expected:<#00[a3b5]> but was:<#00[0000]>
Here is the failing part of the code
String actualColor2 = String.format("#%02x%02x%02x", hexValue1, hexValue2, hexValue3);
Assert.assertEquals("#00a3b5", String.format("#%02x%02x%02x", hexValue1, hexValue2, hexValue3));
In debugging mode I can see all values, and actualColor2 is #00a3b5
But if I run test it fails on this line like actualColor2 is #000000
Tried to rebuild project, restart computer, etc.
string values looks fine
java selenium cucumber assert
I'm trying to debug cucmber test in order to figure out reason of failure:
org.junit.ComparisonFailure: expected:<#00[a3b5]> but was:<#00[0000]>
Here is the failing part of the code
String actualColor2 = String.format("#%02x%02x%02x", hexValue1, hexValue2, hexValue3);
Assert.assertEquals("#00a3b5", String.format("#%02x%02x%02x", hexValue1, hexValue2, hexValue3));
In debugging mode I can see all values, and actualColor2 is #00a3b5
But if I run test it fails on this line like actualColor2 is #000000
Tried to rebuild project, restart computer, etc.
string values looks fine
java selenium cucumber assert
java selenium cucumber assert
edited Nov 19 '18 at 20:15
alepuzio
1,18922431
1,18922431
asked Nov 19 '18 at 16:57
Ekaterina LobanovaEkaterina Lobanova
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
that could be because of the way in which string equals has to be tested. Probably you should try something like
Assert.assertTrue('expected matches actual', expected.equals(actual));
Not sure if the syntax is exact, but it should work. because I remember reading somewhere that assertEquals may not be 100% accurate when comparing two strings. Please correct me if I'm wrong. :)
actually small timout solve an issue, element was visible and clickable but somehow there were not enough time to grab a color
– Ekaterina Lobanova
Nov 21 '18 at 16:27
in that case you could use the selnium waitUntil or a similar function. It will wait until the duration we specify or default WebDriver wait time. :)
– klvenky
Nov 22 '18 at 7:19
I used waitUntil, but even when element become visible & clickable color was "#000000", so I just used simple while solution (while actualColor equals 000000 wait 1sec more)
– Ekaterina Lobanova
Nov 26 '18 at 16:50
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
});
}
});
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%2f53379359%2fassertequals-undefined-in-debugging-mode%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
that could be because of the way in which string equals has to be tested. Probably you should try something like
Assert.assertTrue('expected matches actual', expected.equals(actual));
Not sure if the syntax is exact, but it should work. because I remember reading somewhere that assertEquals may not be 100% accurate when comparing two strings. Please correct me if I'm wrong. :)
actually small timout solve an issue, element was visible and clickable but somehow there were not enough time to grab a color
– Ekaterina Lobanova
Nov 21 '18 at 16:27
in that case you could use the selnium waitUntil or a similar function. It will wait until the duration we specify or default WebDriver wait time. :)
– klvenky
Nov 22 '18 at 7:19
I used waitUntil, but even when element become visible & clickable color was "#000000", so I just used simple while solution (while actualColor equals 000000 wait 1sec more)
– Ekaterina Lobanova
Nov 26 '18 at 16:50
add a comment |
that could be because of the way in which string equals has to be tested. Probably you should try something like
Assert.assertTrue('expected matches actual', expected.equals(actual));
Not sure if the syntax is exact, but it should work. because I remember reading somewhere that assertEquals may not be 100% accurate when comparing two strings. Please correct me if I'm wrong. :)
actually small timout solve an issue, element was visible and clickable but somehow there were not enough time to grab a color
– Ekaterina Lobanova
Nov 21 '18 at 16:27
in that case you could use the selnium waitUntil or a similar function. It will wait until the duration we specify or default WebDriver wait time. :)
– klvenky
Nov 22 '18 at 7:19
I used waitUntil, but even when element become visible & clickable color was "#000000", so I just used simple while solution (while actualColor equals 000000 wait 1sec more)
– Ekaterina Lobanova
Nov 26 '18 at 16:50
add a comment |
that could be because of the way in which string equals has to be tested. Probably you should try something like
Assert.assertTrue('expected matches actual', expected.equals(actual));
Not sure if the syntax is exact, but it should work. because I remember reading somewhere that assertEquals may not be 100% accurate when comparing two strings. Please correct me if I'm wrong. :)
that could be because of the way in which string equals has to be tested. Probably you should try something like
Assert.assertTrue('expected matches actual', expected.equals(actual));
Not sure if the syntax is exact, but it should work. because I remember reading somewhere that assertEquals may not be 100% accurate when comparing two strings. Please correct me if I'm wrong. :)
answered Nov 19 '18 at 22:30
klvenkyklvenky
129211
129211
actually small timout solve an issue, element was visible and clickable but somehow there were not enough time to grab a color
– Ekaterina Lobanova
Nov 21 '18 at 16:27
in that case you could use the selnium waitUntil or a similar function. It will wait until the duration we specify or default WebDriver wait time. :)
– klvenky
Nov 22 '18 at 7:19
I used waitUntil, but even when element become visible & clickable color was "#000000", so I just used simple while solution (while actualColor equals 000000 wait 1sec more)
– Ekaterina Lobanova
Nov 26 '18 at 16:50
add a comment |
actually small timout solve an issue, element was visible and clickable but somehow there were not enough time to grab a color
– Ekaterina Lobanova
Nov 21 '18 at 16:27
in that case you could use the selnium waitUntil or a similar function. It will wait until the duration we specify or default WebDriver wait time. :)
– klvenky
Nov 22 '18 at 7:19
I used waitUntil, but even when element become visible & clickable color was "#000000", so I just used simple while solution (while actualColor equals 000000 wait 1sec more)
– Ekaterina Lobanova
Nov 26 '18 at 16:50
actually small timout solve an issue, element was visible and clickable but somehow there were not enough time to grab a color
– Ekaterina Lobanova
Nov 21 '18 at 16:27
actually small timout solve an issue, element was visible and clickable but somehow there were not enough time to grab a color
– Ekaterina Lobanova
Nov 21 '18 at 16:27
in that case you could use the selnium waitUntil or a similar function. It will wait until the duration we specify or default WebDriver wait time. :)
– klvenky
Nov 22 '18 at 7:19
in that case you could use the selnium waitUntil or a similar function. It will wait until the duration we specify or default WebDriver wait time. :)
– klvenky
Nov 22 '18 at 7:19
I used waitUntil, but even when element become visible & clickable color was "#000000", so I just used simple while solution (while actualColor equals 000000 wait 1sec more)
– Ekaterina Lobanova
Nov 26 '18 at 16:50
I used waitUntil, but even when element become visible & clickable color was "#000000", so I just used simple while solution (while actualColor equals 000000 wait 1sec more)
– Ekaterina Lobanova
Nov 26 '18 at 16:50
add a comment |
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.
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%2f53379359%2fassertequals-undefined-in-debugging-mode%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