acceptance testing - Specflow Feature File Best Practice -

thanks in advance help.

my question pertains best practices inside specflow feature file?

question:

is using wait command inside of feature file considered bad practice.

example:

and click on username , wait 5 seconds , input new value last name 

the wait command forces 5 second wait. doing make sure page loaded prevent "element not found" errors or other errors. make sure have clean page manipulate.

would better practice use wait inside of step file itself?

//using fluent automation i.waituntil(() => ()); //or i.wait(); //timespan 

my reasoning not using fluent automation wait is:

by utilizing fluent automation method dependent on default timeout in settings object. default timeout in cases may not long enough or may long. seems verbose me continually change/reset settings object benefit being remove wait commands feature file.

so best practice?

thanks,

-n

i think best practice keep feature file scenarios, , free of implementation details.

since following bdd process (http://dannorth.net/introducing-bdd) feature file output of conversation between , process expert, , scenario represents steps going take prove functionality works example. hope steps define business process , performed system, not 1 might developing now. ideally logic captures our intent , can reused on future systems might replace current one.

so don't see saying need wait

....

although might want say

when page has loaded 

and maps quite nicely onto fluent automation.