Keep Testability In Mind
From APIDesign
(Difference between revisions)
(→Have You Ever Wondered...?) |
|||
| Line 1: | Line 1: | ||
== Have You Ever Wondered...? == | == Have You Ever Wondered...? == | ||
| - | Why did people prefer [[wikipedia::Spring Framework|Spring]] over [[wikipedia::EJB|EJB 2.x]]? Is this just a problem of these particular technologies or is there a stronger reason beneath it applicable to any API? In | + | Why did people prefer [[wikipedia::Spring Framework|Spring]] over [[wikipedia::EJB|EJB 2.x]]? Is this just a problem of these particular technologies or is there a stronger reason beneath it applicable to any API? In [[Keep Testability In Mind|Chapter 9]] I'll discuss one, in my opinion very important difference that is getting more and more important in the last few years. [[wikipedia::Spring Framework|Spring]] has been designed with testabililty in mind and as such it attracted all those developers who subscribed to agile development. I'll present this as almost necessary feature of every new API and outline a way to make productivity high while making testability simple. |
Revision as of 19:40, 17 August 2008
Have You Ever Wondered...?
Why did people prefer Spring over EJB 2.x? Is this just a problem of these particular technologies or is there a stronger reason beneath it applicable to any API? In Chapter 9 I'll discuss one, in my opinion very important difference that is getting more and more important in the last few years. Spring has been designed with testabililty in mind and as such it attracted all those developers who subscribed to agile development. I'll present this as almost necessary feature of every new API and outline a way to make productivity high while making testability simple.
Follow
