{"action":"closed","issue":{"url":"https://api.github.com/repos/vuejs/vue-test-utils/issues/1400","repository_url":"https://api.github.com/repos/vuejs/vue-test-utils","labels_url":"https://api.github.com/repos/vuejs/vue-test-utils/issues/1400/labels{/name}","comments_url":"https://api.github.com/repos/vuejs/vue-test-utils/issues/1400/comments","events_url":"https://api.github.com/repos/vuejs/vue-test-utils/issues/1400/events","html_url":"https://github.com/vuejs/vue-test-utils/issues/1400","id":547657809,"node_id":"MDU6SXNzdWU1NDc2NTc4MDk=","number":1400,"title":"Add clarifying content for Vue lifecycle hooks","user":{"login":"wes-harper-ibotta","id":51423600,"node_id":"MDQ6VXNlcjUxNDIzNjAw","avatar_url":"https://avatars1.githubusercontent.com/u/51423600?v=4","gravatar_id":"","url":"https://api.github.com/users/wes-harper-ibotta","html_url":"https://github.com/wes-harper-ibotta","followers_url":"https://api.github.com/users/wes-harper-ibotta/followers","following_url":"https://api.github.com/users/wes-harper-ibotta/following{/other_user}","gists_url":"https://api.github.com/users/wes-harper-ibotta/gists{/gist_id}","starred_url":"https://api.github.com/users/wes-harper-ibotta/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/wes-harper-ibotta/subscriptions","organizations_url":"https://api.github.com/users/wes-harper-ibotta/orgs","repos_url":"https://api.github.com/users/wes-harper-ibotta/repos","events_url":"https://api.github.com/users/wes-harper-ibotta/events{/privacy}","received_events_url":"https://api.github.com/users/wes-harper-ibotta/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2020-01-09T18:53:18Z","updated_at":"2020-01-10T05:24:29Z","closed_at":"2020-01-10T05:24:29Z","author_association":"NONE","body":"### What problem does this feature solve?\r\nThis gives further explanation about how `mount` and `shallowMount` behave in conjunction with test runners, clarifying expectations for developers about how their component will be treated during and after each test.\r\n\r\nI recently encountered a scenario where an intermittent test timeout occurred due to a `setInterval` created in the `mounted` hook, expecting the component to be destroyed (and the interval subsequently cleared) by vue-test-utils at the end of the spec.\r\n\r\n### What does the proposed API look like?\r\nThis is a simple addition to the `common-tips` section of the test utils docs with an example. I propose that the lifecycle hooks that can be expected to run automatically during each spec be elaborated on briefly after the \"Shallow Rendering\" section.\r\n\r\n<!-- generated by vue-issues. DO NOT REMOVE -->"}}
{"actor":{"display_login":"JessicaSachs"}}