The agile test automation pyramid is a graphical strategy guide for implementing automated software testing. The pyramid was introduced by Mike Cohn in his book, "Succeeding with Agile." The image below represents Cohn's version of the model. The model splits types of testing into three layers based on the return on investment (ROI) offered by automating that particular type. The components of each layer may vary from one organization to another, but the bottom layer (the largest part of the pyramid structure) typically features unit tests, which are small units of code that are individually and independently scrutinized for proper operation. Unit tests are quick to write and quick to run, and their automation will have a good return on investment. The next-best return on investment is the middle layer of the triangle, at the application program interface (API) or service level. Acceptance tests move inputs to production code and then compare actual and expected results. They provide important feedback, but writing and maintaining them takes more time than unit tests, and they generally run more slowly. Graphical user interface (GUI) tests run more slowly than unit or API-level tests, and may require more frequent updating. In Cohn's model, automating graphical user interface (GUI) testing provides the least ROI. |
No comments:
Post a Comment