{"action":"opened","issue":{"url":"https://api.github.com/repos/junit-team/junit/issues/1095","labels_url":"https://api.github.com/repos/junit-team/junit/issues/1095/labels{/name}","comments_url":"https://api.github.com/repos/junit-team/junit/issues/1095/comments","events_url":"https://api.github.com/repos/junit-team/junit/issues/1095/events","html_url":"https://github.com/junit-team/junit/issues/1095","id":60410186,"number":1095,"title":"ParentRunner does not document itself as calling collectInitializationErrors in it's constructor.","user":{"login":"eatnumber1","id":17551,"avatar_url":"https://avatars.githubusercontent.com/u/17551?v=3","gravatar_id":"","url":"https://api.github.com/users/eatnumber1","html_url":"https://github.com/eatnumber1","followers_url":"https://api.github.com/users/eatnumber1/followers","following_url":"https://api.github.com/users/eatnumber1/following{/other_user}","gists_url":"https://api.github.com/users/eatnumber1/gists{/gist_id}","starred_url":"https://api.github.com/users/eatnumber1/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/eatnumber1/subscriptions","organizations_url":"https://api.github.com/users/eatnumber1/orgs","repos_url":"https://api.github.com/users/eatnumber1/repos","events_url":"https://api.github.com/users/eatnumber1/events{/privacy}","received_events_url":"https://api.github.com/users/eatnumber1/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-09T21:08:26Z","updated_at":"2015-03-09T21:08:26Z","closed_at":null,"body":"ParentRunner and it's subclasses should document the methods which are meant to be overridden, but are transitively called from ParentRunner's constructor.\r\n\r\nArguably, this is a design flaw in ParentRunner, as with the current behavior, subclasses which override these methods will be called before those subclasses begin initialization which severely limits the usefulness of overriding these methods."}}