arguments to use case actions should have quotes

[Emily Bache]

If a new use case action takes an argument (eg Misty), it appears as I type, for example if I name my action "book animal", the use case might look like this:

do something
book animal Misty
quit

The argument is "Misty" but it is not ovbious that it isn't part of the name of the use case action. I think it would be useful to have an option for pyusecase where arguments were quoted, like this:

do something
book animal "Misty"
quit

In Cucumber variables are often quoted like this to show they are not part of the action itself, and might vary.

[Geoff Bache (geoff.bache)]

Not sure about this. Such quotes aren't syntactically necessary and introduce complications if you actually want to enter a quote character. I've deliberately kept syntax to a minimum.

The statement "book animal Misty" is agnostic about whether Misty is a variable or not. Depending on how the UI changes, you could easily imagine situations where a "widget with variables" changed to a "widget without variables" (such as a series of check buttons) and this becomes a pain if the usecases all encode this knowledge (which is really a technical detail).

[Geoff Bache (geoff.bache)]

Closing, see previous comment.