Customer Feedback - Daniel Yokomizo (dev license)
Reported by Kyle Moreland | July 8th, 2010 @ 08:31 PM
I find it great. I recommend it to most developers I know (I'm the team lead of a mid sized team, around 20 developers).
The only thing I don't like about it is wrong positioning of failed assertions when we use custom assertions. For example if I have the following code:
@ public void shouldRaiseBaz() {
final Foo foo = new Foo();
foo.bar(42);
assertRaised(new Baz(42), foo);
}
assertRaised is a custom assertion method, used in several methods, so if I have a test failure marker inside assertRaised it doesn't help me when there are several failures: sometimes a small change triggers several failures and it's not immediately obvious what was the failure.
Comments and changes to this ticket
-
Kyle Moreland July 8th, 2010 @ 08:35 PM
- Assigned user cleared.
Daniel Yokomizo [daniel.yokomizo@gmail.com]
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Continuous Test Runner for Java
benrady (at gmail)
Kyle Moreland