ios iTunes Testflight beta 测试中内部和外部测试人员之间的区别?
声明:本页面是StackOverFlow热门问题的中英对照翻译,遵循CC BY-SA 4.0协议,如果您需要使用它,必须同样遵循CC BY-SA许可,注明原文地址和作者信息,同时你必须将它归于原作者(不是我):StackOverFlow
原文地址: http://stackoverflow.com/questions/28802883/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Difference between internal and external testers in iTunes Testflight beta testing?
提问by Deepak Thakur
Can anyone please explain in complete details the difference between internal and external testers in iTunes Connect Testflight beta testing? The difference here is just too brief. Does internal testers need to add UDID's of upto 10 devices? Or did apple completely removed UDID requirement now?
任何人都可以完整详细地解释iTunes Connect Testflight beta 测试中内部和外部测试人员之间的区别吗?这里的区别太简短了。内部测试人员是否需要添加最多 10 个设备的 UDID?还是苹果现在完全取消了UDID要求?
Can someone please explain what needs to be done to distribute and test app of upto 1000 users? If I have the clients iTunes Connect credentials, how do I share the app from his own account?
有人可以解释一下需要做什么来分发和测试最多 1000 个用户的应用程序吗?如果我有客户的 iTunes Connect 凭据,我如何从他自己的帐户共享应用程序?
I know that there are too many questions asked in this thread which is against stackoverflow's policy, but i only need do's and don'ts of internal and external testing of this awful itunes connect testflight beta testing.
我知道在这个线程中提出了太多问题,这违反了 stackoverflow 的政策,但我只需要对这个糟糕的 iTunes 连接testflight beta 测试进行内部和外部测试。
回答by Aaron Brager
Internal Testersmust be assigned the Admin, Technical, App Manager, Developer, or Marketer role in iTunes Connect, and you can only have 25 of them. You should review the iTunes Connect Roles. If you don't trust someone with these privileges, they aren't "Internal", they're "External".
内部测试人员必须被分配到 iTunes Connect 中的管理员、技术人员、应用程序经理、开发人员或营销人员角色,并且您只能拥有其中的 25 个角色。您应该查看iTunes Connect Roles。如果您不信任拥有这些特权的人,他们就不是“内部”,而是“外部”。
You can have many more External users, but apps need to go through the App Store review process before these users can test them:
您可以拥有更多外部用户,但应用程序需要先通过 App Store 审核流程,然后这些用户才能对其进行测试:
Apps made available to external testers require a Beta App Review and must comply with the full App Store Review Guidelines before testing can begin. A review is required for new versions of your app that contain significant changes. Up to 10 apps can be tested at a time, internally or externally.
可供外部测试人员使用的应用程序需要进行 Beta 版应用程序审核,并且必须符合完整的 App Store 审核指南,然后才能开始测试。您的应用的新版本包含重大更改,需要进行审核。一次最多可以在内部或外部测试 10 个应用程序。
回答by jungledev
Upload your app to TestFlight
将您的应用上传到 TestFlight
Both internal and external testers will install your app from the TestFlight app. Once invited, they will be sent an email asking them to install the TestFlight app. Once they have done so, they'll be able to install your beta app...
内部和外部测试人员都将从 TestFlight 应用程序安装您的应用程序。收到邀请后,他们将收到一封电子邮件,要求他们安装 TestFlight 应用程序。完成此操作后,他们将能够安装您的测试版应用...
Internal Testers:Think of these users as employees who receive instant updates to your app without approval/review
内部测试人员:将这些用户视为未经批准/即可收到应用程序即时更新的员工
- Must be added manually via iTC
- 25 Max allowed
- Once your app is uploaded it's available immediatelyfor internal testers (before it has been reviewed)
- All internal testers must be added as a user in your iTC "Users and Roles" settings, which gives them certain permissions (review other answers and the docs for this). You wouldn't want to give just anyone permissions here.
- Do not have a 60-day time limit
- 必须通过 iTC 手动添加
- 25 最大允许
- 应用上传后,内部测试人员可以立即使用(在审核之前)
- 所有内部测试人员都必须在您的 iTC“用户和角色”设置中添加为用户,这为他们提供了一定的权限(查看其他答案和文档)。您不会想在此处授予任何人权限。
- 没有 60 天的时间限制
External Testers
外部测试人员
Will only be able to use your uploaded build for up to 60 days. If you add additional builds, they can update, and the 60 days starts over again.
Will be able to test your app after
- You have submitted it for review
- It gets approved in TestFlight review and
- You set it to be available for testing. The review process us usually instant for new builds with the same version number. If you add a new version number, the review process can take up to 48hrs as of 10/2016.
Can be added automatically by importing a
csv
file or with Fastlane'spilotautomation tool.As of now (August 2016), up to 2000 email addresses can be added. Each email address will allow a user to install the app on multiple devices. The email addresses do notneed to match their Apple IDs.
They receive an invite to install your app once your first build is available for testing. If you add a new user after making a build available for testing, they'll immediately receive an invite. All users will receive notifications to install newer versions of the app if you upload additional builds.
Will be disallowed from using your app after you have pushed it to the official app store (which promptly ends the beta) or 60 days have passed since you started the beta, whichever comes first.If you end the beta without launching in the app store, and they try to open it, it will crash. Yay, Apple UX! If you do push a version to the app store with the same bundleName, version, and bundleID (build number doesn't matter), then your beta testers will automatically receive the app-store version of the app when it goes live.
最多只能使用您上传的版本 60 天。如果您添加其他构建,它们可以更新,并且 60 天重新开始。
之后将能够测试您的应用程序
- 您已提交审核
- 它在 TestFlight 中获得批准,并且
- 您将其设置为可用于测试。对于具有相同版本号的新版本,我们通常会立即进行。如果您添加新版本号,截至 2016 年 10 月,审核过程最多可能需要 48 小时。
可以通过导入
csv
文件或使用Fastlane 的试验自动化工具自动添加。截至目前(2016 年 8 月),最多可以添加 2000 个电子邮件地址。每个电子邮件地址将允许用户在多个设备上安装该应用程序。该电子邮件地址也没有需要,以满足他们的苹果标识。
一旦您的第一个构建版本可供测试,他们就会收到安装您的应用程序的邀请。如果您在构建可用于测试后添加新用户,他们将立即收到邀请。如果您上传其他版本,所有用户都将收到安装更新版本应用程序的通知。
在您将应用推送到官方应用商店(即会立即结束测试版)后或从您开始测试后 60 天(以先到者为准)后,将被禁止使用您的应用。如果您在未在应用商店中启动的情况下结束测试版,而他们尝试打开它,它将崩溃。是的,苹果用户体验!如果您确实将具有相同 bundleName、版本和 bundleID(版本号无关紧要)的版本推送到应用商店,那么您的 Beta 测试人员将在该应用上线时自动收到该应用的应用商店版本。
回答by John
Internal Testester
内部测试员
- Email id should be used with apple account
- Internal tester will be a member of developer account. Roles may be Admin, Technical, Manager, Developer, Marketer
- Only 25 internal testers are allowed
- Each tester can test on upto 30 devices
- Can test 100 apps at a time
- Build remains active for 90 days
- No app beta review
- 电子邮件 ID 应与苹果帐户一起使用
- 内部测试人员将成为开发者帐户的成员。角色可以是管理员、技术人员、经理、开发人员、营销人员
- 只允许 25 名内部测试人员
- 每个测试仪最多可测试 30 台设备
- 一次可以测试 100 个应用
- 构建保持活动状态 90 天
- 没有应用测试版审核
External Tester
外部测试仪
- Email id need not to be used with apple account
- 10,000 external testers are allowed
- Can test 100 apps at a time
- Build remains active for 90 days
- App required beta review.
- 电子邮件 ID 不需要与苹果帐户一起使用
- 允许 10,000 名外部测试人员
- 一次可以测试 100 个应用
- 构建保持活动状态 90 天
- 应用程序需要测试版。
回答by Gaurav Singla
iOS app testing for getting early feedbacks may be done in multiple ways. Enterprise, Adhoc and the new iOS8 Testflight Beta testing
用于获取早期反馈的 iOS 应用测试可以通过多种方式完成。Enterprise、Adhoc 和新的 iOS8 Testflight Beta 测试
Ad-hoc Provisioning
临时供应
In this method the focus is on devices rather than the users. The devices UDID need to be registered in member center and the deployment profile MUST have the UDID of the specific device to download the app build. The app may be hosted on testflight or even dropbox (Only https: is supported).
在这种方法中,重点是设备而不是用户。设备 UDID 需要在会员中心注册,并且部署配置文件必须具有特定设备的 UDID 才能下载应用程序版本。该应用程序可能托管在 testflight 甚至 Dropbox 上(仅支持 https:)。
TestFlight Beta Testing for iOS applications:
iOS 应用程序的 TestFlight Beta 测试:
UDID is no longer required. The focus is on test users rather than device. A single user may have multiple devices on which the beta app may be installed.
不再需要 UDID。重点是测试用户而不是设备。单个用户可能有多个设备,可以在其中安装 Beta 版应用程序。
For the Test Users of Beta Testing please refer to the "Aaron Brager's" Answer.
Beta 测试的测试用户请参考“Aaron Brager 的”回答。