I did the keynote at
DevCon Summit this year, and I chose to give a talk entitled "How Technical Debt Can Ruin A Business".
You can view the slides here.
Based on the feedback that I got after my talk, it seems what most people are immediately concerned about is automated testing. What I emphasized in my talk was
unit testing, but for a lot of teams, their focus for automated testing is UI testing, with tools such as Selenium or HP-QTP. This will likely lead to as much misery as what the team is trying to solve.
 |
| The Test Pyramid |
A good guideline to how much of each type of automated testing is the
Test Pyramid. The Test Pyramid says that the bulk (~60%) of your automated tests should be unit tests, written by the developers as they write their code. The next most plentiful (~30%) are "Service Layer" or behavioral tests, which execute use cases without the user interface. The smallest number of tests (~10%) should be tests that call the UI Layer.
No comments:
Post a Comment