Ted, good catch on the isMiniYARNCluster property not being set. I assumed that would be in place.
The MiniCluster, as part of it's startup process, sets parameters like the RM address in the configuration.
This is then available via createJobConf in MiniMRCluster, or getConfig in MiniMRClientCluster. Instead of selectively copying out parameters, downstream projects should really be using the configuration objects returned by these APIs to submit jobs. That would allow things to keep working if parameters were changed.
Looked at the PIG code, and that's exactly what it is doing - so the tests passing is expected.
I'm not sure if Hive unit tests will work. In the test command you pasted, I believe TestCliDriver needs to be replaced with TestMinimrCliDriver to actually get it to use the MiniMRCluster.
IAC, does it make sense for HBase to make use of config objects returned by the "getConfig" objects so that similar changes in the future don't break unit tests ?