zenkilan
zenkilan
@tirodkar We have a large amount of test cases, about 2000 cases all together. The cases are based on XCTestCase. If we use EarlGrey 2.0, we can not use XCTestCase...
For example, we have a lot of cases using code from app directly by import the class and methods and properties to do the test. We have a lot of...
We navigate to a page in app directly by using url or schemes. And then, we get the top view controller. And then, we call the methods in the controller...
> @OuterCloud we are not doing a new EarlGrey 1.17 release as we've deprecated it for over a year now. Can you tell us more on why EarlGrey 2.0 is...
We need EarlGrey 1 support more. We need EarlGrey going on.
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.
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...
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...
God. help! Really Really Need Help! Hope EarlGrey 1.17 is comming soon!!!!!!!!!!!!! EarlGrey 2.0 is not what we want. Below is the problem I met and can not resolve. EarlGrey...