{"action":"created","issue":{"url":"https://api.github.com/repos/jquery/qunit/issues/928","repository_url":"https://api.github.com/repos/jquery/qunit","labels_url":"https://api.github.com/repos/jquery/qunit/issues/928/labels{/name}","comments_url":"https://api.github.com/repos/jquery/qunit/issues/928/comments","events_url":"https://api.github.com/repos/jquery/qunit/issues/928/events","html_url":"https://github.com/jquery/qunit/issues/928","id":131121125,"number":928,"title":"Add a Stop Execution button up top","user":{"login":"tundal45","id":59220,"avatar_url":"https://avatars.githubusercontent.com/u/59220?v=3","gravatar_id":"","url":"https://api.github.com/users/tundal45","html_url":"https://github.com/tundal45","followers_url":"https://api.github.com/users/tundal45/followers","following_url":"https://api.github.com/users/tundal45/following{/other_user}","gists_url":"https://api.github.com/users/tundal45/gists{/gist_id}","starred_url":"https://api.github.com/users/tundal45/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tundal45/subscriptions","organizations_url":"https://api.github.com/users/tundal45/orgs","repos_url":"https://api.github.com/users/tundal45/repos","events_url":"https://api.github.com/users/tundal45/events{/privacy}","received_events_url":"https://api.github.com/users/tundal45/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-02-03T18:59:46Z","updated_at":"2016-02-17T19:05:13Z","closed_at":null,"body":"This might be just me but I feel that there are times where you want to run all the tests until their is a particular type of failure that you want to focus on. However, getting to that error to click rerun while the tests are running is impossible. So I was wondering if it would be useful to have a button that stops test execution and retains the results view up until that point.\r\n\r\n1. Is this possible?\r\n2. Will people who are not me find this useful?\r\n3. Where should I begin (assuming 1 & to are affirmative)?"},"comment":{"url":"https://api.github.com/repos/jquery/qunit/issues/comments/185352625","html_url":"https://github.com/jquery/qunit/issues/928#issuecomment-185352625","issue_url":"https://api.github.com/repos/jquery/qunit/issues/928","id":185352625,"user":{"login":"trentmwillis","id":3526753,"avatar_url":"https://avatars.githubusercontent.com/u/3526753?v=3","gravatar_id":"","url":"https://api.github.com/users/trentmwillis","html_url":"https://github.com/trentmwillis","followers_url":"https://api.github.com/users/trentmwillis/followers","following_url":"https://api.github.com/users/trentmwillis/following{/other_user}","gists_url":"https://api.github.com/users/trentmwillis/gists{/gist_id}","starred_url":"https://api.github.com/users/trentmwillis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/trentmwillis/subscriptions","organizations_url":"https://api.github.com/users/trentmwillis/orgs","repos_url":"https://api.github.com/users/trentmwillis/repos","events_url":"https://api.github.com/users/trentmwillis/events{/privacy}","received_events_url":"https://api.github.com/users/trentmwillis/received_events","type":"User","site_admin":false},"created_at":"2016-02-17T19:05:13Z","updated_at":"2016-02-17T19:05:13Z","body":"In my personal experience, when dealing with a large test suite this is definitely desirable. Especially when dealing with debugging a flaky test that is dependent on test order.\r\n\r\nI know Ember currently supports this with a [`pauseTest` helper that returns a non-resolving promise](http://emberjs.com/api/classes/Ember.Test.html#method_pauseTest), but this only works when invoked from within a test. I don't think it would be difficult to implement a similar feature that is invoked from the UI.\r\n\r\nThat said, we'd need to establish a more rigorous definition of what this behavior is: do we pause immediately or do we wait for the current test and associated hooks to finish? Do we allow tests to be unpaused? Will this pause count against the test suite's timeout limit?"}}