in all honesty, i think the focus of our feedback has been more at the level of "the AI isn't chasing the totals in t20 correctly", "why are they throwing their wickets away with helicopters in tests?", "why don't they play off the back foot?" and "why is step outside off and smash it to leg a go to shot?" rather than batsman x or y isn't playing aggressively/conservatively enough in respect of their mentality. that certainly would be awesome, it's a frustration of mine too, but i think as far as the AI goes we are in baby steps territory. my personal targets for the AI are to get them using their bowlers properly, setting good fields in a reasonable manner, and presenting an interesting challenge to dismiss (in which frequent and varied edges that aren't always wickets, bat pads, varied and lively pitches all feature). i think the beta has given some good ideas for all of those, but how achievable they are given time and budget constraints i don't know.
if i had my way, the focus of changes between 14 and 17 would have been almost entirely on the AI, but it is what it is. we can throw hissy fits like blueballs or captain boreoff, or make the best of it. i've had some great fun in DBC17: if the patch gets close to what everyone on both sides of the beta (BA & testers) want, there will be lots more fun to be had for everyone.
i'm sure the beta conversation would stay private and rightly so. but it's certainly not been a love-in: we've been frank when we felt things were going off the wrong track or focus. the fact that we can do that without calling Ross a charlatan on a money grab, or demanding everyone in QA be sacked don't mean we're an echo chamber telling them everything is great.