Chirag Jayswal

Results 95 comments of Chirag Jayswal

Use `@Formatter` with `QAFTestStepArgumentFormatter` instead of `@Transform` with `Transformer`. Refer sample [implementation](https://github.com/qmetry/qaf/blob/5f380746a108b016b41ff9612f38c948b38c6197/test/src/com/qmetry/qaf/automation/impl/step/formatter/TestArgFormatter.java#L36) and [usage of @Formatter](https://github.com/qmetry/qaf/blob/5f380746a108b016b41ff9612f38c948b38c6197/test/src/com/qmetry/qaf/automation/step/SampleStepProvider.java#L85).

This solution will have issues as step didn't proxied for data driven test. It may resolve current issue but will introduce new issues.

Well, refer [resolution](https://github.com/qmetry/qaf/commit/2399ce27367c050be99792299d25ee0c50404ccf)

Use [WinHttpProxySelector](https://github.com/gbastkowski/ntlm-proxy/blob/master/src/main/java/de/compeople/commons/net/proxy/win32/WinHttpProxySelector.java) or similar implementation instead. For example in before suite place below code: import java.net.ProxySelector; .... ProxySelector.setDefault(new WinHttpProxySelector());

`WinHttpProxySelector` is one of the example, if it is not working or not suitable you can have custom implementation of `ProxySelector`. So in either case preferred to use `ProxySelector` to...

How and Where you are registering `ProxySelector`? Proxy selector works fine, set it either before driver init or beforeSuite (preferred) I had used that way and it works fine for...

I would not recommend it because it will address proxy only for driver connection. For example, in case of perfecto if someone wants to use rest api, it will not...

Can you share sample code you are using? it looks that you are not using wait service from qaf (methods available with QAFWebElement and QAFWebDriver)

Well, you can do that witout using iOSFindBy. Refer [documentation](https://qmetry.github.io/qaf/latest/locating_elements.html). You can use alternate locater instead of iOSFindAll. For instance, it may look like ``` @FindBy(locator = "['accessibility id=item.storeBanner','accessibility id=item.someLabel']")...

can you check with latest qaf (2.1.14 RC1 or RC2)?