Szymon Kwiatek
Szymon Kwiatek
> Probably it's not a bug, Sliver is not rendered on screen itself, so it can't be hittestable. You should find some widget which is rendered on the screen -...
Hi @alexks02, Thanks for reporting, we will check this 👀 .
@alexks02 Why you want to use `fail()` in setup? You are right that this is an issue, but I would say with the low priority. Our backlog is long, and...
Hi, It is not like just fail() causes this error? And if you for example use .waitUntilVisible() there, error trace will be correct 🤔 Cheers, Szymon
Hi, You can get NativeAutomator `$.native2` and then use native patrol features there example: `final automator = NativeAutomator(config: nativeConfig);`
If you want to use `PatrolIntegrationTester $` just do it in test body. What is your usecase? setUp is mainly for setting stuff via API or do some native actions...
Should be fixed, can anyone confirm?
Please add more details @josephp-xpress patrol version / flutter version / cli version / emulator details logs from patrol test/develop with --verbose.
Duplicate of https://github.com/leancodepl/patrol/issues/1839
Already got the cause of issue, Developer page that we need to open is at the end of the list now, we need to add scroll there. Should be quick,...