{"issue":{"pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"state":"closed","user":{"avatar_url":"https://secure.gravatar.com/avatar/0be0e4aa42aacd9a8a95c792de273ca7?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"0be0e4aa42aacd9a8a95c792de273ca7","url":"https://api.github.com/users/aslakhellesoy","login":"aslakhellesoy","id":1000},"milestone":null,"labels":[{"name":"JUnit","color":"ededed","url":"https://api.github.com/repos/cucumber/cucumber-jvm/labels/JUnit"}],"assignee":null,"updated_at":"2011-10-28T22:36:58Z","closed_at":"2011-10-28T22:36:58Z","comments":0,"url":"https://api.github.com/repos/cucumber/cucumber-jvm/issues/77","body":"People are bound to misuse classes annotated with @RunWith(Cucumber.class) by putting stepdefs in them. This is bad because it couples stepdefs to features, and confuses people. In fact, two instances of the class will be created. -One by JUnit and one by the DI container.\r\n\r\n@RunWith(Cucumber.class) annotated classes are meant to be empty and should serve a single purpose: kick of cucumber to run a feature.\r\n\r\nForcing users to put stepdefs elsewhere will hopefully help them understand the difference.","html_url":"https://github.com/cucumber/cucumber-jvm/issues/77","number":77,"title":"Throw exception if @RunWith(Cucumber.class) classes have methods.","id":2084091,"created_at":"2011-10-28T21:37:17Z"},"action":"closed"}