Skip to content
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

feat(test-runner): Support lifecycle events #125

Merged
merged 1 commit into from
Jul 17, 2016
Merged

Conversation

nicojs
Copy link
Member

@nicojs nicojs commented Jul 15, 2016

Add support for test runner lifecycle events: init and dispose. These are called once in every test runner life cycle (if implemented). If they return a promise, we will wait for those promises to be resolved before proceding. We will only wait for max 2 seconds with the dispose before forcing the child process to be killed.

Add support for test runner lifecycle events: init and dispose. These are called once in every test runner life cycle (if implemented).  If they return a promise, we will wait for those promises to be resolved before proceding. We will only wait for max 2 seconds with the dispose before forcing the child process to be killed.
@simondel
Copy link
Member

Yay Karma is working again 💃 🎉 🍰 Nice work :)

@simondel simondel merged commit 6c0e229 into master Jul 17, 2016
@simondel simondel deleted the testrunner-lifecycle branch July 17, 2016 18:56
@nicojs nicojs restored the testrunner-lifecycle branch July 22, 2016 12:19
nicojs added a commit that referenced this pull request Jul 30, 2016
Add support for test runner lifecycle events: init and dispose. These are called once in every test runner life cycle (if implemented).  If they return a promise, we will wait for those promises to be resolved before proceding. We will only wait for max 2 seconds with the dispose before forcing the child process to be killed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants