Add before_suite and after_suite callbacks to ExampleGroupMethods and Options
Reported by Brian Takita | December 28th, 2007 @ 11:28 PM | in 1.1.4
Its useful to have a callback before and after the suite runs.
That way, the developer does not need to alias method chain the Options#run_example method.
Comments and changes to this ticket
-
David Chelimsky December 28th, 2007 @ 11:48 PM
- → State changed from “new” to “open”
Do you mean "the RSpec developer" or a developer who is an RSpec user?
-
-
Brian Takita May 4th, 2008 @ 12:49 AM
- → Milestone changed from “” to “1.1.4”
-
Brian Takita May 4th, 2008 @ 12:49 AM
- → Assigned user changed from “” to “Brian Takita”
-
Brian Takita May 4th, 2008 @ 01:36 AM
I'm thinking:
ExampleGroupMethods.before(:suite) and ExampleGroupMethods.after(:suite)
An implication of this is any ExampleGroup can define its own before and after suite callbacks.
-
Brian Takita May 4th, 2008 @ 01:44 AM
- → Title changed from “Add before_suite and after_suite callbacks to Suite or Options” to “Add before_suite and after_suite callbacks to ExampleGroupMethods and Options”
-
Brian Takita May 4th, 2008 @ 01:45 AM
- → State changed from “open” to “resolved”
Pushed in 116abe1ae90e8c6fae864aad94a85f2df175deda
-
Brian Takita May 4th, 2008 @ 02:17 AM
- → State changed from “resolved” to “open”
The after(:suite) callback lambda is passed a boolean representing whether the suite passed or failed.
-
Brian Takita May 4th, 2008 @ 02:54 AM
- → State changed from “open” to “resolved”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Behaviour Driven Development for Ruby.
