-
Notifications
You must be signed in to change notification settings - Fork 36
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
Generalize Reporting & Introduce suite-by-suite HTML Reporting #83
Conversation
This is going to move out of terminate/2 and it's more clear this way.
We will need this if the HTML reporter is going to stick around long enough to recieve information about more than one BDD suite.
I'll resolve the failed builds on Travis: not sure why only some fail. |
Okay: the release notes for 1.2 write the following under enhancements.
|
This keeps the test and CI output like it was before we replaced the progress reporter with the event manager and generic servers.
f7f82b8
to
335bffb
Compare
lib/white_bread/event_manager.ex
Outdated
for {_, pid, _, _} <- Supervisor.which_children(__MODULE__) do | ||
GenServer.stop(pid, :normal, @timeout) | ||
end | ||
Supervisor.stop(__MODULE__) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As you're using Supervisor.stop/1
there's no need to individually stop the children. As they're linked they will be stopped along with the supervisor.
Bit late looking at this but I like the approach. Thanks for the contribution 👍 I'll merge and tag this morning. |
@meadsteve: Thanks for updating the README. |
This introduces and Event Manager similar to ExUnit's.
We can send test information to more than one outputter and keep the outputter processes spinning between test suites. This way the outputters, namely the
HTML
outputter, can report on a suite-by-suite basis. TheConsole
outputter is adapted (this PR makes it responsible for more of the console output we see).