I am guessing that part of an adapter fulfilling the public API is passing all of the adapter non-specific specs regardless of which adapter is used? I was making some Autoit specs and when I switched the default adapter to :autoit any spec that located elements by :id failed. While :id is a valid locator that will work with the :autoit adapter, it's meaning is not the same as for the :win_ffi adapter and as such it cannot currently be used in the same way across adapters.
In particular, the TextField specs fail because they have "textField" listed as the :id which lines up with the AutomationID used by :win_ffi. The :id used by :autoit, however, is a number which changes every time the control is created and as such is problematic to practically use as an identifier.
I am guessing that part of an adapter fulfilling the public API is passing all of the adapter non-specific specs regardless of which adapter is used? I was making some Autoit specs and when I switched the default adapter to :autoit any spec that located elements by :id failed. While :id is a valid locator that will work with the :autoit adapter, it's meaning is not the same as for the :win_ffi adapter and as such it cannot currently be used in the same way across adapters.
In particular, the TextField specs fail because they have "textField" listed as the :id which lines up with the AutomationID used by :win_ffi. The :id used by :autoit, however, is a number which changes every time the control is created and as such is problematic to practically use as an identifier.