When to support testing on iOS 13

Nowadays we found that EarlGrey is not supported for testing on iOS 13, is there any future further plans?

EarlGrey 2.0 (in the earlgrey2 branch has iOS 13 support). Please look at migrating your tests to use it.

We have a lot of test cases using EarlGrey1 It means we should delete them all and rewrite them in EarlGrey2? That seems impossible

Hope EarlGrey1 can support iOS 13 Our imperatives for EarlGrey1 supporting iOS 13 are great. Really need your help, god.

Hey @OuterCloud how many tests do you have? You can utilize the eDO macros in EarlGrey 2.0 to do white-box calls in a UI test as well. If you want us to provide more details, you should join our slack channel.

We have about one thousand cases writen by EarlGrey 1.0 Now we want to test on iOS 13 and we found the EarlGrey 1.0 seems to be unavailable on iOS 13 Our test cases use EarlGrey 1.0 and also the native business code to do a logical test based on UI. I need your help, god. How can I join the slack channel?

We need to call the method in app and use the OCMock to do some mock/stub/expect/verifiy EarlGrey 2.0 not support that Our cases written in EarlGrey 1.0 will be unavailable if move to EarlGrey 2.0 We very very very need EarlGrey 1.0 support iOS 13 We really need EarlGrey 1.0

Send me your email and I'll add you there. You can use OCMock by stubbing it with eDO.

hello Tirodkar please add me to the EarlGrey Slack channel ,I am getting started using it

hello @tirodkar is there any reference on how to use OCMock by stubbing with eDO ? i tried using something like this and it didn't work id flagControl = OCMClassMock([GREY_REMOTE_CLASS_IN_APP(FlagControlHelper) class]); OCMStub([flagControl isFlagEnabled]).andReturn(YES);