Broken interactor due to changed web component
Description
Environment
Potential Workaround
is cloned by
Checklist
hideTestRail: Results
Activity

John Coburn September 27, 2023 at 2:19 PMEdited
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 Bohdan September 27, 2023 at 10:33 AM
Also the same situation in Finance app => Transactions
Yauhen Viazau September 27, 2023 at 9:02 AMEdited
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?
Details
Assignee
John CoburnJohn CoburnReporter
Tetiana GusarTetiana GusarPriority
P2Sprint
NoneDevelopment Team
Stripes ForceFix versions
Release
Poppy (R2 2023)TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee

Reporter

Broken interactor due to changed web component:
https://github.com/folio-org/stripes-components/commit/8b1948a38e7aaea4b911e9913885acd53d5125f0