Tests Apps in both Objective C and Swift #9
Conversation
|
|
||
| class AppDelegate: NSObject, UIApplicationDelegate, UNUserNotificationCenterDelegate { | ||
|
|
||
| var pushDetails = PushNotificationDetailClass() |
There was a problem hiding this comment.
Shouldn't we use @StateObject to init PushNotificationDetailClass (which is an ObservableObject)
@StateObject var pushDetails = PushNotificationDetailClass()
There was a problem hiding this comment.
No StateObject isn't an ideal choice for use for classes that are not SwiftUI.
We get a warning
"Accessing StateObject's object without being installed on a View. This will create a new instance each time."
| } | ||
| } | ||
|
|
||
| struct CampaignClassicMockAPICard: View { |
There was a problem hiding this comment.
nit: Im not sure why we need this when we have enabled the app for Push. We already have integration tests that help inspect and test the outgoing requests for the APIs (happy path).
There was a problem hiding this comment.
Most of the time for quick API testing we use the app with simulator. These mocks will certainly help on those times
Test App Swift
Test App Objective C