Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Determine if using xcpretty, Fastlane or Buck requires additional logic for determining if a test suite has failed #48

Open
SeanROlszewski opened this issue Jan 19, 2019 · 0 comments
Open

Determine if using xcpretty, Fastlane or Buck requires additional logic for determining if a test suite has failed #48

SeanROlszewski opened this issue Jan 19, 2019 · 0 comments
Labels
chore Work to reduce technical debt and improve the health of Muter's codebase, release process, and DX

Comments

@SeanROlszewski
Copy link
Contributor

No description provided.

@SeanROlszewski SeanROlszewski added the chore Work to reduce technical debt and improve the health of Muter's codebase, release process, and DX label Jan 19, 2019
@SeanROlszewski SeanROlszewski changed the title Determine if using xcpretty or Fastlane requires additional logic for determining if a test suite has failed Determine if using xcpretty or Fastlane requires additional logic for determining if a test suite has failed Jan 19, 2019
@rakaramos rakaramos changed the title Determine if using xcpretty or Fastlane requires additional logic for determining if a test suite has failed Determine if using xcpretty, Fastlane or Buck requires additional logic for determining if a test suite has failed Aug 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
chore Work to reduce technical debt and improve the health of Muter's codebase, release process, and DX
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@SeanROlszewski