{"action":"created","issue":{"url":"https://api.github.com/repos/behave/behave/issues/312","labels_url":"https://api.github.com/repos/behave/behave/issues/312/labels{/name}","comments_url":"https://api.github.com/repos/behave/behave/issues/312/comments","events_url":"https://api.github.com/repos/behave/behave/issues/312/events","html_url":"https://github.com/behave/behave/issues/312","id":69735766,"number":312,"title":"can't write summary to file","user":{"login":"alisener","id":8865320,"avatar_url":"https://avatars.githubusercontent.com/u/8865320?v=3","gravatar_id":"","url":"https://api.github.com/users/alisener","html_url":"https://github.com/alisener","followers_url":"https://api.github.com/users/alisener/followers","following_url":"https://api.github.com/users/alisener/following{/other_user}","gists_url":"https://api.github.com/users/alisener/gists{/gist_id}","starred_url":"https://api.github.com/users/alisener/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/alisener/subscriptions","organizations_url":"https://api.github.com/users/alisener/orgs","repos_url":"https://api.github.com/users/alisener/repos","events_url":"https://api.github.com/users/alisener/events{/privacy}","received_events_url":"https://api.github.com/users/alisener/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/behave/behave/labels/info","name":"info","color":"444444"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-04-21T03:44:13Z","updated_at":"2015-05-07T20:30:24Z","closed_at":null,"body":"if you set the config item outfiles to a file, summary is still written to stdout not the file. \r\n\r\n\r\nSummaryReporter has a hard coded \"stdout\"  as output stream\r\n\r\nclass SummaryReporter(Reporter):\r\n    show_failed_scenarios = True\r\n    output_stream_name = \"stdout\"\r\n"},"comment":{"url":"https://api.github.com/repos/behave/behave/issues/comments/100009784","html_url":"https://github.com/behave/behave/issues/312#issuecomment-100009784","issue_url":"https://api.github.com/repos/behave/behave/issues/312","id":100009784,"user":{"login":"jenisys","id":371945,"avatar_url":"https://avatars.githubusercontent.com/u/371945?v=3","gravatar_id":"","url":"https://api.github.com/users/jenisys","html_url":"https://github.com/jenisys","followers_url":"https://api.github.com/users/jenisys/followers","following_url":"https://api.github.com/users/jenisys/following{/other_user}","gists_url":"https://api.github.com/users/jenisys/gists{/gist_id}","starred_url":"https://api.github.com/users/jenisys/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jenisys/subscriptions","organizations_url":"https://api.github.com/users/jenisys/orgs","repos_url":"https://api.github.com/users/jenisys/repos","events_url":"https://api.github.com/users/jenisys/events{/privacy}","received_events_url":"https://api.github.com/users/jenisys/received_events","type":"User","site_admin":false},"created_at":"2015-05-07T20:30:23Z","updated_at":"2015-05-07T20:30:23Z","body":"@alisener \r\nA cheap solution would be to keep track of processed features in ``before_feature()`` or ``after_feature()`` hook and feed to your own Summary-Reporter object in the ``after_all()`` hook.\r\n\r\nAs alternative you could also select SummaryReporter object from the ``context.config.reporters`` list. Then you have direct access to its information. Note that depending on the configuration, a SummaryReporter object may not be always available."}}