Actual value equals expected value but still got failure

[Qun Zhang]

Hi all,

Simply put, in the gtest I am using

ASSERT_EQ(1.069, tf::getYaw(node.position.pose.orientation));

The test result:

test_planner.cpp:41: Failure
Value of: tf::getYaw(node.position.pose.orientation)
Actual: 1.069
Expected: 1.069

How come the equality of both value still generates failure result?

Any inputs would be appreciated. Thanks all.

Best Regards, ZQ

[Keith Ray]

Floating-point values are imprecise.

instead of

ASSERT_EQ(1.069, tf::getYaw(node.position.pose.orientation));

use this

ASSERT_NEAR(val1, val2, abs_error);
or this:

ASSERT_DOUBLE_EQ(expected, actual);

Please see this reference:

    https://code.google.com/p/googletest/wiki/V1_5_AdvancedGuide#Floating-Point_Comparison

--

C. Keith Ray
* (650) 539-4729

* https://www.dropbox.com/s/mpoefyt9bz1yoxx/keith_ray_resume.pdf

* http://agilesolutionspace.blogspot.com/

--

---
You received this message because you are subscribed to the Google Groups "Google C++ Testing Framework" group.
To unsubscribe from this group and stop receiving emails from it, send an email to googletestframe...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Vlad Losev]

Welcome to the brave new world of floating point math!

Most likely, the result of your computation is very close to the expected value - close enough to be printed as one - but doesn't match it exactly. You should look into Google Test's wiki's section on floating point comparison to learn how to do it best.

--