Re: [extremeprogramming] What has changed for you over the past 20 years?

Hi Slava

I'd like to add a step.

James


On 4 Dec 2019, at 22:50, Slava Imeshev via Groups.Io wrote:

> 1. Add a test that fails because the bug is there.
1.5 Add some other tests to make sure you understand the code you want 
to change.
> 2. Make the test green by fixing the bug.
> 3. Check in.
>
>> On Dec 4, 2019, at 5:58 PM, Steve Gordon <[email protected]> 
>> wrote:
>>
>>
>>
>> On Wed, Dec 4, 2019 at 5:58 PM Slava Imeshev via Groups.Io 
>> <[email protected] <mailto:[email protected]>> wrote:
>> Most of times bugs come from under-tested code. Sometimes from edge 
>> cases when requirements weren’t clearly understood. New tests must 
>> cover missed use cases. TDD works great here.
>>
>>
>> Slava,
>>
>> How do you use TDD to write new tests for existing code?  How do you 
>> go from a discovered bug to knowing what unit tests to write for 
>> which objects?  How does TDD apply?
>>
>>
>
>
> 



-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.

View/Reply Online (#160409): https://groups.io/g/extremeprogramming/message/160409
Mute This Topic: https://groups.io/mt/39418691/2417047
Group Owner: [email protected]
Unsubscribe: https://groups.io/g/extremeprogramming/leave/4902963/619838065/xyzzy  [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-