peridot-php / webdriver-manager Goto Github PK

The README is a lie right now! Need to add methods to the manager:

• ->setInstallPath()
• ->addBinary()
• ->removeBinary()
• ->setBinaryResolver()

I tried using this package to manage my selenium dependencies, but I quickly found out that it does not work for mac with the current versions being around.

There is an open PR #16 addressing the issue, but CI is failing and there is no progress on the issue. Do you plan updating the versions and is this project still supported?

Right now ->isRunning() only checks if the parent process is running but doesn't guarantee that the standalone server si ready to process queries.

would be great to have something like:

    public function isReady()
    {
        if ($fd = @fsockopen(<host>, <port>)) {
             close($fd);
             return true:
        }
        return false;
    }

Which check the availability of the standalone server url http://localhost:4444/wd/hub

In light of the recent PR, I was doing a little code review and noticed the pinned versions of standalone and the drivers are lagging behind a bit.

Might be nice to update all those versions to the latest and greatest.

When starting the manager through:

$manager = new Manager();
$manager->startInBackground();

two processes are created:

17:38   0:00 sh -c java -jar /home/jaillet/peridot-php/webdriver-manager/binaries/selenium-server-standalone
17:38   0:01 java -jar /home/jaillet//peridot-php/webdriver-manager/binaries/selenium-server-standalone-2.46.

However when calling ->close() on the manager, only the parent process is terminated and the sandalone server is still running:

17:38   0:01 java -jar /home/jaillet//peridot-php/webdriver-manager/binaries/selenium-server-standalone-2.46.

I think it's probably related to https://bugs.php.net/bug.php?id=39992

This will solve a few issues - namely not having to poll for errors, and it will give some reference for errors.

use robo task runner to handle deployments

The current messaging for the update command handles the start of an update, and whether or not the target system is supported.

A post update status would be useful i.e:

Updating selenium
Nothing to update

OR

Updating binaries....
|========>---------| (60%)
2 binaries updated.

provide documentation using something like apigen