PHPackages                             magium/magento1-clairvoyant-ui - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Testing & Quality](/categories/testing)
4. /
5. magium/magento1-clairvoyant-ui

ActiveMagento-module[Testing & Quality](/categories/testing)

magium/magento1-clairvoyant-ui
==============================

A Magento 1 based UI to build Magium Selenium tests in the Admin UI

0.9.8(8y ago)21413Apache-2.0PHP

Since Jan 3Pushed 8y ago2 watchersCompare

[ Source](https://github.com/magium/magento1-magium-ui)[ Packagist](https://packagist.org/packages/magium/magento1-clairvoyant-ui)[ RSS](/packages/magium-magento1-clairvoyant-ui/feed)WikiDiscussions develop Synced 2mo ago

READMEChangelog (7)Dependencies (2)Versions (12)Used By (0)

The purpose of Magium is to make building and running browser tests as an everyday part of your development experience. Magium takes a big step towards that direction by reducing the investment required to build Selenium tests by establishing a structure and framework for indvidual software products, Magento being the first one.

Magium, however, is more than just a tool to make browser testing easier for developers. Our goal is to make web site testing not just easier, but more holistic. In other words, while Magium's first step was in making developer's lives easier, there is no reason to stop there. Magium Clairvoyant is a series of products under development to inject Magium into the production environment.

That is done via a new Magento module that we have built that provides the ability to build and execute simple Magium tests directly from the Magento UI based off of data that Clairvoyant can extract from the normal execution of the website. To see how this works you can check out this short YouTube video.

[![Short version](https://camo.githubusercontent.com/3df65f88536b5dc4a72b824ecb9ddd74ebff7bbed1725ff5a122fb7f1efedb53/68747470733a2f2f696d672e796f75747562652e636f6d2f76692f7052626e61754c5f4b48452f302e6a7067)](https://www.youtube.com/watch?v=pRbnauL_KHE)

You can also view a longer version that includes instructional elements here:

[![Long version](https://camo.githubusercontent.com/acb1aa127873701dbd780d0217ebb86c1277630c9e658cbf5824de5e63ad9a2d/68747470733a2f2f696d672e796f75747562652e636f6d2f76692f66374e49622d7032796e552f302e6a7067)](https://www.youtube.com/watch?v=f7NIb-p2ynU)

Getting started is super easy.

To install Clairvoyant you need to create a composer.json file for your Magento project that looks something like this:

```
{
    "name": "root/www",
    "require": {
    },

    "extra" : {
        "magento-deploystrategy": "copy",
        "magento-root-dir": "/var/www/magento"
    }
}

```

Then execute

```
composer require magium/magento1-clairvoyant-ui

```

That's it. From there you can start building your tests.

The first thing you will need to do is make sure that you have Selenium Server running. That's easy. And Magium prefers Chromedriver, though you can configurably set it differently.

The log in to your Magento instance and navigate to `System / Configuration :: Magium` and change the settings to suit your environment. In particular, the Selenium Server URL.

[![](https://github.com/magium/magento1-magium-ui/raw/images/images/config.png?raw=true)](https://github.com/magium/magento1-magium-ui/blob/images/images/config.png?raw=true)

From there you can configure Clairvoyant for your individual site, though we recommend initial testing using the sample data set. Navigate to `System / Magium / Test Configuration` and change any Xpath, URL or identity data that you need to make Clairvoyant conform to your site. **Additionally** you need to configure how you want the test to be run: immediately, or via a queue. Immediate mode will trigger as soon as an associated event is triggered. Via the queue will inject the test into a queue and get executed by cron.

[![](https://github.com/magium/magento1-magium-ui/raw/images/images/customer-identity.png?raw=true)](https://github.com/magium/magento1-magium-ui/blob/images/images/customer-identity.png?raw=true)

Once you have configured Clairvoyant it's time to start building tests. Tests are designed to have data from Magento injected into them and get interpolated into the test. We suggest watching the YouTube videos about to see that in action.

[![](https://github.com/magium/magento1-magium-ui/raw/images/images/edit-test.png?raw=true)](https://github.com/magium/magento1-magium-ui/blob/images/images/edit-test.png?raw=true)

One of the key components of building Clairvoyant tests is the use of assertions. The assertions are extracted from Magium and presented for your consumption in the instruction form, along with navigators and actions.

[![](https://github.com/magium/magento1-magium-ui/raw/images/images/assertions.png?raw=true)](https://github.com/magium/magento1-magium-ui/blob/images/images/assertions.png?raw=true)

But while building a test is good, you don't just want to build it and then run it in production; you want to test the test first. To do that you click on the Test Execution button on the top right side of the form and you can simulate an event by injecting various Magento objects into the Magium Dependency Injection Container and executing the test with interpolation. Again, see the video for more information about that.

When the test is completed you will see a log of the test.

[![](https://github.com/magium/magento1-magium-ui/raw/images/images/test-execution.png?raw=true)](https://github.com/magium/magento1-magium-ui/blob/images/images/test-execution.png?raw=true)

Once you are satisfied with your test navigate to `System / Magium / Test Execution`. This is where you will associate the test with certain events.

[![](https://github.com/magium/magento1-magium-ui/raw/images/images/bind-tests.png?raw=true)](https://github.com/magium/magento1-magium-ui/blob/images/images/bind-tests.png?raw=true)

Now that the test has been bound to the event, find an appropriate product and save it. When the test has executed you can navigate to `System / Magium / Test Queue` and see the results of the test.

[![](https://github.com/magium/magento1-magium-ui/raw/images/images/test-log.png?raw=true)](https://github.com/magium/magento1-magium-ui/blob/images/images/test-log.png?raw=true)

So check it out and let us know how we can make your browser testing an enjoyable experience. Again, check out the YouTube videos if you have more questions.

[![Short version](https://camo.githubusercontent.com/3df65f88536b5dc4a72b824ecb9ddd74ebff7bbed1725ff5a122fb7f1efedb53/68747470733a2f2f696d672e796f75747562652e636f6d2f76692f7052626e61754c5f4b48452f302e6a7067)](https://www.youtube.com/watch?v=pRbnauL_KHE)

You can also view a longer version that includes instructional elements here:

[![Long version](https://camo.githubusercontent.com/acb1aa127873701dbd780d0217ebb86c1277630c9e658cbf5824de5e63ad9a2d/68747470733a2f2f696d672e796f75747562652e636f6d2f76692f66374e49622d7032796e552f302e6a7067)](https://www.youtube.com/watch?v=f7NIb-p2ynU)

###  Health Score

29

—

LowBetter than 60% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity15

Limited adoption so far

Community10

Small or concentrated contributor base

Maturity60

Established project with proven stability

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~52 days

Recently: every ~104 days

Total

9

Last Release

2997d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/cd1cf3c696e501a5d5b6813b0aff73169fef00eec3ab5aa437e1302027ded655?d=identicon)[kschroeder](/maintainers/kschroeder)

---

Top Contributors

[![kschroeder](https://avatars.githubusercontent.com/u/237332?v=4)](https://github.com/kschroeder "kschroeder (47 commits)")

### Embed Badge

![Health badge](/badges/magium-magento1-clairvoyant-ui/health.svg)

```
[![Health](https://phpackages.com/badges/magium-magento1-clairvoyant-ui/health.svg)](https://phpackages.com/packages/magium-magento1-clairvoyant-ui)
```

###  Alternatives

[phpspec/prophecy

Highly opinionated mocking framework for PHP 5.3+

8.5k551.7M682](/packages/phpspec-prophecy)[vimeo/psalm

A static analysis tool for finding errors in PHP applications

5.8k77.5M6.7k](/packages/vimeo-psalm)[brianium/paratest

Parallel testing for PHP

2.5k118.8M754](/packages/brianium-paratest)[beberlei/assert

Thin assertion library for input validation in business models.

2.4k96.9M570](/packages/beberlei-assert)[orchestra/testbench

Laravel Testing Helper for Packages Development

2.2k39.1M32.1k](/packages/orchestra-testbench)[phpspec/phpspec

Specification-oriented BDD framework for PHP 7.1+

1.9k36.7M3.1k](/packages/phpspec-phpspec)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)