You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected behavior
Supposed to Navigate to the shell home (Fiori launchpad page)
Logs/Console Output
[0-0] Error in"test.I reopen app"
Error: Invalid URL: #Shell-home
at validateUrl (C:\Users\nnnnnn\git\wdi5-testing\node_modules\webdriverio\build\utils\index.js:378:45)
at Browser.url (C:\Users\nnnnnn\git\wdi5-testing\node_modules\webdriverio\build\commands\browser\url.js:47:52)
at Browser.wrapCommandFn (C:\Users\nnnnnn\git\wdi5-testing\node_modules\@wdio\utils\build\shim.js:137:38)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at Browser.<anonymous> (C:\Users\nnnnnn\git\wdi5-testing\node_modules\wdio-ui5-service\src\lib\wdioUi5-index.js:483:17)
at Browser.wrapCommandFn (C:\Users\nnnnnn\git\wdi5-testing\node_modules\@wdio\utils\build\shim.js:137:29)
Runtime Env (please complete the following information):
wdi5/wdio-ui5-service-version: 0.8.2
UI5 version: [1.99.0-SNAPSHOT]
wdio-version (output of wdio --version): 7.16.15
node-version (output of node --version): 16.13.2
OS: Win 10
Browser + Version : chrome (v98.0.4758.82) on Windows
The text was updated successfully, but these errors were encountered:
the command itself is syntactically correct (browser.goTo({ sHash: '#Shell-home' }))
might be a problem with your configuration.
can you share your wdio.config.(j|t)s-file please? "baseUrl" and the "wdi5" should be sufficient.
Describe the bug
browser.goTo
does not navigate to Shell-homeTo Reproduce
async iNavigateToHomePage() {
await browser.goTo({ sHash: '#Shell-home' });
}
Expected behavior
Supposed to Navigate to the shell home (Fiori launchpad page)
Logs/Console Output
Runtime Env (please complete the following information):
wdi5/wdio-ui5-service
-version: 0.8.2UI5
version: [1.99.0-SNAPSHOT]wdio
-version (output ofwdio --version
): 7.16.15node
-version (output ofnode --version
): 16.13.2The text was updated successfully, but these errors were encountered: