My test database, which was copied over from development, was setup with multiple stores and websites - this worked fine on all my tests, none of which had a multiple store configuration in their fixture file, until I tried to write a new test that included a new configuration because I was specifically testing it. Now when I run my tests I'm getting a SQL error on this specific test.

Zend_Db_Statement_Exception: SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'base' for key 'UNQ_MAG_CORE_WEBSITE_CODE'

This is what my initial DB looked like for websites

mysql> select * from mag_core_website;
+------------+-------+--------------+------------+------------------+------------+
| website_id | code  | name         | sort_order | default_group_id | is_default |
+------------+-------+--------------+------------+------------------+------------+
|          0 | admin | Admin        |          0 |                0 |          0 |
|          1 | base  | Main Website |          0 |                1 |          1 |
+------------+-------+--------------+------------+------------------+------------+

and this was the part of the fixture file that is throwing the error:

scope:
    website: # Initializes websites
        - website_id: 1
          code: "base"
          name: "Main Website"
          default_group_id: 1

It appears I can make this work if I remove website_id: 1 from my test database and have the tests create/remove the entry, but then all my other tests start to break. The only way I see to fix that then will be to add the same multi store markup to all my fixture config files....which I have a lot and ideally don't want to do.

Is there a better way to handle this? I could always use different ID's but if we ever need to adjust these in the DB for some reason and it creates a conflict again - then we'll have the same issue.

I'm concerned I'm going to have the same results when I add groups and/or stores to the fixture as well...although I haven't gotten that far yet.

Hello,

i guess there is actually a lot of work to do, because there are some open pull request and issues as well. Is anyone else going to maintain this project or is there a more active fork?

Regards

1. PHP Fatal error: Call to undefined method Mage_Core_Controller_Request_Http: :reset() in C:\xampp\htdocs\Cacommons\app\code\community\EcomDev\PHPUnit\Test\Ca se\Controller.php on line 1905

Fatal error: Call to undefined method Mage_Core_Controller_Request_Http::reset() in C:\xampp\htdocs\Cacommons\app\code\community\EcomDev\PHPUnit\Test\Case\Contr oller.php on line 1905

2. PHP Fatal error: Call to undefined method CA_Comparesort_Test_Controller_Index ::getMockBuilder() in C:\xampp\htdocs\Cacommons\app\code\community\EcomDev\PHPUn it\Test\Case.php on line 406

Fatal error: Call to undefined method CA_Comparesort_Test_Controller_Index::getM ockBuilder() in C:\xampp\htdocs\Cacommons\app\code\community\EcomDev\PHPUnit\Tes t\Case.php on line 406

In README.md there is a wrong reference to composer package:

• wrong one: "ecomdev/ecomdev_phpunit"
• correct one: "ivanchepurnyi/ecomdev_phpunit"

I'm trying to get a mock of my observer, but nothing happens:

$mock = $this->getModelMock('mymodule/observer');

phpunit just silently exits. Please help.

composer.json:

{
    "require-dev": {
        "ecomdev/ecomdev_phpunit": "*",
        "magento-hackathon/magento-composer-installer": "*"
    },
    "repositories": [
        {
            "type": "composer",
            "url": "http://packages.firegento.com"
        }
    ],
    "extra":{
        "magento-root-dir": ".",
        "magento-deploystrategy": "copy"
    }
}

In $root/shell/: php -f ecomdev-phpunit.php -- -a magento-config --db-user ... and I get: Cannot find local.xml.phpunit file in app/etc directory because it's missing.

I tried both modman and composer installation. Both failed.

Composer: I added to composer.json:

    "require": {
        "ivanchepurnyi/ecomdev_phpunit": "*"
    }

When I run "composer update" I get:

Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - The requested package ecomdev/ecomdev_phpunit could not be found in any ve
rsion, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your min
imum-stability setting
   see <https://groups.google.com/d/topic/composer-dev/_g3ASeIFlrc/discussion> f
or more details.

Read <http://getcomposer.org/doc/articles/troubleshooting.md> for further common
 problems.

Modman I try to run

modman clone git://github.com/EcomDev/EcomDev_PHPUnit.git

I get

/bin/modman: line 759: conditional binary operator expected
/bin/modman: line 759: syntax error near `=~'
/bin/modman: line 759: `if ! [[ "$action" =~ $REGEX_ACTION ]]; th
en'

If vfsStream is installed via composer dependency, the check fails, because composer installs it into vendor directory. Better try to init the class if this fails, throw the exception.

When cleanEntity is called it only removes the main table content. Entries in the related tables for the different types is not necessarily deleted (ie through delete cascade). The patch manually introduces cleanTable calls for category and product.

The patch additionally calls cleanEntity before the fixture is loaded to ensure that no existing data interferes with the data from the fixture.

I see from the README you've bumped phpunit up to 3.7.x. I have updated composer.json to reflect this.

Also changed "magento-hackathon/magento-composer-installer": dependancy to "*"

I think this is the preferred version to pin for magento-composer-installer //cc @vinai

I have created a test suite that I ran successfully for months. I changed my laptop, and in my new environment I'm not able to execute the tests, as it fails with the error message below:

'PDOException' with message 'SQLSTATE[3D000]: Invalid catalog name: 1046 No database selected' in www/shop/lib/Zend/Db/Statement/Pdo.php:228

The database settings appear to be correct because when I first ran the test suite, it has successfully created the copy of the Magento database into the test database.

Error message and stack trace:

PHPUnit 3.6.12 by Sebastian Bergmann.

F
Fatal error: Uncaught exception 'PDOException' with message 'SQLSTATE[3D000]: Invalid catalog name: 1046 No database selected' in www/shop/lib/Zend/Db/Statement/Pdo.php:228
Stack trace:
#0 www/shop/lib/Zend/Db/Statement/Pdo.php(228): PDOStatement->execute(Array)
#1 www/shop/lib/Zend/Db/Statement.php(300): Zend_Db_Statement_Pdo->_execute(Array)
#2 www/shop/lib/Zend/Db/Adapter/Abstract.php(479): Zend_Db_Statement->execute(Array)
#3 www/shop/lib/Zend/Db/Adapter/Pdo/Abstract.php(238): Zend_Db_Adapter_Abstract->query('SELECT `main_ta...', Array)
#4 www/shop/lib/Varien/Db/Adapter/Pdo/Mysql.php(337): Zend_Db_Adapter_Pdo_Abstract->query('SELECT `main_ta...', Array)
#5 www/shop/li in www/shop/lib/Zend/Db/Statement/Pdo.php on line 234

(note: I shrunk down full paths in the error messages)

It's definitely some local problem, however in it's current form it seems to be nearly impossible to fix, so I'd like to ask for some help on how to discover the root cause.

So, till the 2nd step everything was proper. And when running phpunit, it throws an error :

myProj/app/code/local/Dbaux/Customer/sql/customer_setup/upgrade-1.6.2.0.4-1.6.2.0.5.php" - SQLSTATE[42S02]: Base table or view not found: 1146 Table 'magento_test.customer_entity

And when I looked into it, its because the script present in: app/code/core/Mage/Customer/sql/customer_setup which has files with lower version number are not run before running this script.

So, did anyone else facing this issue, or knows how to resolve this issue.

For the step 2: you should add: "The database $DB_NAME should be already created"

For the step 3 you should mention where phpunit must run from:

3. Go to your magento root directory and run unit tests for the first time to install test database by running phpunit. It should take about 3 minutes. $ phpunit

Spent some time to figure it out.

We are currently using Composer to deploy Magento with its modules and also some other non-Magento related tools used for our CI cycle.

We are currently using the dev branch of EcomDev_PHPUnit

We recently run into an issue where PHPUnit crashed silently and it took us several hours before we found out that the source of the problem was that Spyc was being autoloaded via composer at the beginning of the PHPUnit process and later again when loading tests that use either a fixture or dataProvider (we are not using expectations, but I assume its the same case).

The problem was that the first line of EcomDev_PHPUnit_Model_Yaml_Loader does a require_once 'Spyc/spyc.php' without considering the possibility of it already beind loaded gloabally.

For our case, simply wrapping the require_once in if (!class_exists('Spyc', false)) fixed the issue.

Looking closely at the 2 versions of Spyc, we noticed the one we have via Composer is version 0.6.2 while the one bundled with EcomDev_PHPUnit is version 0.4.5 so I am not 100% this fix will work in every scenario.

I can provide a PR with this fix unless the Spyc version needs to be fixed to 0.4.5 for some reason.

Comparing both versions, I only noticed differences in comments, internal functions naming, a bunch of dump stuff (not used by this module) and some additional controls when loading files. Nothing struck me as a possible compatibility breaker but I am not that familiar with Spyc.

GitHub changed the way Markdown headings are parsed, so this change fixes it.

See bryant1410/readmesfix for more information.

Tackles bryant1410/readmesfix#1

While creating for another project a unit test for controller there appeared a problem: They were not starting, found problem at lib/EcomDev/PHPUnit/Mock/Proxy.php wich implements PHPUnit_Framework_MockObject_MockObject and is required to implement also function __phpunit_hasMatchers. I have raised a PR which fixes this issue.

Also my IDE shows following error . Fortunately for me this has not stopped testing controller