{"action":"closed","issue":{"url":"https://api.github.com/repos/CocoaPods/pod-template/issues/114","labels_url":"https://api.github.com/repos/CocoaPods/pod-template/issues/114/labels{/name}","comments_url":"https://api.github.com/repos/CocoaPods/pod-template/issues/114/comments","events_url":"https://api.github.com/repos/CocoaPods/pod-template/issues/114/events","html_url":"https://github.com/CocoaPods/pod-template/issues/114","id":84214137,"number":114,"title":"`pod lib create` creates tests outside of tested library module","user":{"login":"nikita-leonov","id":991541,"avatar_url":"https://avatars.githubusercontent.com/u/991541?v=3","gravatar_id":"","url":"https://api.github.com/users/nikita-leonov","html_url":"https://github.com/nikita-leonov","followers_url":"https://api.github.com/users/nikita-leonov/followers","following_url":"https://api.github.com/users/nikita-leonov/following{/other_user}","gists_url":"https://api.github.com/users/nikita-leonov/gists{/gist_id}","starred_url":"https://api.github.com/users/nikita-leonov/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/nikita-leonov/subscriptions","organizations_url":"https://api.github.com/users/nikita-leonov/orgs","repos_url":"https://api.github.com/users/nikita-leonov/repos","events_url":"https://api.github.com/users/nikita-leonov/events{/privacy}","received_events_url":"https://api.github.com/users/nikita-leonov/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":15,"created_at":"2015-06-02T21:13:31Z","updated_at":"2015-06-03T18:28:16Z","closed_at":"2015-06-03T18:28:16Z","body":"Moved conversation from here — https://github.com/CocoaPods/CocoaPods/issues/3633\r\n\r\nCurrently `pod lib create` for Swift project creates all tests as separate library. Which was fine for ObjC project, but not very comfy for Swift as we can not tests internal methods anymore that are visible only within module. \r\n\r\nPublic interfaces could be much smaller than an actual internal implementation, so resulting tests looks like a functional / integration tests rather than unit-tests. For some libraries it may work, for some not. \r\n\r\nWould it be better to provide an option to decide in a wizard where tests should be created and keep it up to developer to decide? "}}