Alias for fixture names #711
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
* The pages should be excuted in the below order SuiteExecution.ExecutionLogOfSuitePage SuiteExecution.SuiteExecutionCleansUpHistory SuiteExecutionLog.ExecutionLogOfSuitePage SuiteExecutionLog.ExecutionLogOfTestPage * The order below would result without this commit SuiteExecution.ExecutionLogOfSuitePage SuiteExecutionLog.ExecutionLogOfSuitePage SuiteExecutionLog.ExecutionLogOfTestPage SuiteExecution.SuiteExecutionCleansUpHistory
Slight change of the output of the TestTextFormatter. The duration has been put at the beginning to find easier long running test which might indicate a problem.
Test "ScenarioLibraryShouldIncludeIncludedPages" did neither fail nor pass. It had no check. With this commit it passes.
This commit aligns the format of the SuiteExecutionReport to the more compact and more readable TestTextFormatter format: * Duration put to the front * Page name and path are in separate columns * Instead of an absolute path only a relative path is printed.
Write more readable requirements and segregate them from the implementation with alias names for fixtures. See FitNesse.UserGuide.WritingAcceptanceTests.SliM.DefineAlias for samples and details. Also relax the naming convention for slim tables types names. A semicolon is now optional.
This reverts commit 937e0c2.
This reverts commit eb41839.
This reverts commit 6509b04.
This reverts commit de35b5c.
|
Indeed, this is a nice way to decouple fixture names from table headers. This can make table headers more meaningful. |
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.
Write more readable requirements and segregate them from the
implementation with alias names for fixtures.
See FitNesse.UserGuide.WritingAcceptanceTests.SliM.DefineAlias for
samples and details.
Also relax the naming convention for slim tables types names. A
semicolon is now optional. Example: addTableType("dt", DecisionTable.class);