The Test match when no-one wanted to be on top (except maybe Heather Knight)

Posted by
2 minute read

There aren’t many women’s Test matches at all. This means that the worst thing to produce when there is one would be a one-sided boreathon. The 2022 Ashes Test was most definitely not that. It served up almost as many plot twists as Wild Things (a film that averages one double-cross every nine minutes according to The Ringer.)

This article follows one lamenting the impossible workload inflicted on the best England men’s cricketers, so let’s quickly contextualise the rarity of women’s Tests before we get into things properly.

Broadcaster Isabelle Westbury has pointed out that there are currently no women’s Test matches on any confirmed schedule, anywhere, for any nation.

Midway through the Test, her sometime colleague Dan Norcross highlighted how Heather Knight has been England captain for five and a half years and yet was playing just her ninth Test, 11 years after her debut.

So when Australia made 337-9 batting first, we did not have a jeffing clue whether that was a good score or not. 337 is a pretty indeterminate score at the best of times, let alone when it drops into the world in the first innings of a Test when the players involved haven’t really played many international two-innings matches before.

The declaration was a hint, we suppose, and England duly turned it into a good score by slumping to 169-8. Knight was having none of it though. She made 168 not out and turned that 169-8 into 297 all out. Katherine Brunt then followed up her first innings 5-60 with a couple of immediate wickets and day three ended with Australia 12-2.

At this point England were, if not obviously on top scorecard-wise, then dominant in how-does-the-game-feel-right-now terms. But day four was the final day and Australia ambivalently scuffled their way to a position where they were the only team that could win the match.


Set a 257-run target in 48 overs, England thought, “Right, let’s just make those runs – we have Heather Knight, after all.”

Soon enough they were 218-3 and needed only 45 runs from 60 balls.

Then they lost six wickets.

Then number 11 Kate Cross blocked out the final over for a draw.

Just a draw.

Please subscribe to the King Cricket email because honestly, your memory’s not what it was and there’s every chance you’ll forget that we exist otherwise.


Mike Gatting wasn't receiving the King Cricket email when he dropped that ludicrously easy chance against India in 1993.


Why risk it when it's so easy to sign up?


  1. The little we saw (bad timing, this test, for us), Daisy and I thought the standard was very high.

    Not just the impressive batting when trying to save and then trying to win the match, not just the mix of attacking and defensive bowling, but also the fielding. For example two superb catches in the deep during that last hour to deny England what looked like becoming an unlikely win.

    Very watchable (and also very followable, as DC says).

    More please.

  2. In other news, those England U19 fellas have scraped through to the 2022 WC final this evening…exciting stuff, it was.

    They’ll need to play better in the final and there’s no mistake.

    Several of your Lancky youngsters looked the best of the bunch, KC, including The Boy Bell, Josh Borden (remember where you heard that left-arm seamer’s name first) and a lad named Aspinwall who can also bowl.

    1. Josh Boyden. Remember where you heard THAT name first. Predictive text doesn’t know what it’s on about.

      1. The last name I was told to remember in relation to a WC final was BRATHWAITE, and then that didn’t go well for a variety of reasons, not least that most people called him Braithwaite.

        Here’s the scorecard from the last time we reached a yoof WC final. Some great names there, along with many who rarely featured again:

Comments are closed.