Minor thing to keep in mind

[kris]

Hi there,

I came across a minor usability issue with givwenzen when creating a
tutorial for the flex version.

I wanted to show how to get from the acceptance criteria to the domain
step, so I copied the AC and pasted it into the fresh domain step
class. Then I started adding function and assigning annotations. I did
not want to implement anything at the moment just have my steps filled
in with functions and annotations.

After doing it I ran the test to make sure all the steps were found
and matching and guess what...the test was all green.

I'm not saying it's a huge issue - you have the same with an empty
unit test - but that's something you should keep in mind especially
during the development process as without further inspection such
criteria seems to be valid.

Take care,
Kris

[Williams, Wesley]

I have seen this. Any idea how we could change this?

[Kris]

In Flex I think I could check the number of assertions made before and after running single acceptance criteria.  FlexUnit has such statistics. But that is more of a hack.

Initially I though of creating a best practice, that would involve adding fail() call to any step you define.

I also briefly created a live template for IJ that generates the domain step function. It's for flex but you can easily change it into java.

[DomainStep("$REGEXP$")]
public function $END$():void
{
    fail("Not yet implemented");
}

Regards,
Kris