Stallion__
First Class Star
- Joined
- Feb 17, 2015
- Runs
- 3,477
- Post of the Week
- 2
Umpires didn't check for no ball btw 

Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
There have been bigger win margins, but this is one of the most one sided tests in recent memory. The match outcome was clear by tea on day one! Even when the match is one sided you think the match can change course (or perhaps head for a draw), but this match was practically over by the end of the first day's play.
Pretty emotional post-match interviews from both Clarke and Cook.
What DoesnstUnderstandTestCricket isn't getting is that long innings (in the early part of the match) usually win tests and in a long innings there will be periods when test match bowlers get on top, so the batter has to dig in and survive for a bit. All the great batters of the past knew this. These young Aussies do not seem to. They are stuck in ODI mode and that is why they are losing.
Similarly, experienced test bowlers know that sometimes the batters will be on top and they have to spread the field and bowl for containment. Then when a wicket goes down the slips come back and the bowler can come in at full power for a bit. Over several days the constant effort thing doesn't work - you have to know when to attack and when to defend.
Brilliant posts by [MENTION=50394]IndianWillow[/MENTION] and [MENTION=7774]Robert[/MENTION].
[MENTION=135134]CricketAnalyst[/MENTION] is so used to limited overs and Test cricket on roads - as are the Aussies - that he imagines that this wicket was a minefield.
It wasn't. England scored 274-4 on Day 1.
The whole reason why Australia is losing is because its batsmen think like [MENTION=135134]CricketAnalyst[/MENTION] and play expansive shots at balls that they should be leaving, and get caught in the slips.
This wicket was a 60-2 at Lunch on Day 1 wicket. And the only wickets should have been LBW with the batsman leaving the ball.
[MENTION=135134]CricketAnalyst[/MENTION] for some reason has mentioned Strike Rate several times, as if it is a positive in Test cricket on sporting surfaces. It isn't: the bottom line is that the team which wins in Test cricket is the one which bats for longer, not the one which scores faster.
And for exactly the same reasons listed above: the longer you bat, the flatter the wicket gets, the softer the ball gets and the more tired the bowlers become.
I will write a separate post on this, but you couldn't be more wrong.
In the 16 decisive Test matches this calendar year, the side scoring faster has won 14 of them. The side batting longer has won 12 (even after I've considered a side that actually faced fewer overs to have batted longer, if their first innings was longer than the opposition first innings because they won by chasing down quickly).
What this shows is a) The side scoring faster tends to also bat longer. This is a fact and there is an overwhelming correlation here.
b) When there is a divergence between the two, the side scoring faster tends to have done better and that faster scoring is more valuable.
Can you do the stats for two conditions? 1. A non phatta wicket 2. A team winning away.
Let me know how many times a visiting side has toppled a home team on bowling conditions favouring home bowlers with a ODI approach to batting.