You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While reading through the excellent docs, I've found the writing specifications page says table driven scenarios are an experimental feature and must be opted in to.
The execution page does not mention anything about experimental status or anything that must be opted in to.
I've found table driven tests work with the following without opting in to the experimental behavior:
taiko 1.0.6
gauge 1.0.8
VS Code gauge plugin 0.0.11
I think the docs should be updated to remove the experimental sections of the writing-specifications page as well as mention it has IDE plugin support.
I have not tested the other behaviors marked as not working with data tables:
CSV files can not be used as table for scenario.
Reporting plugins does not accommodate this feature.
Thanks!
The text was updated successfully, but these errors were encountered:
I have not tested the other behaviors marked as not working with data tables:
CSV files can not be used as table for scenario.
Reporting plugins does not accommodate this feature.
The feature is marked as experimental because these features do not work yet. It would marked out of experimental mode once reporting plugins have a way of handling it.
While reading through the excellent docs, I've found the writing specifications page says table driven scenarios are
an experimental feature
and must be opted in to.The execution page does not mention anything about experimental status or anything that must be opted in to.
I've found table driven tests work with the following without opting in to the experimental behavior:
I think the docs should be updated to remove the
experimental
sections of the writing-specifications page as well as mention it has IDE plugin support.I have not tested the other behaviors marked as not working with data tables:
Thanks!
The text was updated successfully, but these errors were encountered: