You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
first of all, let me say that FlaUI is a really great library for Test Automation! So thanks for your hard work.
However, comparing with Appium/WinAppDriver we cannot do remote automation. I know, this was discussed before and while in my oppinion it makes no sense adding a narrowing API like selenium/appium on top, I was wondering, what would be necessary to make FlaUI API usable accross Remote Procedure Call (RPC) libs like gRPC. So we could retain the directness of the UIA-level access of FlaUI API. I am not very experienced with RPC but my first experiments showed that object serialization/deserialization seems to be the key challenge. So for instance, would it be possible to add IsSerializable property to all relevant FlaUI API classes? Could there be different problems like with using the Retry method? Or maybe the limiter is the MS UIA libraries used by FlaUI?
Let me give you an example why this could be a useful extension. Imagine your software under test runs on a virtual machine and needs to be reset to a snapshot in order to accelerate test fixture setup. In this case, it would be necessary to run the test runner on a different machine as you would otherwise reset the test runner itself.
I am excited to see if anyone has oppinions on that!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hello everyone,
first of all, let me say that FlaUI is a really great library for Test Automation! So thanks for your hard work.
However, comparing with Appium/WinAppDriver we cannot do remote automation. I know, this was discussed before and while in my oppinion it makes no sense adding a narrowing API like selenium/appium on top, I was wondering, what would be necessary to make FlaUI API usable accross Remote Procedure Call (RPC) libs like gRPC. So we could retain the directness of the UIA-level access of FlaUI API. I am not very experienced with RPC but my first experiments showed that object serialization/deserialization seems to be the key challenge. So for instance, would it be possible to add IsSerializable property to all relevant FlaUI API classes? Could there be different problems like with using the Retry method? Or maybe the limiter is the MS UIA libraries used by FlaUI?
Let me give you an example why this could be a useful extension. Imagine your software under test runs on a virtual machine and needs to be reset to a snapshot in order to accelerate test fixture setup. In this case, it would be necessary to run the test runner on a different machine as you would otherwise reset the test runner itself.
I am excited to see if anyone has oppinions on that!
Beta Was this translation helpful? Give feedback.
All reactions