wdi5: Fiori Elements test is failing
Hello,
we’re testing a FE app and have a simple testcase which is failing.
Given.onTheMainPage.onTable().iExecuteCreate()
Then.onTheDetailPage.iSeeThisPage().and.iSeeObjectPageInEditMode()
If we’re executing it a failure is occouring:
[chrome 102.0.5005.115 windows #0-0] 1) FE basics should see an object page
[chrome 102.0.5005.115 windows #0-0] javascript error: Cannot read properties of undefined (reading 'waitForUI5')
JavaScript stack:
TypeError: Cannot read properties of undefined (reading 'waitForUI5')
at eval (eval at executeAsyncScript (:552:26), <anonymous>:5:14)
at eval (eval at executeAsyncScript (:552:26), <anonymous>:17:8)
at eval (eval at executeAsyncScript (:552:26), <anonymous>:17:33)
at executeAsyncScript (<anonymous>:552:47)
at <anonymous>:567:29
at callFunction (<anonymous>:446:22)
at <anonymous>:460:23
at <anonymous>:461:3
(Session info: chrome=102.0.5005.115)
[chrome 102.0.5005.115 windows #0-0] javascript error: javascript error: Cannot read properties of undefined (reading 'waitForUI5')
[chrome 102.0.5005.115 windows #0-0] JavaScript stack:
[chrome 102.0.5005.115 windows #0-0] TypeError: Cannot read properties of undefined (reading 'waitForUI5')
[chrome 102.0.5005.115 windows #0-0] at eval (eval at executeAsyncScript (:552:26), <anonymous>:5:14)
[chrome 102.0.5005.115 windows #0-0] at eval (eval at executeAsyncScript (:552:26), <anonymous>:17:8)
[chrome 102.0.5005.115 windows #0-0] at eval (eval at executeAsyncScript (:552:26), <anonymous>:17:33)
[chrome 102.0.5005.115 windows #0-0] at executeAsyncScript (<anonymous>:552:47)
[chrome 102.0.5005.115 windows #0-0] at <anonymous>:567:29
[chrome 102.0.5005.115 windows #0-0] at callFunction (<anonymous>:446:22)
[chrome 102.0.5005.115 windows #0-0] at <anonymous>:460:23
[chrome 102.0.5005.115 windows #0-0] at <anonymous>:461:3
[chrome 102.0.5005.115 windows #0-0] (Session info: chrome=102.0.5005.115)
[chrome 102.0.5005.115 windows #0-0] at getErrorFromResponseBody (C:\develop\javascript\onboarding-tool-cap\node_modules\webdriver\build\utils.js:197:12)
[chrome 102.0.5005.115 windows #0-0] at NodeJSRequest._request (C:\develop\javascript\onboarding-tool-cap\node_modules\webdriver\build\request\index.js:166:60)
[chrome 102.0.5005.115 windows #0-0] at processTicksAndRejections (node:internal/process/task_queues:96:5)
[chrome 102.0.5005.115 windows #0-0] at async Browser.wrapCommandFn (C:\develop\javascript\onboarding-tool-cap\node_modules\@wdio\utils\build\shim.js:137:29)
[chrome 102.0.5005.115 windows #0-0] at async Browser.wrapCommandFn (C:\develop\javascript\onboarding-tool-cap\node_modules\@wdio\utils\build\shim.js:137:29)
[chrome 102.0.5005.115 windows #0-0] at async emptyQueue (C:\develop\javascript\onboarding-tool-cap\node_modules\wdio-ui5-service\client-side-js\testLibrary.js:33:12)
Seems that the error is coming from the second line, because a draft record is created.
Another question is when to use which object (Given, When and Then) … is there a more detailed documentation for FE?
About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 22 (2 by maintainers)
I´ll have a look if this test sequence with the initialLoad leads to any issues on our internal OPA tests.
Thanks a lot !!!
Yes … the
npm run builddidi it … I’m able to run your samples … So I will try to compare the configuration & execution … as our apps are similar this sould solve the problems…Let’s see… I will update onthe results.