Member-only story
Why Don’t I Use Defect Tracking? No Need, I do real Continuous Testing.
Replicate a new defect with automated tests, then add it to the regression suite that runs in a Continuous Testing process
Non-Medium-Members: You can read this article free on Vocal.
Those teams who are spending hours every day on a defect-tracking system (DTS), such as Quality Center, may get offended by the title of this article. Here, I borrow quotes from some of the world’s leading experts to support my view.
The answers to track/fix the bugs, from these three highly-claimed books, are the same: creating an automated test to replicate the bug, so that you don’t need to log it in DTS. Here, I would like to share my own experience of practising this in the past decades.
“Facebook is released twice a day, and keeping up this pace is at the heart of our culture. With this release pace, automated testing with Selenium is crucial to making sure everything works before being released.” — DAMIEN SERENI, Engineering Director at Facebook, at Selenium 2013 conference.
The bugs/defects I am referring to are the ones found by the IT team members. Those that are reported by the customers, of course, will be treated with high priority and may be recorded. For my own apps, I usually implement customers’ feature/change requests or bugs within the same day, so I don’t track customers' reported defects either. This is a fact, otherwise, I wouldn’t have been able to develop and maintain 6 complex apps
- TestWise, next-gen functional IDE
- BuildWise, an international award-winning Continuous Testing Server
- ClinicWise, a cloud-based practice management system
