-
Notifications
You must be signed in to change notification settings - Fork 706
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.
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
Add integration tests #535
Conversation
2b57680
to
631134e
Compare
It seems that it fails on watchOS because there is no |
Wow, exporting |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great! Just a few minor tweaks and we're good to go!
} | ||
|
||
func readRawCrashReportData() throws -> Data { | ||
enum Error: Swift.Error { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just asking. Is it OK to use Error
which can be ambiguous in some cases? Also, maybe it would be more useful to define one Error
enum for the whole TestCase?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, these are only valid inside tests and not expected to be used as API. Made it a bit more clear but not sure if we need a single common enum
This is a foundation for integration tests