# Table Difference Checker node failing execution despite equal input tables **URL:** \ **Category:** Node Development\ **Created:** [August 30, 2018, 7:26pm UTC](https://forum.knime.com/t/table-difference-checker-node-failing-execution-despite-equal-input-tables/11951 "2018-08-30T19:26:31Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![qqilihq](https://forum-cdn.knime.com/user_avatar/forum.knime.com/qqilihq/32/50_2.png) [@qqilihq](https://forum.knime.com/u/qqilihq)\ **Post date:** [August 30, 2018, 9:05pm UTC](https://forum.knime.com/t/table-difference-checker-node-failing-execution-despite-equal-input-tables/11951/2 "2018-08-30T21:05:54Z")
This has likely to do with the following (quoting from the [Difference Checker](https://nodepit.com/node/org.knime.testing.internal.nodes.differ.DifferenceCheckerNodeFactory) documentation): > The special checkers are used for the cell contents as well as for the column domain (i.e. possible values and bounds). The minimum/maximum values are obviously different in the reference and the produced table ( **edit to clarify:** this has nothing to do with the actually **visible** values in the table content – but you can inspect it in the ‘Spec’ tab). To fix the test, you could make use of the [Domain Calculator](https://nodepit.com/node/org.knime.base.node.preproc.domain.dialog2.DomainNodeFactory) node. But you should probably double check, whether the domain information needs to be taken care of programmatically? – Philipp --- _[View the full topic](https://forum.knime.com/t/table-difference-checker-node-failing-execution-despite-equal-input-tables/11951)._