Tests fail with "Failed to run tests: run-tests.sh reported no tests were found"

Double check your .info file in the test submodule ... you've got files[] = title_test.module instead of files[] = title.test.

I tried to rebuild the dependencies via jenkins, but still get the same results. Believe I need to get permissions to the script which removes the project_dependency source code cache, and will come back to this once I get that straightened out.

The system line might be messing with something, as I get an empty entry at the end of the dependencies array:

Array
(
    [1873988] => Array
        (
            [uri] => entity
            [version] => 7.x-1.0
            [tag] => 7.x-1.0
            [dependency_type] => 0
        )

    [1829790] => Array
        (
            [uri] => entity_translation
            [version] => 7.x-1.0-beta1
            [tag] => 7.x-1.0-beta1
            [dependency_type] => 0
        )

    [1861746] => Array
        (
            [uri] => lingotek
            [version] => 7.x-1.61
            [tag] => 7.x-1.61
            [dependency_type] => 0
        )

    [] => Array
        (
            [uri] => 
            [version] => 
            [tag] => 
            [dependency_type] => 0
        )

)

If clearing the sourcecode cache and rebuilding doesn't resolve this, I'll bump it to project_dependency as a bug.

Same result after clearing the sourcecode cache and rebuilding the dependencies.

Can you try removing the space after the > symbol dependencies[] = system (> 7.14)? It looks like the examples at http://drupal.org/node/542202 don't have any spaces after the operators, and if the project_dependency code is assuming no space, that may be what's introducing the extra entries in the dependency array.

Good to hear ... I've opened #1905382: Extraneous spaces between operator and versioned dependency result in invalid calculation as a followup.

Same issue with a Chessboard patch here: http://qa.drupal.org/pifr/test/438708
This is my first test run since the PIFR update.

I realized that the mentioned patch itself probably killed bot class loading. I'll check later, but for now please disregard #13.

K ... I isolated this test on a bot to do some troubleshooting ... the bot has properly located the test file, and is passing the test request on to simpletest via the following command:

/usr/bin/php ./scripts/run-tests.sh --concurrency 8 --php /usr/bin/php --url 'http://drupaltestbot953/checkout' --file sites/default/modules/title/tests/title.test

It is simpletest which is firing back the error message saying that no tests were found. Can you try executing that test via the run_tests.sh script from drupal root, as follows:

/path/to/php ./scripts/run-tests.sh --url 'http://drupalsite' --file 'path/to/module/tests/title.test'

If you can make that work locally, it should also work on the bots.

This actually does *not* work from the command line, contrary to #16. I had the testbot build the whole thing and then ran it manually.

So it's either a problem with the code itself of a problem with drupal core and the run_tests.sh. I do notice using debugs that several of the classes in your .test file do not get loaded into $all_tests (although a couple of them do...)

For your convenience I've provided the full checkout on the testbot and the database provided by the testbot.

Files: https://www.dropbox.com/s/esm4m3m6fm5xeaf/title_test_full_files.tgz
Database: https://www.dropbox.com/s/mlzbb2nj8dqflyz/title_test.sql.gz