-
Notifications
You must be signed in to change notification settings - Fork 179
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
Is there anything like @BeforeSpek or @AfterSpek #145
Comments
No. This is already available. You can use onBefore/After Test |
I was after something that runs only once for the whole spek, not for every test |
The 1.1 EAP now has changed behaviour to be like that.
…On 30/12/16 08:28, Jorge Antonio Díaz-Benito Soriano wrote:
I was after something that runs only once for the whole spek, not for
every test
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#145 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAGmS44bRvizRu15PtN9HnzresuOvJXYks5rNLKwgaJpZM4LXnay>.
--
Regards,
Hadi Hariri
http://hadihariri.com | @hhariri
|
Alright thanks. |
@stoyicker , in the |
I support the suggestion of adding wrappers to run around groups so that using them at top level would enclose the whole Spek - it's basically what I was after and I really believe that writing group-level initialization and teardown should be supported as is already the case for individual tests with |
+1 on |
I've been reading #115 where this are mentions about statements for before and after group. The problem is that the intention with that one seems to be exposing an extension api. Will writing an extension be needed to add Spek-wide before/after statements?
The text was updated successfully, but these errors were encountered: