On Jul 10, 2013, at 9:08 AM, Stefan Marr smallt...@stefan-marr.de wrote:
Hi Camillo:
On 10 Jul 2013, at 02:46, Camillo Bruni camillobr...@gmail.com wrote:
Does anybody here distinguish failures and errors for real when doing TDD?
To make your live a little more difficult, I actually
camillo
frankly there are plenty of things that should be improved but for SUnit.
First we should look at the main branch in VW because it changes since
we forked it
Second Smalltalk/X people probably enhance it too.
Fourth there is also assess the frameworks of andres
Camillo wrote:
Does anybody here distinguish failures and errors for real when doing TDD?
Yes, it has a special meaning AND is very helpfull - ESPECIALLY when you start
with tests first (XPStyle):
Usually one writes the tests and then you try to get them from red over yellow
to
green:
red:
Am 10.07.2013 um 08:15 schrieb Torsten Bergmann asta...@gmx.de:
Camillo wrote:
Does anybody here distinguish failures and errors for real when doing TDD?
Yes, it has a special meaning AND is very helpfull - ESPECIALLY when you
start with tests first (XPStyle):
Usually one writes the
Hi Camillo:
On 10 Jul 2013, at 02:46, Camillo Bruni camillobr...@gmail.com wrote:
Does anybody here distinguish failures and errors for real when doing TDD?
To make your live a little more difficult, I actually introduced an additional
type of failure on top of that: blue for still to be
On 2013-07-10, at 09:08, Stefan Marr smallt...@stefan-marr.de wrote:
Hi Camillo:
On 10 Jul 2013, at 02:46, Camillo Bruni camillobr...@gmail.com wrote:
Does anybody here distinguish failures and errors for real when doing TDD?
To make your live a little more difficult, I actually
Precisely. There is a huge difference between invalidating a known contract
(i.e., failure) and raising an unexpected error (i.e., error).
Please do not do away with this distinction.
Cheers,
Doru
On Jul 10, 2013, at 10:34 AM, Damien Cassou damien.cas...@gmail.com wrote:
On Wed, Jul 10,
On 2013-07-10, at 13:32, Tudor Girba tu...@tudorgirba.com wrote:
Precisely. There is a huge difference between invalidating a known contract
(i.e., failure) and raising an unexpected error (i.e., error).
In which sense?
As a programmer I have to tackle them both the same way: start debugging.
On 2013-07-10, at 14:09, Sven Van Caekenberghe s...@stfx.eu wrote:
Maybe we should not throw away the distinction, I am used to it as well.
But what Camillo means, I think, is that in the end it does not matter.
For example, if I have a unit test for some object's #printString both the
Error – defect in the human thought process made while trying to
understand given information, solve problems, or to use methods and
tools. In the context of software requirements specifications, an error
is a basic misconception of the actual needs of a user or customer.
Fault – concrete
Hi,
On Jul 10, 2013, at 1:47 PM, Camillo Bruni camillobr...@gmail.com wrote:
On 2013-07-10, at 13:32, Tudor Girba tu...@tudorgirba.com wrote:
Precisely. There is a huge difference between invalidating a known contract
(i.e., failure) and raising an unexpected error (i.e., error).
In which
On 2013-07-10, at 14:47, Tudor Girba tu...@tudorgirba.com wrote:
Hi,
On Jul 10, 2013, at 1:47 PM, Camillo Bruni camillobr...@gmail.com wrote:
On 2013-07-10, at 13:32, Tudor Girba tu...@tudorgirba.com wrote:
Precisely. There is a huge difference between invalidating a known contract
Oh, so programming in the debugger was a myth?
I'm disappointed ;)
2013/7/10 Damien Cassou damien.cas...@gmail.com
On Wed, Jul 10, 2013 at 8:16 AM, Norbert Hartl norb...@hartl.name wrote:
I use them. I always fix the red tests first because they are mostly
easier to fix and some of them
Am 10.07.2013 um 15:33 schrieb Nicolas Cellier
nicolas.cellier.aka.n...@gmail.com:
Oh, so programming in the debugger was a myth?
I'm disappointed ;)
Well, I would say it is neither a myth nor has it to be forced. There is always
more than one work mode.
So you program only in the
Does anybody here distinguish failures and errors for real when doing TDD?
I do not really see the point of separating them.
Besides the complexity added to the testing framework it is a burden for
newcomers.
I personally just see:
1) test passes = green, ok
2) test doesn't pass = red,
On Wed, Jul 10, 2013 at 2:46 AM, Camillo Bruni camillobr...@gmail.comwrote:
Does anybody here distinguish failures and errors for real when doing TDD?
I don't and I would like to see if both can be merged.
--
Damien Cassou
http://damiencassou.seasidehosting.st
Success is the ability to go
On 2013-07-10, at 06:35, Damien Cassou damien.cas...@gmail.com wrote:
On Wed, Jul 10, 2013 at 2:46 AM, Camillo Bruni camillobr...@gmail.comwrote:
Does anybody here distinguish failures and errors for real when doing TDD?
I don't and I would like to see if both can be merged.
2
17 matches
Mail list logo
