wordpress-develop

mirror of https://github.com/gosticks/wordpress-develop.git synced 2026-04-04 04:34:31 +00:00

Files

Robert Anderson 385c29b49a Fix wp.i18n.isRTL()

Fixes a bug causing wp.i18n.isRTL() to return false in RTL langauges by manually
loading the translated 'ltr' string for the i18n dependency. This ports over an
identical fix that was made in Gutenberg.

Fixes #52441.
Props @jonsurrell @youknowriad.


git-svn-id: https://develop.svn.wordpress.org/trunk@50259 602fd350-edb4-49c9-b593-d223f7449a82

2021-02-08 23:49:33 +00:00

data

Blocks: Add automatic RTL handlind for block styles registered from metadata

2021-01-19 11:48:59 +00:00

includes

Build/Test Tools: Check if Travis/GitHub Actions environment variables are defined.

2021-01-02 12:19:41 +00:00

tests

Fix wp.i18n.isRTL()

2021-02-08 23:49:33 +00:00

build.xml

Coding Standards: Replace spaced indentation sections of phpunit.xml.dist, multisite.xml, and build.xml with tabs.

2019-01-28 17:20:06 +00:00

multisite.xml

Build/Test Tools: Allow code coverage reports to be generated when running tests as a multisite.

2020-12-12 20:07:55 +00:00

README.txt

Update tests/README.txt to reflect the new tests directory structure. props jdgrimes. fixes #25133 .

2013-08-31 13:42:56 +00:00

wp-mail-real-test.php

Code Modernization: Replace dirname( __FILE__ ) calls with __DIR__ magic constant.

2020-02-06 06:31:22 +00:00

README.txt

The short version:

1. Create a clean MySQL database and user.  DO NOT USE AN EXISTING DATABASE or you will lose data, guaranteed.

2. Copy wp-tests-config-sample.php to wp-tests-config.php, edit it and include your database name/user/password.

3. $ svn up

4. Run the tests from the "trunk" directory:
   To execute a particular test:
      $ phpunit tests/phpunit/tests/test_case.php
   To execute all tests:
      $ phpunit

Notes:

Test 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.

phpunit 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.

Changes to the test database will be rolled back as tests are finished, to ensure a clean start next time the tests are run.

phpunit is intended to run at the command line, not via a web server.