wdi5: enterText method does not trigger Suggest Event

Describe the bug sap.m.MultiInput have suggestionColumns and suggestionRows aggregations used for tabular input suggestions. Besides this, sap.m.MultiInput has the startSuggestion property used to specify minimum length of the entered text in input before suggest event is fired.

Unfortunately, the suggest event is not triggered after calling the enterText method, respectively the suggestionsm list is not displayed.

The below is my code. I’m just invoking the enterText method

 const multiInputSelector = {
        selector: {
            interaction: "root",
            controlType: "sap.m.MultiInput",
             properties: {
                    name: "MultiInputName"
                }
        }
    }

    const multiInput = await browser.asControl(multiInputSelector);
    await multiInput.enterText(value);

To Reproduce enter text into a MultiInput using enterText method, suggest event is not triggered and suggestion list is not rendered

Expected behavior enter text into a MultiInput using enterText method, suggest event is triggered and suggestion list is rendered

Runtime Env (please complete the following information):

  • wdi5/wdio-ui5-service-version: 0.9.13
  • UI5 version: 1.96.0
  • wdio-version: 7.25.0
  • node-version: 14.17.3
  • OS: macOS Monterey 12.6
  • Browser + Version: Chrome 106.0.0

About this issue

  • Original URL
  • State: open
  • Created 4 years ago
  • Comments: 28 (3 by maintainers)

Most upvoted comments

Hello, We planned to enhance the API of the RecordReplay.interactWithControl function to allow pass information like keepFocus pressEnterKey, idSuffix. That would allow the display the suggestions list as requested in this issue. We will update when the new implementation is available.

Hi @kineticjs,

sorry for the late response. With your snippet I could figure out what the problem is. In this specific case the pressEnterKey of the EnterText function is missing. By looking further into this, I encountered the problem that in the current state of the RecordReplay API we can not provide any additional information to the RecordReplay.interactWithControl function.

On the one hand wdi5 has to pass more information and on the other hand interactWithControl has to understand the additional information

press needs an optional parameter for the interaction type to be passed. enterText needs an optional config object to pass information like clearTextFirst keepFocus pressEnterKey to the recordReplay API.

Maybe it would be good to sync on this topic. @hmanchev and @vobu what do you think?


@hmanchev and @vobu

I ran into another issue where a table row cannot be selected. The reason is because the interaction rowsel doesn’t work properly. Here, I see that it is already mentioned that the press function doesn’t process the passed interaction.

Just wanted to add my +1 vote for the resolution of this issue.

Thanks.

Hi @kineticjs,

sorry for the late response. With your snippet I could figure out what the problem is. In this specific case the pressEnterKey of the EnterText function is missing. By looking further into this, I encountered the problem that in the current state of the RecordReplay API we can not provide any additional information to the RecordReplay.interactWithControl function.

On the one hand wdi5 has to pass more information and on the other hand interactWithControl has to understand the additional information

press needs an optional parameter for the interaction type to be passed. enterText needs an optional config object to pass information like clearTextFirst keepFocus pressEnterKey to the recordReplay API.

Maybe it would be good to sync on this topic. @hmanchev and @vobu what do you think?

Hi @borceacristiann,

thanks for submitting this issue. For enterText we are using the same functionality that OPA5 uses. So it could be an issue on their side. We will come back to you when we could clarify that.