The problem with what i said above is this.
You fool the cpu, and keep scoring shots down by
1. Pitching the ball on a good length.
2. Hitting the meter on the perfect execution spot
However, once you get used to hitting the lengths, and hitting the execution spot the cpu gets wise and starts to score runs.
Now, you either keep doing what your doing or you take a risk and deliberately bowl badly. If you do the later then you will either create a chance, ie cpu will mistime a shot or because you have bowled a bad delivery that will capitalize on it and score.
Its a vicious circle of rinse repeat. It becomes tedious, although i think the idea is good. It just does not execute well, so what you see is the computer scoring runs off balls they have no right to, and you end up taking a wicket because the cpu goes into slog mode.
This is not always the case of course, but i think this is the main problem with ai pacing in tests.