Would you avoid the brittleness that clicks submit link|button has over I
submit.
There are often many ways of submitting on the same page. So to avoid
tying I submit to a particular scenario, I tend to use I click
'submit', which doesn't correspond to a link or button specifically,
but to a
Josh,
On 22/01/2009, Josh Chisholm joshuachish...@gmail.com wrote:
Would you avoid the brittleness that clicks submit link|button has over
I submit.
There are often many ways of submitting on the same page. So to avoid
tying I submit to a particular scenario, I tend to use I click
On Wed, Jan 21, 2009 at 6:49 AM, Juanma Cervera li...@ruby-forum.com wrote:
I am specing a feature, maybe at more high level of what it should be,
and this makes scenarios that involves more that one rails controller.
Is it possible or convenient?
I have scenarios like this (although it's
Hi David,
On 21/01/2009, David Chelimsky dchelim...@gmail.com wrote:
text on the button that is deemed to have business value, then you
might say And I click 'Request Service' - but if you're referencing
DOM IDs or HTML element names like 'submit', I'd hide those.
However we could get a
On Wed, Jan 21, 2009 at 9:27 AM, aidy lewis aidy.le...@googlemail.com wrote:
Hi David,
On 21/01/2009, David Chelimsky dchelim...@gmail.com wrote:
text on the button that is deemed to have business value, then you
might say And I click 'Request Service' - but if you're referencing
DOM IDs
Assuming that your steps are focused on using DOM Id's what sort of
convention would you use to translate from the narrative of the step to the
DOM id.
Would you avoid the brittleness that clicks submit link|button has over I
submit. Thats me arguing that whether its a link or a button, and
