Skip to main content

Testing web apps in PHP using Selenium WebDriver

The Applitools Eyes Selenium for PHP SDK allows you to easily add visual checkpoints to your Php Selenium tests. It takes care of getting screenshots of your application from the underlying WebDriver, sending them to the Eyes server for validation and failing the test in case differences are found.

Install the SDK

composer require applitools/eyes.sdk.php

If you don't have any installed packages create composer.json file:

"require": {
"applitools/eyes.sdk.php": "^1.3.3"

And then run:

composer install

Run your first test

Applitools Eyes reports differences by comparing screenshots of your application with baseline images that define the expected appearance of the application at each step of the test. By default, the Eyes SDK detects the environment in which the application is running (namely, the operating system, the type of browser and its viewport size) and compares the screenshots against baseline images that are specific to that environment. The first time you run a test in a given environment, its screenshots will be automatically saved as its baseline. Starting from the second run onward, you always have a baseline to compare against.

The test below is a simple Php program that visually validates the Hello World web-page at It consists of two visual checkpoints, each validating the entire application window. The first time you run this test a new baseline will be created, and subsequent test runs will be compared to this baseline. If any screenshot mismatch its baseline image in a perceptible way, $eyes.close() will throw a DiffsFoundException which includes a URL that points to a detailed report where you can see the detected differences and take appropriate actions such as reporting bugs, updating the baseline and more.

Before running the test, make sure to set the API key that identifies your account in the environment variable APPLITOOLS_API_KEY or directly assign it to the $eyes->setApiKey() method. You can find your API key under the user menu located at the right hand side of the test manager toolbar. If you don't yet have an account create it now to obtain your key.



use Applitools\RectangleSize;
use Applitools\Selenium\Eyes;
use Facebook\WebDriver\Remote\RemoteWebDriver;
use Facebook\WebDriver\Remote\WebDriverCapabilityType;
use Facebook\WebDriver\WebDriverBy;

class HelloWorld

protected $url = '';
protected $webDriver;

public function demo()

// Open a chrome browser.
$capabilities = array(WebDriverCapabilityType::BROWSER_NAME => 'chrome');
$this->webDriver = RemoteWebDriver::create('http://localhost:4444/wd/hub', $capabilities);


// Initialize the eyes SDK and set your private API key.
$eyes = new Eyes();

try {

$appName = 'Hello World!';
$testName = 'My first PHP test!';

// Start the test and set the browser's viewport size to 800x600
$eyes->open($this->webDriver, $appName, $testName,
new RectangleSize(800, 600));

// Visual checkpoint #1.

// Click the "Click me!" button

// Visual checkpoint #2.

// End the test.

} finally {

// Close the browser.

// If the test was aborted before eyes->close was called,
// ends the test as aborted.


$test = new HelloWorld();

Analyze your test results

Congratulations! You've successfully run your first visual UI test with Applitools Eyes! A detailed report is ready for your inspection at the Applitools Eyes test manager. Watch this 5 minute video to get acquainted with the test manager and to learn the basics of baseline maintenance.

Login to Applitools and analyze the results.

Having Trouble?

Don't suffer in silence! Let us help you. Please reach out to us to get your project working.

Taking the next steps with Applitools

Congratulations on completing this quickstart! There's still so much to learn about visual testing with Applitools, but you're off to a great start.

Resources for next steps:

  1. 🤖 Learning how visual testing works
  2. ↔️ Setting match levels for visual checkpoints
  3. 💥 Troubleshooting common issues
  4. 🐞 Reporting bugs
  5. 🗺 Detailed overview of visual testing with Applitools

You can also: