OndraM
Repos
99
Followers
64
Following
58

Detect continuous integration environment and get information of current build

182
9

PHP libraries that makes Selenium WebDriver + PHPUnit functional testing easy and robust

219
40

PHP client for Selenium/WebDriver protocol. Previously facebook/php-webdriver

4680
760

PHP API Client for Matej recommendation engine

11
6

LMC Cookie Consent Manager

Zend Framework OAuth 2.0 example app

7
2

Events

Api documentations update (2022-09-25 12:07:06+00:00)

#apidocs

Created at 5 days ago

Run integration tests on Selenium server 4.3.0

It fixes some speed regressions of 4.1.0

Created at 1 week ago
delete branch
OndraM delete branch feature/php-8.2-build
Created at 1 week ago

Add PHP 8.2 build

Add allow-plugins to composer.json

Created at 1 week ago
pull request closed
Add PHP 8.2 build
Created at 1 week ago

Add allow-plugins to composer.json

Created at 1 week ago

Normalize composer.json to new schema

Add PHP 8.2 build

Add allow-plugins to composer.json

Created at 1 week ago

Add allow-plugins to composer.json

Created at 1 week ago
pull request opened
Add PHP 8.2 build
Created at 1 week ago
create branch
OndraM create branch feature/php-8.2-build
Created at 1 week ago
delete branch
OndraM delete branch feature/php73
Created at 1 week ago
delete branch
OndraM delete branch feature/remove-contiuousphp
Created at 1 week ago
delete branch
OndraM delete branch feature/composer-normalize
Created at 1 week ago
delete branch
OndraM delete branch feature/appveyor-curl
Created at 1 week ago
delete branch
OndraM delete branch feature/php-8.2-build
Created at 1 week ago

Add PHP 8.2 build

Created at 1 week ago
pull request closed
Add PHP 8.2 build
Created at 1 week ago
pull request opened
Add PHP 8.2 build
Created at 1 week ago
create branch
OndraM create branch feature/php-8.2-build
Created at 1 week ago

Update github actions

Created at 1 week ago
ElementToBeClickable doesn't actually guarantee the element is clickable

What are you trying to achieve? (Expected behavior)

Sometimes, async elements overlaying another element intercept clicks, even though ElementToBeClickable suggests that the underlying element is clickable (it's not)

What do you get instead? (Actual behavior)

The method to return true only when the element really is clickable. When other items overlay it (like fixed position elements) the element is not clickable, even though it's in the DOM, visible, and ready.

How could the issue be reproduced? (Steps to reproduce)

Just overlay a button with a fixed element.

// You can insert your PHP code here (or remove this block if it is not relevant for the issue).

Details

  • Php-webdriver version: 1.8@dev
  • PHP version: 7.3
  • Selenium server version: 3.141.59-yttrium
  • Operating system: Mac OS X Mojave
  • Browser used + version: Chrome 76
Created at 1 week ago
ElementToBeClickable doesn't actually guarantee the element is clickable

What are you trying to achieve? (Expected behavior)

Sometimes, async elements overlaying another element intercept clicks, even though ElementToBeClickable suggests that the underlying element is clickable (it's not)

What do you get instead? (Actual behavior)

The method to return true only when the element really is clickable. When other items overlay it (like fixed position elements) the element is not clickable, even though it's in the DOM, visible, and ready.

How could the issue be reproduced? (Steps to reproduce)

Just overlay a button with a fixed element.

// You can insert your PHP code here (or remove this block if it is not relevant for the issue).

Details

  • Php-webdriver version: 1.8@dev
  • PHP version: 7.3
  • Selenium server version: 3.141.59-yttrium
  • Operating system: Mac OS X Mojave
  • Browser used + version: Chrome 76
Created at 1 week ago
ElementToBeClickable doesn't actually guarantee the element is clickable

From what I found, php-webdriver behavior is the same as in others official Selenium language bindings. So closing this, as there doesn't seem to be a simple way to workaround this. Unless anyone is interested in digging into this deeper, we are keeping this as is.

Created at 1 week ago

Empty commit to trigger build

Created at 1 week ago
Aggregate results do not get reported correctly to GitHub

Hi, shouldn't repo_token be the value which is displayed on coveralls repository homepage (when signed in), instead of GITHUB_TOKEN?

Using the project token, the rerun payload gets accepted. {"rerun":true,"url":"https://coveralls.io/builds/...","jobs":14}.

(However the coverage is still not calculated correctly, the value in the header is still inconsistent and much lower then coverage displayed below the "Source files" header).

Created at 1 week ago

Fix coveralls workaround

Trigger build

Created at 1 week ago

Fix coveralls workaround

Created at 1 week ago

Fix coveralls workaround

Trigger build

Created at 1 week ago