assertEquals undefined in debugging mode
up vote
0
down vote
favorite
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
edited Nov 19 at 20:15
alepuzio
1,15922331
asked Nov 19 at 16:57
Ekaterina Lobanova
12
add a comment |
up vote
0
down vote
favorite
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
edited Nov 19 at 20:15
alepuzio
1,15922331
asked Nov 19 at 16:57
Ekaterina Lobanova
12
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
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
edited Nov 19 at 20:15
alepuzio
1,15922331
asked Nov 19 at 16:57
Ekaterina Lobanova
12
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 at 20:15
alepuzio
1,15922331
asked Nov 19 at 16:57
Ekaterina Lobanova
12
edited Nov 19 at 20:15
alepuzio
1,15922331
asked Nov 19 at 16:57
Ekaterina Lobanova
12
edited Nov 19 at 20:15
alepuzio
1,15922331
edited Nov 19 at 20:15
alepuzio
1,15922331
edited Nov 19 at 20:15
alepuzio
1,15922331
1,15922331
asked Nov 19 at 16:57
Ekaterina Lobanova
12
asked Nov 19 at 16:57
Ekaterina Lobanova
12
asked Nov 19 at 16:57
Ekaterina Lobanova
12
12
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
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 at 22:30
klvenky
73110
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 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 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
2 days ago
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
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 at 22:30
klvenky
73110
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 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 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
2 days ago
add a comment |
up vote
0
down vote
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 at 22:30
klvenky
73110
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 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 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
2 days ago
add a comment |
up vote
0
down vote
up vote
0
down vote
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 at 22:30
klvenky
73110
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 at 22:30
klvenky
73110
answered Nov 19 at 22:30
klvenky
73110
answered Nov 19 at 22:30
klvenky
73110
answered Nov 19 at 22:30
klvenky
73110
73110
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 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 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
2 days ago
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 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 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
2 days ago
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 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 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 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 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
2 days ago
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
2 days ago
add a comment |
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
