As a user
I want to be able to create a beta tester assigned to a group, a build, or an app by their email address, first and last name,
So that he/she can receive the invitation, get the access and download the app from TestFlight

Covering this API.

🗣 Context

We have issue #12, and creating beta testers is one of the main features of AppStoreConnect API.
But it can't cover all the use cases, and we want to do more about TestFlight testers

💬 Narrative

As a user
I want to be able to

• list all the beta testers for an app,
• read one or more beta tester's info
• removing one or more beta tester

So that I can have better management of all the beta testers
Covering APIs

1. list
2. info
3. delete

✅ Acceptance Criteria

• I can use the command list to see a list of all the beta testers of an app, by inputting app's bundleId
• I can input beta testers' emails, to get specific beta testers info
• I can input beta testers' emails to delete one or more beta testers

🚫 Out of Scope

This Issues not relevant to Beta Groups, we will have another issue for Beta Groups

Given that this tool is likely to be run from CI or by a user interactively we will need multiple ways of feeding authentication credentials (API key).

We should support specifying the credentials via the environment (to support CI).

Possible environment keys:

• APPSTORE_ISSUER_ID
• APPSTORE_KEY_ID
• APPSTORE_KEY

We can also read the this from some sort of ~/.appstoreconnect-cli/auth.{yml,json} file. We should ensure that this file and directory is mode 0600 and owned by the running user for security sake.

We could also support the behaviour that altool does for command-line arguments, eg:

--apiKey <api_key>        API Key. Required for JWT authentication while using 
validation, upload, and notarization. This option will search the following 
directories in sequence for a private key file with the name of 
'AuthKey_<api_key>.p8': './private_keys', '~/private_keys', '~/.private_keys', 
and '~/.appstoreconnect/private_keys'.
--apiIssuer <issuer_id>   Issuer ID. Required if --apiKey is specified.

❕ Problem Statement

We don't have a LICENSE.md file.

💬 Task Description

Create a license file with the MIT License.

🗣 Context

Get a specific beta tester.

💬 Narrative

As a user
I want to get the information of a specific beta tester
So that I can view it

📝 Notes

Covering this API.

🎨 Design

asc testflight betatesters read emailAddress

Output:

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...

🗣 Context

We need to be able to invite beta testers to an organisation and give them access to apps.

💬 Narrative

As a User
I want to be able to invite beta tester become testers of specific apps in my organisation
So that they can install those apps on their devices

🎨 Design

Example command:

asc testflight betatesters invite [email protected] Joe Example com.iba.app1 --groups "Group 1" "Group 2"

The above command invites the user to be a tester of an app and adds them to two groups.

• On success print the beta testers info as returned by the API.

✅ Acceptance Criteria

GIVEN there is no existing beta tester with the email address [email protected]
WHEN I issue the command asc testflight betatesters invite [email protected] com.iba.app1 --groups "Group 1" "Group 2"
THEN the specified user is invited and the relationships with the specified app and groups are established
AND the details of the invited user are displayed to stdout

GIVEN there is no existing "Group 1" beta group for app com.iba.app1
WHEN I issue the command asc testflight betatesters invite [email protected] com.iba.app1 --groups "Group 1" "Group 2"
THEN an error is displayed No Beta Group "Group 1" exists for application with Bundle ID "com.iba.app1". to stderr and there is no output to stdout.

🚫 Out of Scope

• Adding inviting a beta tester a multiple apps at once.
• Inviting a user to test a specific build of an app.

🗣 Context

To increase the flexibility of the tool it should support reading and writing data from CSV files. Examples of data that would make good use of CSV:

• TestFlight Beta Group user lists
• AppStore connect Users

💬 Narrative

As a user
I want to be able to read certain input as CSV data.
So that I can use tools like Numbers or Excel to make it easier maintain that data.

📝 Notes

There is already an implementation of Codable for CSV that we can take advantage of.

• Important Note: At the moment CodableCSV only supports decoding, encoding is on the roadmap. See dehesa/CodableCSV#2

✅ Acceptance Criteria

GIVEN I have am issuing a command
WHEN I specify the option --output-format csv
THEN the resulting output should be formatted as CSV

GIVEN I have am issuing a command such as appstoreconnect-cli users sync
WHEN I specify the input file ending in .csv
THEN the input file is parsed as CSV data.

🗣 Context

Find and list beta groups for all apps.

💬 Narrative

As a User
I want to list my beta groups
So that I can see what groups have been configured

📝 Notes

Covering this API.

🎨 Design

asc testflight betagroup list

Input:
There are multiple filters that can be applied, we should choose the most relevant ones for initial release.

Output:

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...

🚫 Out of Scope

Describe what is out of scope

As a user
I want to be able to list all the apps on my App Store connect account.
So that I can review them.

• The output should be in a tabular format
• The output should also be able to be rendered for easy consumption by other tools or for writing out to YAML or JSON.

Covering API.

🗣 Context

Create a new certificate using a certificate signing request.

💬 Narrative

As a user
I want create a certificate
So that so that I can use it with a provisioning profile.

📝 Notes

Covering this API.

🎨 Design

asc certificates create ios_development --csrFile CertificateRequest.csr

✅ Acceptance Criteria

GIVEN I provide a valid certificate type and CSR
WHEN I issue a create command
THEN a certificate is created.

GIVEN I provide a invalid certificate type or CSR
WHEN I issue a create command
THEN I receive an appropriate error message.

GIVEN I provide valid inputs to the create command
WHEN the API fails
THEN I receive an appropriate error message.

🚫 Out of Scope

• Creating the CSR. It is assumed the user has done that correctly with KeyChain Access already.

🤔 Future Directions

• Create the CSR for the user using macOS Security APIs.

🗣 Context

Get a specific beta group and display its information.

💬 Narrative

As a ...
I want ...
So that ...

📝 Notes

Covering this API.

🎨 Design

Provide design example, screenshot, text input/output etc

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...

🚫 Out of Scope

Describe what is out of scope

🗣 Context

This tool could be used by a world wide audience. Our displayed output should at least support localisation.

💬 Narrative

As an international user
I want output to be in my default locale
So that so that I don't need to know English in order to use the application effectively

🚫 Out of Scope

The actual translation of messages.

🗣 Context

Disable a capability for a bundle ID.

💬 Narrative

As a use
I want disable a capability for a bundle ID
So that my app no longer can use that capability.

📝 Notes

Covering this API.

🎨 Design

asc capability disable bundleId capabilityType

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...

As a user
I would like to be able to run appstoreconnect-cli on Linux
So that I can run it on Linux CI hosts

Get tool build/running on Linux so users don't pay 10x for GitHub macOS runners.

We can then also build Docker based GitHub actions based on this tool.

🗣 Context

Download finance reports filtered by your specified criteria.

💬 Narrative

As a user
I want to download my app's financial reports
So that so that I can analyse the data offline

📝 Notes

Covering this API.

🎨 Design

asc reports financial regionCode reportDate reportType vendorNumber outputFilename

✅ Acceptance Criteria

GIVEN I specify valid input
WHEN I issue the command
THEN data is written to the specified outpoutFilename

GIVEN I specify invalid input
WHEN I issue the command
THEN I receive an appropriate error message

GIVEN I issue the command
WHEN the API fails
THEN I receive an appropriate error message

GIVEN I issue the command
WHEN no data is available
THEN I receive an appropriate error message

🗣 Context

Get information about a certificate and download the certificate data.

💬 Narrative

As a user
I want to display information about a certificate and optionally download the certificate file
So that I can inspect the certificate

📝 Notes

Covering this API.

🎨 Design

asc certificates read  XXYYZZ --certificate-output ./file.cer 

Output:

"📥 Certificate '(serial)' downloaded to: (certificateOutput)"

✅ Acceptance Criteria

GIVEN I provide a valid input without --certificate-output
WHEN I issue a read command
THEN the certificate's information is displayed (as above).

GIVEN I provide valid input with --certificate-output
WHEN I issue a list command
THEN the certificate's information is displayed and the certificate data is written to the specified file.

GIVEN I provide a invalid input
WHEN I issue a list command
THEN I receive an appropriate error message.

GIVEN I provide valid inputs to the list command
WHEN the API fails
THEN I receive an appropriate error message.

🚫 Out of Scope

• Displaying the decoded certificate contents.

🤔 Future Directions

• The the X.509 certificate information could be displayed like:

Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            10:e6:fc:62:b7:41:8a:d5:00:5e:45:b6
        Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=BE, O=GlobalSign nv-sa, CN=GlobalSign Organization Validation CA - SHA256 - G2
        Validity
            Not Before: Nov 21 08:00:00 2016 GMT
            Not After : Nov 22 07:59:59 2017 GMT
        Subject: C=US, ST=California, L=San Francisco, O=Wikimedia Foundation, Inc., CN=*.wikipedia.org
        Subject Public Key Info:
            Public Key Algorithm: id-ecPublicKey
                Public-Key: (256 bit)
            pub: 
                    00:c9:22:69:31:8a:d6:6c:ea:da:c3:7f:2c:ac:a5:
                    af:c0:02:ea:81:cb:65:b9:fd:0c:6d:46:5b:c9:1e:
                    9d:3b:ef
                ASN1 OID: prime256v1
                NIST CURVE: P-256
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Agreement
            Authority Information Access: 
                CA Issuers - URI:http://secure.globalsign.com/cacert/gsorganizationvalsha2g2r1.crt
                OCSP - URI:http://ocsp2.globalsign.com/gsorganizationvalsha2g2
            X509v3 Certificate Policies: 
                Policy: 1.3.6.1.4.1.4146.1.20
                  CPS: https://www.globalsign.com/repository/
                Policy: 2.23.140.1.2.2
            X509v3 Basic Constraints: 
                CA:FALSE
            X509v3 CRL Distribution Points: 
                Full Name:
                  URI:http://crl.globalsign.com/gs/gsorganizationvalsha2g2.crl
            X509v3 Subject Alternative Name: 
                DNS:*.wikipedia.org, DNS:*.m.mediawiki.org, DNS:*.m.wikibooks.org, DNS:*.m.wikidata.org, DNS:*.m.wikimedia.org, DNS:*.m.wikimediafoundation.org, DNS:*.m.wikinews.org, DNS:*.m.wikipedia.org, DNS:*.m.wikiquote.org, DNS:*.m.wikisource.org, DNS:*.m.wikiversity.org, DNS:*.m.wikivoyage.org, DNS:*.m.wiktionary.org, DNS:*.mediawiki.org, DNS:*.planet.wikimedia.org, DNS:*.wikibooks.org, DNS:*.wikidata.org, DNS:*.wikimedia.org, DNS:*.wikimediafoundation.org, DNS:*.wikinews.org, DNS:*.wikiquote.org, DNS:*.wikisource.org, DNS:*.wikiversity.org, DNS:*.wikivoyage.org, DNS:*.wiktionary.org, DNS:*.wmfusercontent.org, DNS:*.zero.wikipedia.org, DNS:mediawiki.org, DNS:w.wiki, DNS:wikibooks.org, DNS:wikidata.org, DNS:wikimedia.org, DNS:wikimediafoundation.org, DNS:wikinews.org, DNS:wikiquote.org, DNS:wikisource.org, DNS:wikiversity.org, DNS:wikivoyage.org, DNS:wiktionary.org, DNS:wmfusercontent.org, DNS:wikipedia.org
            X509v3 Extended Key Usage: 
                TLS Web Server Authentication, TLS Web Client Authentication
            X509v3 Subject Key Identifier: 
                28:2A:26:2A:57:8B:3B:CE:B4:D6:AB:54:EF:D7:38:21:2C:49:5C:36
            X509v3 Authority Key Identifier: 
                keyid:96:DE:61:F1:BD:1C:16:29:53:1C:C0:CC:7D:3B:83:00:40:E6:1A:7C

    Signature Algorithm: sha256WithRSAEncryption
         8b:c3:ed:d1:9d:39:6f:af:40:72:bd:1e:18:5e:30:54:23:35:
         ...

❕ Problem Statement

We currently call directly into AppStoreConnect_Swift_SDK and couple ourselves to it by directly making use of it from our commands

We mix and match whether we use AppStoreConnect_Swift_SDK models (with extensions) or if we translate into our own Models

It's reaching the point where we want our own consistent Model layer and to abstract the knowledge of AppStoreConnect_Swift_SDK away from our commands

💬 Task Description

• Create Models for use in all our commands
• Create an API Client that calls through to AppStoreConnect_Swift_SDK and translates the library model types to our model types

👩‍🔧 Technical Design Notes

We should structure our models with consideration for table formats, some models we use are quite nested
If we are to support pretty output tables and csv we need a flat structure that can print models row by row

🤝 Relationships

#24
This work is needed to output CSV correctly as CSVDecoder does not support types that are nested more than two levels.

🗣 Context

Update the configuration of a specific capability.

💬 Narrative

As a user
I want modify a capability on a specific bundle ID
So that my app can use that capability

📝 Notes

Covering this API.

🎨 Design

asc capability modify bundleId capabilityType <capability settings>

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...

🗣 Context

Get a list of builds of a specific prerelease version.

💬 Narrative

As a ...
I want ...
So that ...

📝 Notes

Covering this API.

🎨 Design

Provide design example, screenshot, text input/output etc

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...

🚫 Out of Scope

Describe what is out of scope

🌎 Environment

• OS: macOS
• Version/Release: 10.15.2

💬 Description

The limit option for users list doesn't work. It returns the entire list.

🦶 Reproduction Steps

Steps to reproduce the behavior, provide an example of the command line issued:

1. Run this swift run asc users list --limit 5

🤔 Expected Results

Should return only 5 users if the limit is set as 5

😲 Actual Results

It returns the entire list

🗣 Context

Remove a specific beta tester from one or more beta groups, revoking their access to test builds associated with those groups.

💬 Narrative

As a user
I want remove an existing beta tester from beta groups
So that so I can manage user access

📝 Notes

Covering this API.

🎨 Design

asc testflight betatesters removegroup emailAddress groups...
asc testflight betagroup removeuser emailAddresses...

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...

🗣 Context

Add one or more beta testers to a specific beta group.

💬 Narrative

As a user
I want add an existing beta tester to beta groups
So that so I can manage user access

📝 Notes

Covering this API.

🎨 Design

asc testflight betatesters addgroup emailAddress groups...
asc testflight betagroup adduser emailAddresses...

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...

Cloning the codebase and running swift build currently fails

You must also generate the xcode project and build in xcode project
Finally building from the command line once more
Also creation of a bin directory allows the binary to be copied correctly (this is done from a scheme post action)

🗣 Context

Get a list of prerelease versions for all apps.

💬 Narrative

As a user
I want to list pre-release versions of my application
So that I can inspect the details

📝 Notes

Covering this API.

🎨 Design

asc testflight prereleaseversion list --filter-app <bundleId> --filter-build-processing-state <states...> --filter-builds-expired <bool?> --filter-platform <platforms...> --filter-version <versions...> --limit <n> --sort <order>

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...

🚫 Out of Scope

Describe what is out of scope

🗣 Context

Remove a beta tester's ability to test all apps.

💬 Narrative

As a user
I want to be able to delete beta testers
So that so that they can't see my apps anymore

📝 Notes

Covering this API.

🎨 Design

asc testflight beta-tester delete emailAddress

✅ Acceptance Criteria

GIVEN I have the email address of a beta tester
WHEN I issue the command
THEN the beta tester is deleted.

GIVEN I supply the email address of someone who is not a beta tester
WHEN I issue the command
THEN an appropriate error message is displayed

🗣 Context

Revoke a lost, stolen, compromised, or expiring signing certificate.

💬 Narrative

As a user
I want to revoke a compromised certificate
So that so that it can no longer be used to sign apps

📝 Notes

Covering this API.

🎨 Design

asc certificates revoke XCYZ ABCD EFGH

Output:

🚮 Certificate `XCYZ` revoked.
🚮 Certificate `ABCD ` revoked.
🚮 Certificate `EFGH ` revoked.

✅ Acceptance Criteria

GIVEN I provide a valid input
WHEN I issue a revoke command
THEN the certificates I specified are revoked.

GIVEN I provide some invalid input (eg, one of the serials I provide is invalid)
WHEN I issue a revoke command
THEN then NO certificates are revoked and I receive an appropriate error message.

As a user
I want to be able to list all the users registered on my App Store connect account
So that I can review them.

• The output should be in a tabular format. Using something like https://github.com/scottrhoyt/SwiftyTextTable or https://github.com/cfilipov/TextTable (pick the most suitable, or another).

• The output should also be able to be rendered for easy consumption by other tools or for writing out to YAML or JSON.

The CLI should support most of the options available on the API.

However:

• Don't support the ability to fetch sparse field sets.

🗣 Context

Download sales and trends reports filtered by your specified criteria.

💬 Narrative

As a user
I want to download my app's sales and trend reports
So that so that I can analyse the data offline

📝 Notes

Covering this API.

🎨 Design

asc reports sales frequency reportDate reportType reportSubType vendorNumber outputFilename --version version

✅ Acceptance Criteria

GIVEN I specify valid input
WHEN I issue the command
THEN data is written to the specified outpoutFilename

GIVEN I specify invalid input
WHEN I issue the command
THEN I receive an appropriate error message

GIVEN I issue the command
WHEN the API fails
THEN I receive an appropriate error message

GIVEN I issue the command
WHEN no data is available
THEN I receive an appropriate error message

❕ Problem Statement

At the moment we're not performing any form of CI, we should.

💬 Task Description

Set up GitHub Actions to build the project (and run unit tests) for Pull Requests.

👩‍🔧 Technical Design Notes

If we could get this project running on Linux we could use Linux GitHub Actions agents. macOS agents will be free when this project is public/Open Source. For private repos they cost 10x as much as Linux hosts.

🗣 Context

Create a beta group associated with an app, optionally enabling TestFlight public links.

💬 Narrative

As a user
I want create beta groups for my app
So that I can start adding beta testers to them

📝 Notes

Covering this API.

🎨 Design

asc testflight betagroup create appBundleId groupName --[no]-public-link --public-link-limit <n> 

Notes:

• We can use @Flag's support for negation with no prefix.
• The specification of a --public-link-limit implies that publicLinkLimitEnabled should be true in the BetaGroupCreateRequest.Data.Attributes.

Output:

✅ Acceptance Criteria

GIVEN I provide invalid input
WHEN I issue the command
THEN an appropriate error message should be displayed

GIVEN I provide valid input
WHEN I issue the command
THEN the output should be displayed

🗣 Context

Get information about a specific prerelease version.

💬 Narrative

As a ...
I want ...
So that ...

📝 Notes

Covering this API

🎨 Design

Provide design example, screenshot, text input/output etc

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...

🚫 Out of Scope

Describe what is out of scope

🗣 Context

Delete a beta group and remove beta tester access to associated builds.

💬 Narrative

As a ...
I want ...
So that ...

📝 Notes

Covering this API.

🎨 Design

Provide design example, screenshot, text input/output etc

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...

🚫 Out of Scope

Describe what is out of scope

🗣 Context

Beta Group is an essential part of the whole Test Flight workflow. When inviting a tester, we have to eight invite them to a specific build, or invite them to a group.

💬 Narrative

As a user
I want to be able to

1. creating, modifying, and deleting Beta Groups
2. getting Beta Group Information for an app (List, Read info)
   So that I can have better management of all the Beta Groups

Covering APIs

1. creating
2. modifying
3. deleting
4. list
5. info

✅ Acceptance Criteria

1. I can create a beta group for an app by it build Id
2. I can modify(change status) the specific beta group by it Id or name
3. I can delete groups
4. I can list all the groups related to an app,
5. I can get information about a specific group, by input its id or name

🚫 Out of Scope

BetaTester is in another issue #12

❕ Problem Statement

Every cool macOS command line tool needs to be installable with brew.

💬 Task Description

Create a homebrew formula for appstoreconnect-cli.

👩‍🔧 Technical Design Notes

See other projects that have formula for guidance.

• https://github.com/Homebrew/homebrew-core/blob/master/Formula/swiftlint.rb
• https://github.com/Homebrew/homebrew-core/blob/master/Formula/swiftformat.rb

As a user
I want to be able to synchronise AppStore Connect users with a file
So that I can keep my user configuration in source control and practice infrastructure-as-code principles with AppStore Connect.

I should be able to have a file that contains the canonical information about users in App Store Connect.

Ideally this command should not require state. It would consider the input files as the canonical source of information and push that into the AppStore Connect API.

You would have a file (yaml, csv, json) on disk that would have all the details of users, their roles and the apps they should have access to. If the CLI had the right level of permissions on the account it could create/delete/modify all users.

⚠️ The tool should support a --dry-run option that only prints what would happen and doesn't actually take action on the AppStore Connect API.

🚨Note that this sync function should never delete users with the ACCOUNT_HOLDER role. It probably can't anyway but it shouldn't try.

🗣 Context

Get information about a specific app.

💬 Narrative

As a ...
I want ...
So that ...

📝 Notes

Covering this API.

🎨 Design

Provide design example, screenshot, text input/output etc

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...

🚫 Out of Scope

Describe what is out of scope

❕ Problem Statement

At the moment we don't have any linting being performed during build.

💬 Task Description

Configure the build process to run SwiftLint with appropriate rules.

👩‍🔧 Technical Design Notes

We want to be pretty strict with our rules so we have a consistent looking codebase.

As a user
I want to be able to fetch the details of a user by email address
So that I can see details of this user, their roles and the apps they can see.

Covering this API.

• Again we don't need to support sparse field sets.

🗣 Context

Enable a capability for a bundle ID.

💬 Narrative

As a user
I want enable a capability on a specific bundle ID
So that my app can use that capability

📝 Notes

Covers this API.

🎨 Design

asc capability enable bundleId capabilityType <capability configuration options based on type>

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...

HTTPClient.deviceUDIDResourceId(matching:) will throw notUnique when nothing matches.
Should we throw a different error or no error at all?

Originally posted by @adamjcampbell in #75

As a user
I want to be able to register, modify or delete Bundle IDs,
So that the I can manage bundle IDs easily.

Covering this API.

❕ Problem Statement

We currently do not have a contributing guide for the project with guidance on how we expect people to contribute.

💬 Task Description

Define clear well articulated CONTRIBUTING.md and CODE_OF_CONDUCT.md files for the project.

👩‍🔧 Technical Design Notes

A good way to start this would be to take inspiration from some good documentation from another popular open source project.

🗣 Context

Find and list certificates and download their data.

💬 Narrative

As a user
I want list and/or download certificates
So that I can inspect them

📝 Notes

Covering this API.

🎨 Design

asc certificates list --filter-serial XXYYZZ --sort <sort> --filter-type <type> --filter-display-name <name> --limit 100 --download-path ./path 

Output:

"📥 Certificate '\(certificate.name)' downloaded to: \(path/serial.cer)"

✅ Acceptance Criteria

GIVEN I provide a valid input without a --download-path
WHEN I issue a list command
THEN the certificates I have are listed.

GIVEN I provide valid input with a --download-path
WHEN I issue a list command
THEN the certificates I have are listed
AND the certificates are saved to the specified path.

GIVEN I provide a invalid input
WHEN I issue a list command
THEN I receive an appropriate error message.

GIVEN I provide valid inputs to the list command
WHEN the API fails
THEN I receive an appropriate error message.

🚫 Out of Scope

• Importing certificates into the user's KeyChain.

🤔 Future Directions

• Certificates could be imported into the user's keychain via Security APIs.

❕ Problem Statement

Every cool open source project has a screenshot or gif that demonstrates how to use it.

💬 Task Description

Create an animated gif of the tool in use for prominent positioning in our README.

🎨 Design Notes

See example:

• https://github.com/jakubroztocil/httpie#readme

🤝 Relationships

• Other Related Issues: #25

🗣 Context

Modify a beta group's metadata, including changing its Testflight public link status.

💬 Narrative

As a ...
I want ...
So that ...

📝 Notes

Covering this API.

🎨 Design

Provide design example, screenshot, text input/output etc

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...

🚫 Out of Scope

Describe what is out of scope

As a user
I want to be able to invite users to my team
So that they can take a specific role in my development team for specific apps

Covering this API

🗣 Context

We have not yet implemented GetBetaTesterInfoCommand.

💬 Narrative

As a user
I want get all the information relating to a beta tester
So that so that I can view it.

📝 Notes

This should cover all the features of the API.

However we should use the beta tester's email address to find them rather than their opaque resource ID as is required by the API. So it might be easier to use the list API with a filter on email rather than call the Read Beta Tester Information API. I'm pretty sure the information returned is the same.

We should support --limit-apps, --limit-builds, --limit-beta-groups options to control the number of fetched apps, builds and betaGroups.

🎨 Design

asc testflight betatester info [email protected]

Output:

In YML and JSON formats more detailed data for the App and BetaGroups could be displayed based on the data fetched we should not be restricting the field set fetched.

✅ Acceptance Criteria

GIVEN a tester exists with the email address [email protected]
WHEN I specify the email address [email protected]
THEN the data for the user with the email address [email protected] should be displayed

GIVEN a tester does not exist with the email address [email protected]
WHEN I specify the email address [email protected]
THEN an error message Beta Tester for specified email address not found. should be displayed on stderr, no output should be sent to stdout.

GIVEN a tester exists with the email address [email protected] and has 10 associated apps
WHEN I specify the the arguments [email protected] --limit-apps 5
THEN only 5 apps should be displayed in the list of apps the user has associated with them.

💬 Description

Currently none of our commands support paging.

🦶 Reproduction Steps

Steps to reproduce the behavior, provide an example of the command line issued:

1. Run a command on a dataset that exceeds the default page limit.

🤔 Expected Results

That all pages of data are fetched.

😲 Actual Results

On the first page of data is fetched.

❕ Problem Statement

This project needs a logo. Every cool open source project needs a logo.

💬 Task Description

Create a cool logo for placement in the README.

🎨 Design Notes

Some examples of open source projects that have logos:

• https://github.com/iterative/dvc#readme
• https://github.com/NSRare/NSGIF#readme
• https://github.com/Alamofire/Alamofire#readme
• https://github.com/Redocly/redoc#readme
• https://github.com/sultan99/react-on-lambda#readme

🗣 Context

Find and list beta testers for all apps, builds, and beta groups.

💬 Narrative

As a user
I want to be able to list all the beta testers associated with my apps
So that so that I can view them.

📝 Notes

Covering this API.

🎨 Design

asc testflight betatesters list --filter-email <email address patterns> --filter-firstname <firstnames> --filter-lastname <lastnames> --filter-invite-type <invite type> --filter--fliter-apps <bundle ids> --filter-beta-groups <beta group list> --limit <n> --sort <sort options>

Output:

✅ Acceptance Criteria

GIVEN ...
WHEN ...
THEN ...