The issue here seems to be caused by the activeByDefault in the hadoop-1 maven profile which includes the hadoop-1 jars and shim jars in the test classpath even when -Phadoop-2 is used. I read the documentation on maven and it feels like what is done here is right but, when I remove those and use -Phadoop-2 (along with some changes to the way shims are included), I am able to see hadoop-2 tests being run correctly. I think that might be a maven bug.
Also, I looked into the hbase maven build as well since they have hadoop-1 and hadoop-2 specific builds. Their approach is to use a -Dhadoop.profile on the maven command line to choose a particular profile. Their default is hadoop-1 as well controlled by the absence of the -Dhadoop.profile flag. Let me know your thoughts on this approach. I can quickly provide a patch for this.