search

wp-cli / doctor-command

Diagnose problems within WordPress by running a series of checks for symptoms
MIT License
146 stars 22 forks source link

Update test suite to get tests passing again #110

Closed danielbachhuber closed 7 years ago

danielbachhuber commented 7 years ago
danielbachhuber commented 7 years ago

@schlessera This looks funky:

[ErrorException]                                                                                                                          
  include_once(/home/travis/build/wp-cli/doctor-command/php/WP_CLI/AutoloadSplitter.php): failed to open stream: No such file or directory

Why would the path be incorrect in this manner?

schlessera commented 7 years ago

I fixed the issue so that the tests run now, but not in a satisfying way for now. See https://github.com/wp-cli/autoload-splitter/issues/5 for the problem to solve.

schlessera commented 7 years ago

Still fails, now because of a plugin update warning:

...................................................................... 70
...................................................................... 140
...................................................................... 210
.......................................F...................F----...... 280
...............................................................
(::) failed steps (::)
01. name    status  message
    plugin-update   warning 1 plugin has an update available.
    In step `Then STDOUT should be a table containing rows:'. # features/steps/then.php:44
    From scenario `Plugins are up to date'.                   # features/check-plugin-update.feature:11
    Of feature `Check whether plugins are up to date'.        # features/check-plugin-update.feature
02. $ wp doctor check --all --spotlight
    name    status  message
    plugin-update   warning 1 plugin has an update available.

    cwd: /tmp/wp-cli-test-run-59097a78b71457.24786200/
    exit status: 0
    In step `Then STDOUT should be:'.                                # features/steps/then.php:15
    From scenario `Use --spotlight to focus on warnings and errors'. # features/check.feature:3
    Of feature `Basic check usage'.                                  # features/check.feature
66 scenarios (64 passed, 2 failed)
343 steps (337 passed, 4 skipped, 2 failed)
4m33.193s
danielbachhuber commented 7 years ago

@schlessera This is fixed now