-
Notifications
You must be signed in to change notification settings - Fork 712
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
* Add accessibility labels * Support install path override * Add integration test * Add integration test CI job * Wait for crash * Do not CI tvOS * Assert Apple-formatted report * Remove visionOS part * Extract integration tests to a separate workflow * Add testplan and fix scheme * Lower repetitions number * Wait for install button * Add some swifty sugar * Use directory sink for tests * Add other crash types * Fix watchOS * Split helper and crash triggers * Add crash search and use it in tests * Just use scroll instead of search * Use a different second test * Fix format * Run tests in parallel * Remove typealias * Limit number of scrolls * Fix throws * Swipe slowly * Even slower? * Add generic crashed thread validation * Add mach exception test * Fix C++ test by enabling cxa_throw swap * Fix toggle logic * Use env + script instead of UI elements * Test Mach only on iOS * Add tvOS test target * Address comments * Add platform-specific action delay * Add macOS * Remove test UI ids * Use manual run for most changes
This is a foundation for integration tests