India vs South Africa, Cape Town Test: Lessons from 23-wicket Day – How not to bat in Tests

On a day where they lost six wickets for 0 runs, what was the best-case scenario for India? South Africa's weaker batting performance in the first innings (they were bowled for 55) and the ensuing 98-run deficit could prove to be the decisive factor on an exciting day of cricket. South Africa's awful ways continued as they lost three wickets and fell down by thirty-six runs in the second innings. The doubters will highlight the run differential between India's score and that Pink ball Test during the 2020 Australia visit, but surely India cannot fail again?

That being said, the day was ideal for venting about the deteriorating quality of Test batting. Prior to a tailender saving them, there were Pakistan's antics on a level track in Australia before daybreak. After that, in the afternoon, South Africa imploded, and in the evening, India spontaneously exploded to cement the deal.

Inadvertent there was also grim humor. Virat Kohli entered the game just after the pivotal moment of the innings, when KL Rahul was taken over by an enigmatic force and made 153 for 5 off the opening delivery of the 34th over.

He murmured series of instructions as he guided the next batsman, Ravindra Jadeja. Jadeja stabbing Ngidi bouncer to gully during two balls. Then, Kohli made significant contribution to the arrival of Jasprit Bumrah by engaging in frequent conversation with him. Bumrah also only lasted two balls until his bat splice broke off due to kicker.

Next, Kohli's gaze shifted to Muhammad Siraj. He had spoken to three teammates in four balls; nobody can claim he was by himself in the middle and didn't have any company. Kagiso Rabada packed him for the fifth time in Test matches with lifter from back of length that caused forceful push and an edge to the slips, ending any more chats with Kohli.

 

 

 

Enjoyed this article? Stay informed by joining our newsletter!

Comments

You must be logged in to post a comment.

About Author