Originally Posted by
rabbimojo
This could probably be isolated in an evening of testing by a few alliance and horde priests. If it hasn't been acknowledge as a bug by Blizzard, you could probably make a very solid case for it by week's end, and potentially have it fixed for 3.1.2. Mild anecdotal evidence isn't going to earn you much, so get rigorous.
Gear up past 17% hit, head to the boss dummy. Make sure nobody else comes by. Start DPing, look for misses. Long cooldown, but keep at it. Get a couple thousand cumulative between the group of you. Record the data reliably,
Not finding any?
Ok, drop down to 16%, and drop misery, in a group with draenei hitbuff. Test again as above.
Drop to 14%, get misery going. Gather data.
Drop to 13%, with misery + draenei
etc. just keep testing to isolate each buff and talent. Repeat until statistically significant. If you need help on that, head to EJ forums, discuss what you want to do, and ask someone to figure out how many casts you would need to make it statistically significant.
It will be quite a lot of casts, since if the problem is that say the draenei buff doesn't apply, you've only got a 1% chance on any given cast for a miss, when testing 16%+draenei.
Tricky part is getting hit exactly at the right amount, or close enough. Below 17%, each priest gathering data would need to record their exact +hit rating while casting, and report it along with the data. This is because the chances of not seeing a miss if you have, say, 16.5% hit, vs. 16%, are significantly different. After 100 casts with 16.5%, you have a 60.5% of not seeing one, vs. 16%, where you'd have just a 36.6% chance. (Testing misery makes this easy, as 3% miss should make itself evident very quickly.)
A final variable you'll want to try and isolate is dual-spec swapping.
Anywho.. that's all I have to say. Just trying to get the community to raise the level of evidence we bring to Blizz to talk to them.