Why Auto-Retry of Test Execution in a Test Framework is Wrong?

Recently, I noticed the ‘Auto-Retry’ feature in some ‘new test frameworks’, such as Jest and Cypress. It is wrong! I pioneered (and implemented) the ‘auto-retry’ back in 2007 and have been using it ever since. The difference is that my ‘Auto-Retry’ is in Continuous Testing Server, not the automation or syntax framework. BuildWise, the CT server I created with the Auto-Retry feature…

--

--

--

Test automation & CT coach, author, speaker and award-winning software developer. Help teams succeed with Agile/DevOps by implementing real Continuous Testing.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

You should know these 8 things about Serverless before you’ll spend months on the IT project

A Gentle Introduction to ZFS, Part 3: Network File Systems and iperf3 Testing

3 ways to learn coding fast from YouTube…

Pro Con Critical Evaluation — but What If?

Code Coverage with JaCoCo and SonarQube

Laravel Development Company USA

Ways to Mock Service in Spring Development

The Hidden Costs of IoT Application Development

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Zhimin Zhan

Zhimin Zhan

Test automation & CT coach, author, speaker and award-winning software developer. Help teams succeed with Agile/DevOps by implementing real Continuous Testing.

More from Medium

Successful Windows Desktop App Test Automation with Appium

Selenium Selectors that Suck Less

Access now the beta to generate tests from your logs

Time those functional tests with Timings API — Part 2