V2: Evented Approach #14
Merged
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.
Evented approach
Events are being added to
SpecSuitewith the goal of providing more feedback during tests, adding anAfterEachapproach for teardown (Fixes #9), and providing a foundation for extensibility (WBProxy and Scenario can be built much more cleanly on top of events).The following events are fired by
SpecSuite:BeforeEach: Called before each spec in suite (setup)Result(Spec): Called when spec has resultAfterEach: Called after each spec in suite (teardown)Note:
BeforeAllandAfterAlltype events are best handled in the listenerInitializeandTerminate.Before
After
Tasks
WBProxyandScenario). May add back later, especially sinceWBProxywill work much better with eventsInlineRunnerandDisplayRunnerto reporters (use events)Closes #7