[Email Plugin Development Tale] Spec details

The devil is in details...

A week ago there was a feature described this way:

Given project 1

And requester with email 'sender@company.com'

And sender email is 'sender@company.com'

And profile has rules:

|Rule |

|then attach to project 2|

|then attach to project 1|

When the email arrived

Then the message should be attached to project 1

I sat down and implemented it, marked bug as 'Coded' and passed to QA.

Today Anastasia, our QA, come to me and said that this bug is still reproducible.

After short revising the specification was updated to:

A week ago there was a feature described this way:

Given project 1

And deleted project 2

And requester with email 'sender@company.com'

And sender email is 'sender@company.com'

And profile has rules:

|Rule |

|then attach to project 2|

|then attach to project 1|

When the email arrived

Then the message should be attached to project 1

You see? In first spec project was not actually created, in the second spec project exists in the system as deleted.

Just one line of code changed everything! And finally we've got a failed spec on "then the message should be attached to project 1" and it was easily fixed.

The conclusion is: don't underestimate your specs! Look through them carefully! :)