All work

Select view

Select search mode

 
50 of 89

Broken interactor due to changed web component

Done

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

6

Checklist

hide

TestRail: Results

Details

Assignee

Reporter

Priority

Sprint

Development Team

Stripes Force

Fix versions

Release

Poppy (R2 2023)

RCA Group

TBD

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created September 27, 2023 at 8:03 AM
Updated October 11, 2023 at 7:55 PM
Resolved October 5, 2023 at 5:10 PM

Activity

Show:

John CoburnSeptember 27, 2023 at 2:19 PM
Edited

I've pushed PR's to stripes-testing to update the interactors, with a PR in stripes-components that is pointed at the fix branch. https://github.com/folio-org/stripes-testing/pull/168

I don't particularly want to use the mclContainer class in multiple places within the component since it would require more interactor work to target the correct element, and I'm hesitant to actually move the id to a different element as that could potentially break other tests. Either of these options are possible approaches if updating the interactor alone is not adequate.

Ihor BohdanSeptember 27, 2023 at 10:33 AM

Also the same situation in Finance app => Transactions

Yauhen ViazauSeptember 27, 2023 at 9:02 AM
Edited

At least the following elements were affected (mclContainer class removed and therefore existing interactors do not work):

  • #job-logs-list in Data Import

  • #list-inventory in Inventory

- could you please take a look and add mclContainer class to affected elements if possible?

TestRail: Cases
TestRail: Runs

Flag notifications