Keep Testability In Mind - Revision history

JaroslavTulach at 13:47, 4 April 2018

2018-04-04T13:47:48Z

←Older revision		Revision as of 13:47, 4 April 2018
Line 3:		Line 3:
	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.		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.

-	== When ~~there~~ is Enough of [[CodeCoverage]] ==	+	== When There is Enough of [[CodeCoverage]]? ==

	{{:CodeCoverage}}		{{:CodeCoverage}}

JaroslavTulach at 13:47, 4 April 2018

2018-04-04T13:47:23Z

←Older revision		Revision as of 13:47, 4 April 2018
Line 2:		Line 2:

	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.		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.
		+
		+	== When there is Enough of [[CodeCoverage]] ==
		+
		+	{{:CodeCoverage}}

JaroslavTulach: /* Have You Ever Wondered...? */

2008-08-17T19:40:21Z

Have You Ever Wondered...?

←Older revision		Revision as of 19:40, 17 August 2008
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 ~~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.	+	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.

JaroslavTulach at 05:15, 3 August 2008

2008-08-03T05:15:58Z

←Older revision	Revision as of 05:15, 3 August 2008
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.

Apidesign: Removing all content from page

2008-06-14T05:59:38Z

Removing all content from page

←Older revision		Revision as of 05:59, 14 June 2008
Line 1:		Line 1:
-	~~Testability in design is an important topic, so I am glad you cover it. However, this section seems especially verbose to me.~~

-	~~Page 138: Devices in UNIX are typically notated with a leading slash; e.g. /dev/dvb/adapter0/frontend~~
-
-	~~Page 139: The trick about test-only methods and assertions seems like a hack to me.~~
-
-	~~--[[User:TomWheeler\|TomWheeler]] Sat Apr 12 19:13:37 CDT 2008~~

Tomwheeler at 00:50, 13 April 2008

2008-04-13T00:50:47Z

←Older revision		Revision as of 00:50, 13 April 2008
Line 2:		Line 2:

	Page 138: Devices in UNIX are typically notated with a leading slash; e.g. /dev/dvb/adapter0/frontend		Page 138: Devices in UNIX are typically notated with a leading slash; e.g. /dev/dvb/adapter0/frontend
		+
		+	Page 139: The trick about test-only methods and assertions seems like a hack to me.

	--[[User:TomWheeler\|TomWheeler]] Sat Apr 12 19:13:37 CDT 2008		--[[User:TomWheeler\|TomWheeler]] Sat Apr 12 19:13:37 CDT 2008

Tomwheeler at 00:49, 13 April 2008

2008-04-13T00:49:33Z

←Older revision		Revision as of 00:49, 13 April 2008
Line 1:		Line 1:
	Testability in design is an important topic, so I am glad you cover it. However, this section seems especially verbose to me.		Testability in design is an important topic, so I am glad you cover it. However, this section seems especially verbose to me.

		+	Page 138: Devices in UNIX are typically notated with a leading slash; e.g. /dev/dvb/adapter0/frontend

	--[[User:TomWheeler\|TomWheeler]] Sat Apr 12 19:13:37 CDT 2008		--[[User:TomWheeler\|TomWheeler]] Sat Apr 12 19:13:37 CDT 2008

Tomwheeler: New page: Testability in design is an important topic, so I am glad you cover it. However, this section seems especially verbose to me. --TomWheeler Sat Apr 12 19:13:37 CDT ...

2008-04-13T00:48:21Z

New page: Testability in design is an important topic, so I am glad you cover it. However, this section seems especially verbose to me. --TomWheeler Sat Apr 12 19:13:37 CDT ...

New page

Testability in design is an important topic, so I am glad you cover it. However, this section seems especially verbose to me.

--[[User:TomWheeler|TomWheeler]] Sat Apr 12 19:13:37 CDT 2008