Unit Tests Failing

  • presspay

    (@presspay)


    13 years ago

    Hi everyone,

    I’m just getting started with the unit tests and have gotten phpunit working and I’m trying to run the unit tests on the 3.5.1 code base. I’m failing a test and getting this error:

    Fatal error: Call to undefined function wp_unslash() in /Users/spinlock/WordPress/wordpress-tests/tests/attachment/slashes.php on line 45

INFO: Trac was inaccessible, so a local ticket status cache was used.

    I think the issue is that I have 2 directories wordpress-tests which is the svn repository for the unit tests and wordpress-3.5.1 for the code base. If I point to wordpress-3.5.1 in wp-tests-config.php I get the above error. But, if I point wp-tests-config.php to wordpress-tests/wordpress/ the test suite runs to completion.

    Can someone explain what’s going on? Should I be checking out a different suite of tests to run against wordpress-3.5.1?

    Thanks!

Viewing 4 replies - 1 through 4 (of 4 total)
  • luisyane27

    (@luisyane27)

    13 years ago

    I’m running into the same issue when running phpunit. Were you able to figure out what the problem was?

    Thread Starter presspay

    (@presspay)

    12 years, 12 months ago

    I was setting the wordpress directory incorrectly. It needs to be the one in the svn repo and not a separate version.

    jibbius

    (@jibbius)

    12 years, 11 months ago

    The problem is that wp_unslash() is a new function that is currently unavailable in v3.5.1 (or earlier versions of WordPress). It is however, available in the development version.

    It only makes sense to use the current Unit Tests repository ( https://unit-tests.svn.wordpress.org/trunk ), if you are testing in this version.

    michaelsauter

    (@michaelsauter)

    12 years, 10 months ago

    I’m getting the same error (on 3.5.2). Is there a way to get unit tests specifically for version 3.5.2?

    I would like to test my plugins against the version that I’m actually using. Testing against trunk is not an option for me as it doesn’t prove that my setup works. Any ideas on how to do that?

    (On a side note: If there are only tests against trunk, that would basically mean that WordPress version (e.g. 3.5.2) get released “untested”?!)

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Unit Tests Failing’ is closed to new replies.

Tags