{"action":"opened","issue":{"url":"https://api.github.com/repos/tarpas/testmon/issues/7","labels_url":"https://api.github.com/repos/tarpas/testmon/issues/7/labels{/name}","comments_url":"https://api.github.com/repos/tarpas/testmon/issues/7/comments","events_url":"https://api.github.com/repos/tarpas/testmon/issues/7/events","html_url":"https://github.com/tarpas/testmon/issues/7","id":63223028,"number":7,"title":"per-method granularity","user":{"login":"tarpas","id":135344,"avatar_url":"https://avatars.githubusercontent.com/u/135344?v=3","gravatar_id":"","url":"https://api.github.com/users/tarpas","html_url":"https://github.com/tarpas","followers_url":"https://api.github.com/users/tarpas/followers","following_url":"https://api.github.com/users/tarpas/following{/other_user}","gists_url":"https://api.github.com/users/tarpas/gists{/gist_id}","starred_url":"https://api.github.com/users/tarpas/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/tarpas/subscriptions","organizations_url":"https://api.github.com/users/tarpas/orgs","repos_url":"https://api.github.com/users/tarpas/repos","events_url":"https://api.github.com/users/tarpas/events{/privacy}","received_events_url":"https://api.github.com/users/tarpas/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-03-20T12:54:43Z","updated_at":"2015-03-20T12:54:43Z","closed_at":null,"body":"In current version we are tracking changes on file/module level. That is fine for many projects but suboptimal if you had a lot of functionality split into only a couple of files (e.g. pytest itself is a good example)\r\nAnd editing of test methods was kinda annoying because, every test change triggered execution of all the tests in a file. \r\nOf course coverage.py provides line granularity so it should be possible (if somewhat messy) to be more precise. But, in Python, you can break any execution unit without changing any of it's lines, by simply adding statemets after the block. Would it be possible to mitigate this by simply adding adjecent (non whitespace) lines to the change tracking? Maybe.\r\nFor now I have an ugly-code experiment which uses python \"ast\".\r\nhttps://www.youtube.com/watch?v=IJRdQKumCuE"}}