{"action":"opened","issue":{"url":"https://api.github.com/repos/junit-team/junit-lambda/issues/13","labels_url":"https://api.github.com/repos/junit-team/junit-lambda/issues/13/labels{/name}","comments_url":"https://api.github.com/repos/junit-team/junit-lambda/issues/13/comments","events_url":"https://api.github.com/repos/junit-team/junit-lambda/issues/13/events","html_url":"https://github.com/junit-team/junit-lambda/issues/13","id":117545645,"number":13,"title":"Provide mechanism to order the sequence of tests","user":{"login":"elygre","id":23876,"avatar_url":"https://avatars.githubusercontent.com/u/23876?v=3","gravatar_id":"","url":"https://api.github.com/users/elygre","html_url":"https://github.com/elygre","followers_url":"https://api.github.com/users/elygre/followers","following_url":"https://api.github.com/users/elygre/following{/other_user}","gists_url":"https://api.github.com/users/elygre/gists{/gist_id}","starred_url":"https://api.github.com/users/elygre/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/elygre/subscriptions","organizations_url":"https://api.github.com/users/elygre/orgs","repos_url":"https://api.github.com/users/elygre/repos","events_url":"https://api.github.com/users/elygre/events{/privacy}","received_events_url":"https://api.github.com/users/elygre/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-11-18T09:24:47Z","updated_at":"2015-11-18T09:24:47Z","closed_at":null,"body":"While being discouraged, having a way of ordering tests is useful to some people. The JUnit4 @FixMethodOrder-annotation specifically and deliberately (https://github.com/matthewfarwell/junit/commit/c610a49727858597d9a10289bed0a0174053a69f#diff-429e0417e6fa5ece80ea7817add1daa7R46) makes it impossible to implement a simple ordering scheme, forcing users who want/need this to resort to method names like \"test245_ensureReasonableTestName()\".\r\n\r\n* The minimal \"requirement\" would be to allow users to write their own MethodSorter for @FixMethodOrder\r\n* A reasonable implementation would be to allow @FixMethodOrder(ORDERED), and then @Order(integer) to specify individual tests. Tests could be run from smallest number to highest, with un-annotated methods having a default of 0. Methods with the same order could be run in parallel; different order tiers could not."}}