Scenario with output parameters #536
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Added required Slim client features to SlimHelperLibrary. Added tests for the changes to new page: FitNesse.SuiteAcceptanceTests.SuiteSlimTests.SlimSymbolManipulation
amolenaar
added a commit
that referenced
this pull request
Oct 23, 2014
Scenario with output parameters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.