I’m having difficulties using ‘Verify Element Text’ with regards to the case (upper or lower) of text, in conjunction with cross-browser testing.
I have a piece of text on the page: ‘MY SETTINGS’. Inspecting the element shows the text as ‘My Settings’, so I think there is some JavaScript (or similar) that is capitalising the text, so that on the page, it renders as ‘MY SETTINGS’.
The problem I have is that I see different results for what Katalon regards as actual text, between different browsers.
In Microsoft Edge, the actual text (as observed in error-stack-trace.txt) is shown as ‘My Settings’, but in Chrome, it shows as ‘MY SETTINGS’. This means that whatever I record as the expected text in my data file, either Edge or Chrome will fail, as the text doesn’t match one or the other.
I would imagine that there’s some way of checking which browser is being used, and therefore follow a path suitable for that browser, but I want to avoid complexity, and also that might then mean having two columns of data in my data file (one upper case, one not), which I really want to avoid.
Does anyone have any suggestions for a more straightforward solution?
Perhaps it’s possible to capitalise the captured (actual) text before checking against expected text, therefore making the text case the same before checking?
All suggestions gratefully welcomed - thanks