Skip to:
Content

BuddyPress.org


Ignore:
Timestamp:
02/14/2014 07:51:11 PM (10 years ago)
Author:
boonebgorges
Message:

Don't test prev_value return value on WP < 3.7

There was a bug prior to WP 3.7 that caused update_metadata() to return true
even when the update failed due to a 'prev_value' parameter not being matched.
Since this is not really a functionality issue, but is more about error
reporting, it doesn't affect end-user functionality in BP, except insofar as
the function will return an unexpected value in those cases. Instead of coming
up with an arcane workaround for these old versions, we'll just skip the tests
for the time being.

See https://core.trac.wordpress.org/ticket/24933 for background on the WP issue

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/tests/testcases/xprofile/functions.php

    r7885 r7887  
    448448        $g = $this->factory->xprofile_group->create();
    449449        bp_xprofile_add_meta( $g, 'group', 'foo', 'bar' );
    450         $this->assertFalse( bp_xprofile_update_meta( $g, 'group', 'foo', 'bar2', 'baz' ) );
     450
     451        // In earlier versions of WordPress, bp_activity_update_meta()
     452        // returns true even on failure. However, we know that in these
     453        // cases the update is failing as expected, so we skip this
     454        // assertion just to keep our tests passing
     455        // See https://core.trac.wordpress.org/ticket/24933
     456        if ( version_compare( $GLOBALS['wp_version'], '3.7', '>=' ) ) {
     457            $this->assertFalse( bp_xprofile_update_meta( $g, 'group', 'foo', 'bar2', 'baz' ) );
     458        }
     459
    451460        $this->assertTrue( bp_xprofile_update_meta( $g, 'group', 'foo', 'bar2', 'bar' ) );
    452461    }
Note: See TracChangeset for help on using the changeset viewer.