Coverage increased (+0.05%) to 79.867% when pulling ae5c89e on justlevine:feat/user-object-mutation-id-inputs into bcee697 on wp-graphql:develop.

1. It seems all the tests are triggering positive for is_multisite().
2. wpmu_delete_user doesnt support reassigning, which is why the test fails on multisite. I think we can use remove_user_from_blog() to keep feature parity.

It's 1:00AM and im not by my pc, but if you dont figure it out before I come back online, i'll dig deeper and tackle the fix then 💤

@justlevine so you can change your env variable to make multisite tests run or not

MULTISTE=0 means the tests will run in non-multisite
MULTISITE=1 means they will run in multisite

I tend to run tests locally outside of docker (faster for me) so I can run them like so: MULTISITE=true vendor/bin/codecept run wpunit or MULTISITE=false vendor/bin/codecept run wpunit

From what I can tell, they're running as expected.

From what I can tell, they're running as expected.

I'm not by my computer, but that's the only reason I can think that the reassign test is failing now with a bad reassign, on all the tests (and not just 5.9 MU). Can be confirmed if you a put a codecept_debug in the is_multisite() conditional in that test. Not sure why that would be, though

@justlevine I mistyped. instead of MULTISITE=false vendor/bin/codecept run wpunit it needs to be MULTISITE=0 vendor/bin/codecept run wpunit

I can verify now by placing this inside the mutate_and_get_payload function in the UserDelete.php file and running the test command.

MULTISITE=0 vendor/bin/codecept run tests/wpunit/UserObjectMutationsTest.php:testDeleteUserWithReassign --debug

MULTISITE=1 vendor/bin/codecept run tests/wpunit/UserObjectMutationsTest.php:testDeleteUserWithReassign --debug

Code Climate has analyzed commit ae5c89e and detected 1 issue on this pull request.

Here's the issue category breakdown:

View more on Code Climate.