New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scenario with output parameters #536

Merged
merged 3 commits into from Oct 23, 2014

Conversation

Projects
None yet
2 participants
@six42
Contributor

six42 commented Oct 16, 2014

This patch allows to use output parameters in scenarios.
For scripts calling a scenario this was not documented but heavily used if you look at the acceptance tests.
Now this feature can also be used for decision tables. In addition you can now declare the output parameters of a scenario in the header which makes them more readable.
See the new suite FitNesse.SuiteAcceptanceTests.SuiteSlimTests.ScenarioTestSuite for details.

Only to support symbol assignments in decision tables implemented with a scenario a new library function is required in the slim client. For the java client this has been added. For other slim client you need to add them. See the FitNesse.UserGuide.WritingAcceptanceTests.SliM.SlimProtocol for the new function.

To support in future releases also symbol assignments in Table Tables and Query Tables some more functions have been added already.

Finally if an unknow table type is given in a test this is now flagged as error and not as fail.

six42 added some commits Oct 5, 2014

Extended SlimHelperLibrary
Added required Slim client features to SlimHelperLibrary. Added tests
for the changes to new page:
FitNesse.SuiteAcceptanceTests.SuiteSlimTests.SlimSymbolManipulation

@amolenaar amolenaar merged commit bd77e26 into unclebob:master Oct 23, 2014

amolenaar added a commit that referenced this pull request Oct 23, 2014

@amolenaar amolenaar added this to the Next release milestone Nov 13, 2014

@six42 six42 deleted the six42:scenario_with_output branch Mar 17, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment