{"action":"opened","issue":{"url":"https://api.github.com/repos/vmware/vic/issues/7514","repository_url":"https://api.github.com/repos/vmware/vic","labels_url":"https://api.github.com/repos/vmware/vic/issues/7514/labels{/name}","comments_url":"https://api.github.com/repos/vmware/vic/issues/7514/comments","events_url":"https://api.github.com/repos/vmware/vic/issues/7514/events","html_url":"https://github.com/vmware/vic/issues/7514","id":305255126,"number":7514,"title":"Address gaps in VCH Management API testing","user":{"login":"zjs","id":408880,"avatar_url":"https://avatars2.githubusercontent.com/u/408880?v=4","gravatar_id":"","url":"https://api.github.com/users/zjs","html_url":"https://github.com/zjs","followers_url":"https://api.github.com/users/zjs/followers","following_url":"https://api.github.com/users/zjs/following{/other_user}","gists_url":"https://api.github.com/users/zjs/gists{/gist_id}","starred_url":"https://api.github.com/users/zjs/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zjs/subscriptions","organizations_url":"https://api.github.com/users/zjs/orgs","repos_url":"https://api.github.com/users/zjs/repos","events_url":"https://api.github.com/users/zjs/events{/privacy}","received_events_url":"https://api.github.com/users/zjs/received_events","type":"User","site_admin":false},"labels":[{"id":317677446,"url":"https://api.github.com/repos/vmware/vic/labels/area/apis","name":"area/apis","color":"f9d0c4","default":false},{"id":530073666,"url":"https://api.github.com/repos/vmware/vic/labels/component/test","name":"component/test","color":"d4c5f9","default":false},{"id":327809115,"url":"https://api.github.com/repos/vmware/vic/labels/component/vic-machine","name":"component/vic-machine","color":"d4c5f9","default":false},{"id":318105115,"url":"https://api.github.com/repos/vmware/vic/labels/kind/quality","name":"kind/quality","color":"bfd4f2","default":false},{"id":680163695,"url":"https://api.github.com/repos/vmware/vic/labels/team/lifecycle","name":"team/lifecycle","color":"c2e0c6","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-14T17:23:18Z","updated_at":"2018-03-14T17:23:18Z","closed_at":null,"author_association":"MEMBER","body":"#7501 defined a test plan for existing VCH Management API functionality and identified gaps between that desired end state and the tests that exist today. This epic tracks the work to close those gaps.\r\n\r\nThere are a few natural ways to divide that work, such as dividing it based on the feature being tested (create, list, inspect, delete) or based on the type of test case (positive, negative, interoperability, concurrency). It's not clear that any such division would be the \"correct\" division (or even what \"correct\" would mean in this context). Instead of striving for some optimal decomposition, this Epic will attempt to capture reasonably cohesive and reasonably tractable increments of work. If it becomes clear, as progress is made on an an issue, that further decomposition would be helpful, assignees should feel free to do so on a case-by-case basis.\r\n\r\nThe overall goal for this epic is as captured in the summary: address gaps in VCH Management API testing. The test cases identified by the test plan may insufficient in some ways and overkill in others. We should continually adjust the plan as we learn more, focusing on this overall goal. (For example, if a defect is discovered during this process, we should think about other tests we might want to introduce to test for related issues.)"}}
{"actor":{"display_login":"zjs"}}