[
https://issues.apache.org/jira/browse/HBASE-8275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13622968#comment-13622968
]
Lars Hofhansl commented on HBASE-8275:
--------------------------------------
Another option is to use reflection to find all public methods and dump a
description into gold file that we check in together with the test.
Running the test would involve regenerating that file and comparing it against
the checked in version. That way this becomes a unit test that is constantly
running and we would immediately identify any interface changes.
> Tool to test binary compatibility
> ---------------------------------
>
> Key: HBASE-8275
> URL: https://issues.apache.org/jira/browse/HBASE-8275
> Project: HBase
> Issue Type: New Feature
> Reporter: Jean-Daniel Cryans
> Fix For: 0.98.0
>
>
> Stack and I were discussing of ways to make binary compatibility easier to
> test than doing it completely by hand.
> One idea would be to have a tool that uses reflection to generate code that
> calls all the public methods from a list of classes. You would then compile
> this code against the current version you are on, then try it out with
> different HBase jars without recompiling.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
