Keep Testability In Mind

From APIDesign

Revision as of 05:59, 14 June 2008 (edit) Apidesign (Talk | contribs) (Removing all content from page) ← Previous diff		Revision as of 05:15, 3 August 2008 (edit) (undo) JaroslavTulach (Talk | contribs) Next diff →
Line 1:		Line 1:
		+	== 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 this chapter 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 05:15, 3 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 this chapter 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.