In that case use
Given users:
|eye|
|blue|
and write the @Given method so it will put defaults in unspecified columns.
On 11 November 2010 17:13, Gilles Scokart wrote:
> That's indeed a good solution. But I think this aproach doesn't
> highlight the thing that is important.
>
> If in my test t
That's indeed a good solution. But I think this aproach doesn't
highlight the thing that is important.
If in my test the only thing that mather is that the user has blue
eyes and others characteristics can be default, I feel the table
aproach put some 'noice' it.
But I can give it a try to see w
Why don't you use a tabular parameter to specify your user
characteristics, e.g.:
Given a user with:
|eye colour|height|age|
|blue|180|21|
In this way, you delegate to the implementation what to do with the
table information.
Also, you can easily scale up to deal with multiple users with no extr
Did you have already faced a case where you want to write different
sentences like this :
Given a user with blue eyes
Given a user measuring 1m80
Given a user measuring 1m80 with blue eyes
Given a user of 21 years old
Given a user of 21 years old measuring 1m80
Given a user of 21 years old measuri
