All Versions
26
Latest Version
Avg Release Cycle
100 days
Latest Release
468 days ago

Changelog History
Page 3

  • v1.0.0 Changes

    May 09, 2015

    ➕ Added

    • ✅ Possibility to specify zero as @delayMinutes (eg. if you want to force test order, but don't need to actually wait) or to use floating point number as delay.
    • ✅ SyntaxSugarTrait with shortcuts for element locating and waiting ($this->findBy...(), $this->findMultipleBy...() and $this->waitFor...()) usable in TestCases and Components.

    🔄 Changed

    • BC: Global configuration constants replaced with Config object accessed through ConfigProvider. Thus all the global constants (BROWSER_NAME, ENV, SERVER_URL, PUBLISH_RESULTS, FIXTURES_DIR, LOGS_DIR, DEBUG) are no longer available, use the Config object instead.
    • ✅ BC: lib/ and lib-tests/ directories renamed to src/ and src-tests/ respectively.
    • BC: Changed namespaces of eg. ConfigProvider and ProcessSet.

  • v0.12.0 Changes

    February 12, 2015

    🔄 Changed

    • ↪ Workaround for Firefox locking port collisions (consequence of Selenium issue #5172) - if FF cannot be started, try it again up to five times

  • v0.11.0 Changes

    February 06, 2015

    ➕ Added

    • 🆕 New debug() method that output to log only in debug mode. Could be used in both TestCases and Components.
    • ext-curl requirement into composer.json (as CURL is needed by HttpCommandExecutor).

    🔄 Changed

    • ⚡️ Test-cases order is optimized before running tests, so that test-cases with the longest delay of theirs dependencies are run as first.
    • 👌 Improved error messages when Selenium server is not accessible or when any of required directory does not exist.

    🛠 Fixed

    • Error is thrown if not-existing method is called on AbstractComponent descendants.
    • Properly handle PHPUnit_Framework_Warning when eg. data provider is invalid.

  • v0.10.1 Changes

    November 27, 2014

    🛠 Fixed

    • 🛠 Fix Xdebug being initialized even if the --xdebug option of run-tests command was not passed at all.

  • v0.10.0 Changes

    November 26, 2014

    ➕ Added

    • ✅ @noBrowser annotation on either test case class or test method could be used if you don't need to create new WebDriver (= browser window) instance.
    • ✅ Legacy component (imported from separate repository). It allows you to share data between test-cases.
    • ✅ Verbose output of executed WebDriver commands is provided in debug mode of run-tests command (debug mode could be enabled using -vvv).
    • ➕ Added --xdebug option to run-tests command to allow simple remote debugging of tests using Xdebug.

    🔄 Changed

    • ✅ Test cases running longer than 1 hour are killed and their result is set as "Fatal" in results.xml.

  • v0.9.0 Changes

    November 20, 2014

    ➕ Added

    • 🔄 CHANGELOG.md file.
    • ✅ Global DEBUG constant (is true if -vvv passed to run-tests), that could be used in tests to print some more verbose output.
    • ✅ The install command now checks for the latest version of Selenium server and interactively asks for confirmation.
    • ✅ Possibility to add custom test Publishers (enabled by --publish-results). Pass it as argument of TestStatusListener in phpunit.xml.
    • ✅ During the run-tests execution, current test results are generated into logs/results.xml. This is useful eg. on long-lasting Jenkins jobs or if you want to know more precise status of the current (or last) test run.
    • Shortcut to WebDriver in components - it's now possible to write $this->wd instead of $this->tc->wd.
    • ✅ Possibility to set --fixtures-dir in run-tests command. This is handy eg. when tests are run on remote terminal and fixtures are located on network directory.
    • ✅ Possibility to set --logs-dir in run-tests command. Useful when Steward core is installed as dependency and is run from vendor/bin/.
    • 💻 Possibility to easily overload any browser-specific capability, using custom (overloaded) WebdriverListener.
    • ✅ Specified group(s) could be excluded from the run-tests, using --exclude-group option.

    🔄 Changed

    • ✅ The last argument of run-tests command (browser name) is now always required (as well as the environment name).
    • ✅ The --publish-results parameter is now used without a value (as a switch to enable publishing test results).
    • ✅ Unified testcases and test status and results naming:
      • Testcases (= process) statuses: done, prepared, queued
      • Testcases (= process) results (for "done" status): passed, failed, fatal
      • Test statuses: started, done
      • Test results (for "done" status): passed, failed, broken, skipped, incomplete
    • The install command now outputs only full path to jar file in -no-interactive mode (except -vv or -vvv is passed) and nothing else.
    • ✅ Path to tests in run-tests command is now defined using --tests-dir.
    • ✅ Browser resolution is by default 1280x1024 and could easily be set eg. in AbstractTestCase using $browserWidth and $browserHeight properties.
    • ✅ The --group option could now be specified multiple times to select multiple values for run-tests.
    • ✅ Both run-tests and install commands now uses the project base directory as root path (for logs, test files, fixtures and as jar file installation) even if installed as dependency into vendor/ dir, so that it is not necessary to define the paths manually.
    • 👀 Commands are now triggering Events (see CommandEvents), which could be used to extend commands with custom features.