Cheezy,
Thank you for the contribution to JUnit. I understand that the shift to a
"specification" metaphor is helpful for some people.
We won't be incorporating @Spec as a synonym for @Test into JUnit at this
time. Our preference is to keep JUnit as simple as possible and my opinion
is that the added complexity of having a synonym is not repaid by enough
additional utility to make it worth putting in the core.
We will reconsider if there is a groundswell of support describing the
practical advantage of @Spec.
Regards,
Kent
_____
From:
junit@... [mailto:
junit@...] On Behalf Of
kuzman22
Sent: Monday, October 12, 2009 10:16 AM
To:
junit@...
Subject: [junit] @Spec
A little over a week ago I decided to update my Java TDD course.
I wanted to add a section that describes BDD or possibly even
write a new course that teaches BDD. As I was working on the
examples to be used for the course I noticed that it felt odd
to mark my unit level specs with @Test. I forked the junit code
in github and added the ability to mark them using a new @Spec
annotation. It behaves identically to @Test. I have sent a pull
request to Kent but I am curious what this list thinks about this
change.
Thanks
-Cheezy
[Non-text portions of this message have been removed]
