Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>I have never used the <code>PHPUnit_Extensions_Database_TestCase</code>, mostly because for these two reasons:</p> <ul> <li>It doesn't scale well. If you set up and tear down the database for every single test and you have a application which relies heavily on the database, you end up creating and dropping the same schema over and over again.</li> <li>I like to have my fixtures not only within my tests but also within my development database and some fixtures are even needed for production (initial admin user or product categories or whatever). Having them inside an xml which can only be used for phpunit doesn't seem right to me.</li> </ul> <p><strong>My way in theory...</strong></p> <p>I use the <a href="https://github.com/doctrine/DoctrineFixturesBundle" rel="noreferrer">doctrine/doctrine-fixtures-bundle</a> for fixtures (no matter what purpose) and set up the whole database with all fixtures. I then execute all tests against this database and make sure to recreate the database if a test changed it.</p> <p>The advantages are that I don't need to set up a database again if a test only reads but don't change anything. For changes I have to do drop it and create it again or make sure to revert the changes.</p> <p>I use sqlite for testing because I can set up the database, then copy the sqlite file and replace it with a clean one to bring back the original database. That way I don't have to drop the database, create it and load all fixtures again for a clean database. </p> <p><strong>...and in code</strong></p> <p>I wrote an <a href="http://sgoettschkes.blogspot.com/2012/06/symfony2-test-database-best-pratice.html" rel="noreferrer">article about how I do database tests with symfony2 and phpunit</a>.</p> <p>Although it uses sqlite I think one can easily make the changes to use MySQL or Postgres or whatever.</p> <p><strong>Thinking further</strong></p> <p>Here are some other ideas which might work:</p> <ul> <li>I once read about a test setup where before you use the database you start a transaction (within the setUp method) and then use the tearDown to rollback. That way you don't need to set up the database again and just need to initialize it once.</li> <li>My setup described above has the drawback that the database is set up every time phpunit is executed, even if you only run some unit tests with no database interaction. I am experimenting with a setup where I use a global variable which indicates if the database was set up and then within the tests call a method whcih checks this variable and initializes the database if it didn't happened yet. That way only when a tests needs the database the setup would happen.</li> <li>One problem with sqlite is that it doesn't work the same as MySQL in some rare cases. I had an issue once where something behaved different in MySQL and sqlite causing a test to fail when in with MySQL everything worked. I cannot remember what it was exactly.</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. POHow to set up database-heavy unit tests in Symfony2 using PHPUnit?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USk0pernikus
    1. USSgoettschkes
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThere is a bundle that provides further integration between PHPUnit and Doctrine's fixtures called [Liip/FunctionalTestBundle](https://github.com/liip/LiipFunctionalTestBundle). We use this in combination with a sqlite database defined in our config_test.yml configuration and it helps to simplify things a lot! One really useful feature of the bundle is that it can cache your sqlite database so the database isn't shared between tests with reduced overheads involved in creating and setting up the database for each test.
      singulars
      1. PO
      1. USPeter Horne
    2. CORegarding the differences between SQLite and MySQL, I think the first things that you run into are date and time functions like NOW() that do not work in SQLite. I have a recent post in my blog about using SQLite for unit testing that describes some of these issues http://cvuorinen.net/2012/10/model-testing-using-sqlite-in-memory-database-with-zend-framework/
      singulars
      1. PO
      1. USCvuorinen
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload