Add tests for when a single supported branch has 2 security updates that are both not insecure

The Needs Review Queue Bot → tested this issue. It either no longer applies to Drupal core, or fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".

Apart from a re-roll or rebase, this issue may need more work to address feedback in the issue or MR comments. To progress an issue, incorporate this feedback as part of the process of updating the issue. This helps other contributors to know what is outstanding.

Consult the Drupal Contributor Guide → to find step-by-step guides for working with issues.

Issue Summary update and title change

#31
1. Already fixed.
2. Added test case and removed @todo in UpdateContribTest.
3. The MR for this is MR1615
4. Check if these results are what is wanted:

Since 1. was her the part affecting usability and was fixed already and the remaining task for this ticket is the test, I'm removing "usability" and needs usability review" tags. If we need to look at the usability aspects of the message (such as order of the recommendations, security updates on each supported minor etc.) it should prbably be a new issue.

Attaching an example screnshot for 10.1.1 message for reference.

smustgrave → changed the visibility of the branch 2865920-when-a-site to hidden.

smustgrave → changed the visibility of the branch 2865920-when-a-site to active.

Rebased and fixed phpcs issue
Hiding patches and old MR (but then un-hid_

Will remove tests tag as test branch is showing failure.

But can we update the MR 1594 for 11.x and include tests too please.

Unsure about the retitle and IS rewrite here. I didn't say the issue was fixed, just that it was mitigated by a recent change to d.o. The issue is still partly present AFAIK.

According to #32.1 this original problem is fixed. tedbow states that they tested on 9.2 and "I think the problem is fixed but we should have test to confirm this doesn't happen again".

As this was tagged, I had this queued for UX review meeting on May 10 but while preparing, I couldn't reproduce the original usability issue as it was already fixed as mentioned in #32. We didn't therefore do a formal review/recommendations and the related discussion is not included in the meeting recording.

quietone → changed the visibility of the branch 2865920-test-without-patch to hidden.

quietone → changed the visibility of the branch 2865920-test-without-patch to active.