Andrei Rogal

@aleksandr-kotlyar now the tests pass in 36s for Selene 2.0.0a21 and 28s for Selenium. - `poetry run pytest --tb=short .\tests\test_selene.py` [test_selene.log](https://github.com/andreirogal/selene-experiments/blob/master/logs/test_selene_28_03_2021.log) session ~36s - `poetry run pytest --tb=short .\tests\test_native_selenium.py` [test_native_selenium.log](https://github.com/andreirogal/selene-experiments/blob/master/logs/test_native_selenium_28_03_2021.log)...

@aleksandr-kotlyar here are the results after the merge: - `poetry run pytest tests/test_selene.py --tb=no` [test_selene](https://github.com/andreirogal/selene-experiments/blob/master/logs/test_selene_28_03_2021_2.log) ~36s - `poetry run pytest tests/test_native_selenium.py --tb=no` [test_native_selenium](https://github.com/andreirogal/selene-experiments/blob/master/logs/test_native_selenium_28_03_2021_2.log) ~26s

> retry in six times with 2 second pause in your logs: @aleksandr-kotlyar Yes, I noticed that too. But I can't understand what this is related to.

> * On GitHub Actions **Ubuntu** test execution time is: 21s selene and 28s selenium - [details](https://github.com/aleksandr-kotlyar/selene-experiments/runs/2212876480?check_suite_focus=true) but difference from run to run: sometimes 15s selene and 27.75s selenium [details](https://github.com/aleksandr-kotlyar/selene-experiments/runs/2212876506?check_suite_focus=true)...

@aleksandr-kotlyar I run these tests on i7-9750H CPU 2.60GHz, 16 GB Memory, SSD disk and Windows 10 Home v.20H2 OS Build 19042.867

@aleksandr-kotlyar Then I reopen this issue. It's very interesting how it will be resolved)