Uploaded image for project: 'Moodle'
  1. Moodle
  2. MDL-48194

phpunit testsuites inconsistently named

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Minor Minor
    • 2.7.4, 2.8.2
    • 2.6.6, 2.7, 2.8
    • Unit tests
    • MOODLE_26_STABLE, MOODLE_27_STABLE, MOODLE_28_STABLE
    • MOODLE_27_STABLE, MOODLE_28_STABLE
    • MDL-48194-master
    • Hide
      1. Run all unit tests in the world, ever
      2. Check that we didn't break jenkins
      3. Run commands at your glee. Here are a few examples: 

        vendor/bin/phpunit --testsuite core_phpunit_testsuite
        		 
        vendor/bin/phpunit --testsuite mod_quiz_testsuite
        		 
        vendor/bin/phpunit --testsuite logstore_standard_testsuite

      Show
      Run all unit tests in the world, ever Check that we didn't break jenkins Run commands at your glee. Here are a few examples: vendor/bin/phpunit --testsuite core_phpunit_testsuite vendor/bin/phpunit --testsuite mod_quiz_testsuite vendor/bin/phpunit --testsuite logstore_standard_testsuite

      In the generated phpunit.xml, the generated testsuite names are inconsistently named:

      Core testsuites are named like:
      <testsuite name="core_phpunit_testsuite">

      All others are named:
      <testsuite name="atto_indent test suite">

      It's irritating because it makes them less guessable when wishing to run all testsuits for a component.

      They should ideally all match the same naming scheme without spaces and with the word 'testsuite' rather than two words 'test suite'

            dobedobedoh Andrew Lyons
            dobedobedoh Andrew Lyons
            Frédéric Massart Frédéric Massart
            Sam Hemelryk Sam Hemelryk
            Adrian Greeve Adrian Greeve
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved:

                Error rendering 'clockify-timesheets-time-tracking-reports:timer-sidebar'. Please contact your Jira administrators.