Sven Jost

@marcphilipp I think this ticket should be reopened. I just ran into the issue with JUnit 7.5.2 while writing my own test engine and applying it to a big number...

Hi @marcphilipp Is there any chance to tackle this issue somehow? Selenium 4 is out now and unfortunately is using `ExecutorService` with `newFixedThreadPool` inside which results in JUnit 5 tests...

@DrKLO On the Google Play website you can currently download version 1.3.25 as binary. Where can I find the source code of this version? The public repo seems to only...

> I remember currently we have https://github.com/appium/appium/issues/16550 to fully work with Grid 4. What is the current plan to add support in appium for this? The needed change in selenium...

The zoom feature had to be removed because of various bugs. But we recently introduced an option to set the font size in the preferences to adjust the app to...

The zoom feature had to be removed because of this bugs. But we recently introduced an option to set the font size in the preferences to adjust the app to...

> What is your initial intention there? Do you want a new simulator to be created every time a new test is started? I assume it takes a lot of...

> Also the fact that setting `enforceFreshSimulatorCreation` to false does not change the actual behavior is expected. It only affects things being set to true (e.g. even if a test...

> the driver has a concept of life cycle and thus always assumes that if the simulator was created by it then it must also be deleted at the end...

> I assume this part of the code has not been touched for very long time. I'll create a PR to properly align the logic there Thank you for the...