Problem/Motivation

Follow up to #2931598: Messenger methods drop repeat flag where we introduced a new kernel test that covers the functionality of the legacy drupal_set_message() tests. However, there is some migration tests which also depend on these.

Proposed resolution

Remove legacy drupal_set_message() tests such as

  • \Drupal\Tests\system\Functional\Bootstrap\DrupalSetMessageTest::testDrupalSetMessage
  • \Drupal\system_test\Controller\SystemTestController::drupalSetMessageTest

Remaining tasks

N/A

User interface changes

N/A

API changes

N/A

Data model changes

N/A

Comments

kim.pepper created an issue. See original summary.

kim.pepper’s picture

Title: Remove legacy drupal_set_message tests » [PP-1] Remove legacy drupal_set_message tests
kim.pepper’s picture

Status: Active » Postponed
kim.pepper’s picture

Status: Postponed » Active
kim.pepper’s picture

Title: [PP-1] Remove legacy drupal_set_message tests » Remove legacy drupal_set_message tests

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

Drupal 8.5.0-alpha1 will be released the week of January 17, 2018, which means new developments and disruptive changes should now 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.6.x-dev » 8.7.x-dev

Drupal 8.6.0-alpha1 will be released the week of July 16, 2018, which means new developments and disruptive changes should now 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.7.x-dev » 8.8.x-dev

Drupal 8.7.0-alpha1 will be released the week of March 11, 2019, which means new developments and disruptive changes should now be targeted against the 8.8.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.8.x-dev » 8.9.x-dev

Drupal 8.8.0-alpha1 will be released the week of October 14th, 2019, which means new developments and disruptive changes should now be targeted against the 8.9.x-dev branch. (Any changes to 8.9.x will also be committed to 9.0.x in preparation for Drupal 9’s release, but some changes like significant feature additions will be deferred to 9.1.x.). For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

jeroent’s picture

Version: 8.9.x-dev » 9.0.x-dev
Status: Active » Closed (outdated)

This seems to be fixed.