When you execute run-tests.sh from the terminal, there is no indication of the current test_id. The test_id is useful if you want to visit admin/config/development/testing/results/TEST_ID to see the full results in your browser.

Patch forthcoming.

CommentFileSizeAuthor
#11 906004_test_id-11.patch722 bytesabhi170893
#9 906004_test_id-9.patch718 bytesabhi170893
#6 906004_test_id-5.patch852 bytesAnonymous (not verified)
#5 906004_test_id-4.patch850 bytesAnonymous (not verified)
#4 906004_test_id-3.patch1.33 KBAnonymous (not verified)
#2 906004_test_id-2.patch852 bytesAnonymous (not verified)
#1 906004_test_id.patch869 bytesAnonymous (not verified)

Comments

Anonymous’s picture

Anonymous (not verified) commented
StatusFileSize
new 906004_test_id.patch869 bytes

Here is the patch. It's my first core patch, so feedback is obviously appreciated.

Code for convince:

function simpletest_script_reporter_display_results() {
  ...
 
  global $args;
  echo "\n";
  echo "Test Results\n";
  echo "------------\n";
  echo "Test ID: $test_id\n";
  echo "Test results page: "{$args['url']}"admin/config/development/testing/results/$test_id\n";
  if (variable_get('simpletest_clear_results', TRUE)) {
    echo "(WARNING: Disable the 'Clear results after each complete test suite run' option\n";
    echo " in testing settings to have access to results on the above URL.)";
  }
  echo "\n";
}
Anonymous’s picture

Anonymous (not verified) commented
StatusFileSize
new 906004_test_id-2.patch852 bytes

I realized that global $args is redundant.

New patch attached.

Anonymous’s picture

Anonymous (not verified) commented
Status: Active » Needs review

And marking as "needs review"

Anonymous’s picture

Anonymous (not verified) commented
StatusFileSize
new 906004_test_id-3.patch1.33 KB

Fixing an obvious bug in the way I had the string formatted.

Anonymous’s picture

Anonymous (not verified) commented
StatusFileSize
new 906004_test_id-4.patch850 bytes

Sorry. This takes practice, apparently.

Removing unnecessary junk from the top of the patch.

Anonymous’s picture

Anonymous (not verified) commented
StatusFileSize
new 906004_test_id-5.patch852 bytes

At Albright's suggestion, I added a \n to the second line in the if statement.

New patch up.

thedavidmeister’s picture

thedavidmeister commented
Version: 7.x-dev » 8.0.x-dev
Issue summary: View changes
Status: Needs review » Needs work
Issue tags: +Needs reroll

Apparently run-tests.sh might be going away sometime soonish in the new CI setup, but for now this patch is still relevant to d8 and should be easy enough to port.

thedavidmeister’s picture

thedavidmeister commented

Actually, looking at the patch again. I don't think there's any point showing a URL and saying "oh by the way, that URL is a 404". The warning message should show OR the info with the test ID should show. No reason to have both.

abhi170893’s picture

abhi170893 commented
Status: Needs work » Needs review
Issue tags: -Needs reroll
StatusFileSize
new 906004_test_id-9.patch718 bytes

the attached patch applies cleanly to the 8.0.x

Status: Needs review » Needs work

The last submitted patch, 9: 906004_test_id-9.patch, failed testing.

abhi170893’s picture

abhi170893 commented
Status: Needs work » Needs review
StatusFileSize
new 906004_test_id-11.patch722 bytes

replaced the variable_get() with \Drupal::config()->get().

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

mile23’s picture

mile23
Primary language English
Location Seattle, WA
commented
Status: Needs review » Postponed (maintainer needs more info)

run-tests.sh isn't going away any time soon.

run-tests.sh currently has a --browser option, which lets you see results in the browser.

What else is needed?

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.9.x-dev » 9.2.x-dev

Drupal 8 is end-of-life as of November 17, 2021. There will not be further changes made to Drupal 8. Bugfixes are now made to the 9.3.x and higher branches only. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.2.x-dev » 9.3.x-dev
quietone’s picture

quietone commented

Is this issue still a problem?

There has been no activity here for 5 years.

Since we need more information to move forward with this issue, I am keeping the status at Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.15 was released on June 1st, 2022 and is the final full bugfix release for the Drupal 9.3.x series. Drupal 9.3.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.4.x-dev branch from now on, and new development or disruptive changes should be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.9 was released on December 7, 2022 and is the final full bugfix release for the Drupal 9.4.x series. Drupal 9.4.x will not receive any further development aside from security fixes. Drupal 9 bug reports should be targeted for the 9.5.x-dev branch from now on, and new development or disruptive changes should be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

smustgrave’s picture

smustgrave commented
Status: Postponed (maintainer needs more info) » Closed (outdated)

Since there has been no follow up since requesting if this is still a feature 1 year ago (#23) going to close out

Thanks!