Make WordPress Core

Changeset 880 in tests


Ignore:
Timestamp:
07/03/2012 09:16:52 PM (12 years ago)
Author:
nacin
Message:

Remove the old test runner, wp-test.php, and update the README.

Location:
trunk
Files:
1 deleted
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/README.txt

    r760 r880  
    331. Create a clean MySQL database and user.  DO NOT USE AN EXISTING DATABASE or you will lose data, guaranteed.
    44
    5 2. Copy wp-config-sample.php to wp-config.php, edit it and include your database name/user/password.
     52. Copy wp-tests-config-sample.php to wp-tests-config.php, edit it and include your database name/user/password.
    66
    773. $ svn up
     
    1111Notes:
    1212
    13 Test cases live in the 'wp-testcase' subdirectory.  All files in that directory will be included by default.  Extend the WP_UnitTestCase class to ensure your test is run.
     13Test cases live in the 'tests' subdirectory.  All files in that directory will be included by default.  Extend the WP_UnitTestCase class to ensure your test is run.
    1414
    1515phpunit will initialize and install a (more or less) complete running copy of WordPress each time it is run.  This makes it possible to run functional interface and module tests against a fully working database and codebase, as opposed to pure unit tests with mock objects and stubs.  Pure unit tests may be used also, of course.
    1616
    17 The test database will be wiped clean with DROP TABLE statements once tests are finished, to ensure a clean start next time the tests are run.
     17Changes to the test database will be rolled back as tests are finished, to ensure a clean start next time the tests are run.
    1818
    1919phpunit is intended to run at the command line, not via a web server.
Note: See TracChangeset for help on using the changeset viewer.