In CoreUpdateTest::testUi, confirm that the UI says no update is available after updating successfully

Created on 15 March 2023, over 1 year ago

Problem/Motivation

In \Drupal\Tests\automatic_updates\Build\CoreUpdateTest::assertUpdateSuccessful we have

// The update form should not have any available updates.
    // @todo Figure out why this assertion fails when the batch processor
    //   redirects directly to the update form, instead of update.status, when
    //   updating via the UI.
    $this->visit('/admin/modules/update');
    $this->getMink()->assertSession()->pageTextContains('No update available');

But we don't redirect to the form any more. \Drupal\automatic_updates\BatchProcessor::finishCommit redirects to automatic_updates.finish which is \Drupal\automatic_updates\Controller\UpdateController::onFinish and that redirects to update.status which is the available update reports

Steps to reproduce

Proposed resolution

fix the assertions

Remaining tasks

User interface changes

API changes

Data model changes

πŸ› Bug report
Status

Fixed

Version

3.0

Component

Code

Created by

πŸ‡ΊπŸ‡ΈUnited States tedbow Ithaca, NY, USA

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Production build 0.71.5 2024