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

Yes! In fact, that=E2=80=99s what I advise my team to do: do a method usage=
 search and add tests that confirms that expectations for the method still =
work. It=E2=80=99s also good for understanding the codebase.

> On Dec 4, 2019, at 8:23 PM, James Grenning <[email protected]> wrote:
>=20
> Hi Slava
>=20
> I'd like to add a step.
>=20
> James
>=20
>=20
> On 4 Dec 2019, at 22:50, Slava Imeshev via Groups.Io wrote:
>=20
>> 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 t=
o change.
>> 2. Make the test green by fixing the bug.
>> 3. Check in.
>>=20
>>> On Dec 4, 2019, at 5:58 PM, Steve Gordon <[email protected]> wrote:
>>>=20
>>>=20
>>>=20
>>> On Wed, Dec 4, 2019 at 5:58 PM Slava Imeshev via Groups.Io <imeshev=3D=
[email protected] <mailto:[email protected]>> wrote:
>>> Most of times bugs come from under-tested code. Sometimes from edge ca=
ses when requirements weren=E2=80=99t clearly understood. New tests must co=
ver missed use cases. TDD works great here.
>>>=20
>>>=20
>>> Slava,
>>>=20
>>> How do you use TDD to write new tests for existing code?  How do you g=
o from a discovered bug to knowing what unit tests to write for which objec=
ts?  How does TDD apply?
>>>=20
>>>=20
>>=20
>>=20
>=20
>=20
>=20
>=20
>=20


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

View/Reply Online (#160413): https://groups.io/g/extremeprogramming/messag=
e/160413
Mute This Topic: https://groups.io/mt/39418691/2417047
Group Owner: [email protected]
Unsubscribe: https://groups.io/g/extremeprogramming/leave/4902963/61983806=
5/xyzzy  [[email protected]]
-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-=3D-